Step 1: Add Tracking Code
If installing via code, copy and paste the UXCam snippet inside the
<head>section of your website.If using Google Tag Manager (GTM), follow this guide to configure UXCam through GTM.
After integration, UXCam will begin recording user interactions automatically. Sessions will be available within 5-10 minutes.
Step 2: Select authorized domains/subdomains for data-capture (Optional)
To restrict session recording, go to App settings > Data capture & recording and specify the domains and subdomains where tracking should be enabled. Only sessions from the listed domains (that also have the integration code) will be captured. If no domains are added, all sessions will be recorded by default.
Step 3: Decide what defines a screen visit
How UXCam tracks screen Visits
UXCam tracks screen visits by default based on URL path changes. You can choose to track screen visits paged on four different options depending on your web requirements.
Go to app settings > Scroll to additional settings :
Step 4: Set user identity and send user properties
By default, UXCam identifies users based on Browser ID, which can be found under Install ID. Each user is assigned a random alias. To identify users across multiple devices or use your own unique identifiers, you can set user identity by following this guide.
⚠️ Note: Users are tracked based on their browser rather than their device. If a user switches browsers, they will be counted as a different user unless an ID is provided. If you are using UXCam for mobile & web, we highly recommend sending a consistent User ID across both platforms to ensure more efficient tracking.
Sending Additional Properties
Sending custom user properties allows you to segment users, filter sessions, and analyze behavior across different audiences. You can send additional properties
Property | Description |
User ID | Assign a unique identifier to track individual users across devices. |
Acquisition Source | Understand whether a user came from a campaign, referral, or organic source. |
Subscription Type | Track differences in behavior between free and paid users. |
Loyalty Membership | Analyze engagement of VIP vs. regular users. |
📌 Note: We recommend not sending PII data (e.g., email, phone number).
Step 5: Send events
You can track user interactions by sending events to UXCam. This helps you analyze user behavior, optimize conversion funnels, and identify friction points in the user journey.
UXCam already captures these events by default.
⚙️ To learn more about the technical requirements on how to send over additional events, refer to the developer documentation.
You can send events through code
You can send events through Google tag manager. You can reuse existent triggers or push data from GTM data layers.
Step 6: Define pages
By default, UXCam tracks every unique URL as a separate page. However, modern web apps often use dynamic URLs with user IDs, product names, or filters that shouldn’t be counted as separate pages.
Page Definition allows you to group similar URLs under a single name, ensuring cleaner reports while still retaining key details as properties.
Step 7: User Privacy: Occluding Sensitive Data
UXCam automatically occludes input fields that are likely to contain sensitive information. By default, input fields are occluded if they meet any of the following criteria:
Input Types:
password,email,tel,hidden,numberInput Names Containing:
password,cc-,emailAutocomplete Properties Containing:
cc-,address,phone,email,password
UXCam also allows you to occlude sensitive data in URLs and query parameters to protect user privacy via code.
Occluding Sensitive Data in URLs & Query Parameters
You can specify which query parameters should be masked to prevent exposing sensitive information.
Occluding Query Parameters Example:
Before:
http://www.uxcam.com/query?product=shoes&userId=321After:
http://www.uxcam.com/query?product=_occluded_&userId=_occluded_
Occluding URLs Example
A custom function can modify and mask parts of the URL before query parameters.
Example:
Before:
http://www.uxcam.com/invite/12345After:
http://www.uxcam.com/invite/:inviteId
⚙️ To learn more about the technical requirements, refer to the developer documentation.