When does a web session start and end? Is it different than a mobile session? 

Yes, the way we capture sessions on web is different from mobile. A web session starts when a user opens a website tab and starts interacting with it. If there is no incoming data for 3 minutes—due to reasons like the browser/tab being closed, internet loss, or system suspension—the session is considered ended, and the recording is uploaded.

 

What happens if the customer loses internet connection?

If a customer loses their internet connection, what happens depends on how long the connection is lost:

• Scenario 1: If the connection is lost for more than 3 minutes, the session up until the disconnection is uploaded. Any actions taken offline during the downtime are not recorded. If the user reconnects and refreshes or opens a new page, a new session will start.

• Scenario 2: If the connection is restored within 3 minutes, the entire session, including any offline activity, is recorded and uploaded as a single session.

 

How does UXCam identify users in web? 

Browser-Based Tracking: Unlike mobile devices, 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.

 

What events does UXCam track automatically on web ? 

By default, the following events are captured. You can of course analyze these anywhere in the dashboard.

 

• uxc_input: Triggered when an input loses focus after it has been modified.
• uxc_submit: Triggered when a form is submitted.
• uxc_u_turn: Triggered when a user goes back to the same page. The event is triggered on the page they went back to.
  Example: If a user navigates Home > About Us > Home, it will be triggered on Home.
• uxc_page_refresh: Triggered when refreshing the page.

What does UXCam automatically occlude on web ? 

What are some differences between default web vs. mobile properties?

How are screens captured? 

Automatic Capture: Screens are captured automatically based on changes to the URL path.

URL Structure: Changes in the domain, subdomain, path, query parameters, or fragments can trigger a new screen visit.

Dynamic URLs: Dynamic IDs in URLs can result in multiple screen visits for the same page, complicating analysis.

Filtering: Use the 'Screen name Contains' filter to group similar pages. For example, filtering by "Screen name contains Sessions" will consolidate all sessions-related screens.

Future Improvements: The UXCam team plans to enhance screen capture and filtering in future versions of the Web SDK.