This article describes the basic steps for UXcam Customization when you are setting up your account.
4.1 Plan events and properties
UXCam automatically detects the screens visited and the different gestures of the user (taps, double taps, swipes, etc). In addition, we detect two events automatically:
- Rage taps: to show user frustration
- UI Freezes: when the screen freezes
To gather more and better insights into your users’ interaction with your application, you must send custom events and properties to UXCam. Planning your events and aligning them with your goals and metrics will help you speed up and organize the process.
An event can indicate any interaction that occurs between the user and your application. It can be an action that the user performs (e.g., pressing a button) or a specific event (e.g., an error message was displayed).
What events to send to UXCam?
We recommend planning your events based on your goals and the key metrics you want to track in the Dashboard. A few examples are:
- Steps needed for the registration process (e.g., add name, email, password, phone, etc.)
- Actions or tasks required to complete an important process in your application. (e.g. add to cart, or add payment method).
- Processes that the user must complete in your app (e.g. onboarding or validation)
- Error messages or options to delete or cancel a process.
- Actions related to a new feature that you recently launched (e.g. to measure adoption)
Ask your team what questions they want to answer with UXCam insights and define the events required to answer these questions.
Add more details to your events withproperties. A property is an attachment to the event that provides more information and allows you to dig deeper into the interaction. Each event can have up to 20 properties. E.g. for your cinema app, you have the event add to the cart. This event can have the properties: movie name, movie category, movie time, selected theater, ticket price, and the number of tickets.
✏ Note: To make it easier for you and your team to analyze, it is advisable to establish an event naming system to be consistent and clear. Focus on sending the most important events, then you can iterate and evaluate if you need more events or need to remove some.
You can use this table as a reference to plan your events.
|Goal||Metric||Question||Event||Event description||Event properties||Example||Flow||Importance||Sequence|
|Increase conversion rates for adding extra products to the cart along with movie tickets.||Number of ticket purchases that have additional products added.
Purchases with extra items vs purchases with only movie tickets.
|Why don't customers add extras to the purchase?
How did customers navigate the list of available products?
|Add_product_cart||When the user adds an extra product to the cart||Product_name
|Add_ticket_cart||When the user adds the movie ticket to the cart||Movie_name
|Purchase_completed||When the user completes the purchase||Movie_name
✏ Note: you can use events to filter sessions, create user segments, group your data, and create conversion funnels. You can get a lot more value from UXCAm by sending events.
Reference: event add to cart grouped by event property: item name and user property: language
Once you have the events defined, share the list and our API Guide with your developers. Available here → .
4.2 Define user properties
UXcam automatically detects unique users based on the device ID and assigns a random alias in the Dashboard. However, you can identify your users with a unique ID thanks to our API 'Set user identity'.
By default, UXCam captures data related to the user's location (based on the device IP) and data related to the user's device (model, platform, app version, internet connection, etc.). But you can attach other properties to a user profile; some of the most common are:
- Demographic data: age, gender, date of birth, language.
- Marketing data: referral source, campaign ID.
- Type of user: free or premium users, users of a loyalty program, type of subscription.
Guide to add user properties →
User information will allow you to create different segments, focus on certain groups of users, and group your events or funnels to observe differences in behavior between users.
UXCam is GDPR compliant and can be used with anonymous data of your users, without the need to send any PII data (e.g. name, phone, email); however, if you want to send these personal details you must sign a DPA agreement with us. Available online here.
4.3 Hide sensitive information
If you collect sensitive information in your application such as passwords or personal data, or you have payment pages, you can hide this information from the recordings. You have two ways to do it and different possibilities:
a. Hide sensitive information from the Dashboard
• Hide all the text fields, such as the fields of a registration form
• Hide entire screens, you can choose which screens you want to hide or which screens you want to record, depending on your requirements. E.g. you can hide the screen to add credit card details.
✏ Note: when you hide a whole screen, you can choose to record or not record the gestures.
b. Hide sensitive information with our API
• Hide text fields
• Hide entire screens
• Hide a sector of the screen - e.g. an account number
Please notice that the availability and possibilities of this API are subject to the framework you use, you can check the compatibility in the guide.
All the hidden screens or views of your app will appear under a red box in the video recordings and will be hidden before we render the video. Therefore, the info will never be sent to UXCam.
4.4 Allow short break for another app
Sessions are stopped and uploaded when the user sends the app to the background. If your app includes processes that require the use of other applications to be completed e.g. login with Facebook, take and upload a photo, scan a code, etc. You can use our Allow short break API to avoid having the session split.
This implies that UXCam will wait a few minutes for the user to return from the other application to continue with the recording instead of finalizing it and immediately uploading it to the Dashboard.
You can read more about it here →
4.5 Tag your screens & fragments
UXCam will automatically capture the screen name for Native apps and Xamarin framework, if you use any other framework such as Flutter, React Native, Unity, Ionic, or Cordova you will need to manually tag your screens with our API.
[Android]Since UXCam captures screens (view controllers and activities) and not fragments if you have one or more fragments inside an activity you need to tag them with our API.
⚠️ Please notice that when tagging your screens you need to disable our Automatic screen-tagging and make sure you tag all the screens and consider all the screen transitions to avoid any issues.
Now that everything is set up, it's time to start exploring the Dashboard.