Integrating UXCam's SDK is a straightforward process and the basic implementation shouldn't take your devs more than a few minutes. Below is a user-friendly checklist for you to understand the steps involved, what's required and our recommendations so you can have derive most value from UXCam. You'll understand what your developers can do for you to get even more granular insights.
Your developers can refer to the technical dev documentation here.
| Steps | Description | Why? Best Practices | Guides/Resources |
|---|---|---|---|
| 1 | Required:Create separate instances for your test/internal data and your production data | Separating environments from the start will help you keep your data clean and reliable and exclude internal users which might skew your data. | Dev guide : Locate API Key |
| 2 | Required: Install the SDK | Dev guide: Install SDK | |
| 3 | Required: Hide end-user personal data | If you collect sensitive information in your app like : Passwords, Personal data, Payment pages. You can hide this information from recordings through your developers or directly on the dashboard. Refer to guides to the right for help! | |
| 4 | Required: Tag the screens in your app |
Depending on the app's frameworks, screens may be tagged automatically or manually by your dev. Best Practice : Go to screens and click on a screen to check the heat map screenshots. Ensure that all screens appear correctly. 💡Tip » If you'd like to change the name of a screen to make it clearer : Go to screens> screen name>pencil icon. The name will change across the dashboard |
Dev guide : Tag screens |
| 5 | Recommended: Utilize opt in or out APIs to clean your production data | Dev guide : opt-in-opt-out | |
| 6 | Recommended: Send custom events to UXCam |
You can send Events to UXCam to have more insights about your users’ behavior to understand how they interact with each element of your screen, measure the adoption of new features, create meaningful funnels, and closely follow the user journey. An Event is a user interaction with your app that can be measured independently of the screens, e.g. Press a certain button, Add to Cart. You can send up to 100 events. Best Practice : You should firstly map all of them and then ask your engineers to send them to UXCam. Check the guides on the right for a spreadsheet structure and ideas of events. |
Need some inspiration? |
| 7 | Recommended: Send custom user properties to UXCam |
You can enrich your behavioral and user data thanks to custom user properties. You can send up to 100 additional user properties such as age, gender, or loyalty status. Best Practice : You should firstly map all of them and then ask your engineers to send them to UXCam. 💡Tip » Send over your own user ID to replace the default alias with your own user ID to easily identify your users when you filter for them.
|
Next steps
Now that the SDK integration is completed, it time to think strategically and define goals & key metrics!