Web-Specific Filters
When analyzing web sessions, UXCam provides additional filtering options tailored for web environments. These include:
Device & Browser Filters
Device & Browser Filters
Browser: Filter by browser name (e.g., Chrome, Edge, Safari).
Browser Version: Narrow down to a specific browser version.
OS: Identify sessions by operating system (Windows, macOS, Linux, iOS, Android).
Device Type: Differentiate between Desktop, Mobile, or Tablet users.
Session Properties
Session Properties
Referrer: The full URL of the page that referred the user to the site.
Referrer Domain: The domain of the referring website.
Landing UTM Parameters: Used to track campaign performance (e.g., Source, Medium, Campaign, Content).
Events (Auto-Captured in Web Sessions)
Events (Auto-Captured in Web Sessions)
These events help analyze user engagement and frustration:
uxc_dead_click: A user clicks on an unresponsive element.
uxc_input: An input field loses focus after modification.
uxc_page_refresh: The page is refreshed.
uxc_submit: A form is submitted.
uxc_u_turn: A user navigates back to the previous page.
uxc_url_navigate: A user navigates between URLs.
You can filter sessions based on all the above events and properties.
Web Filtering Benefits
Optimize for Specific Browsers & OS: Identify performance issues or UI inconsistencies across different browsers and operating systems.
Adapt UI/UX for Device Types: Ensure a seamless experience for desktop, tablet, and mobile users.
Detect Frustration Points: Use events like dead clicks, U-turns, and page refreshes to find usability issues.
Segment Users Based on Attributes: Filter by location, language, or acquisition source to analyze user behavior.
Screen Visit Properties (Leveraging Page Definition)
One of the key advantages of UXCam’s web analytics is the ability to filter by screen visit properties, which are derived from Page Definition.
Using Page Definition for Filtering & Segmenting
Page Definition allows you to:
Save dynamic URL parameters (e.g., Product ID, Category, Campaign ID) as properties.
Use these properties for filtering in session replays and analytics reports.
In an e-commerce website, Page Definition has been used to define the:
Category view page and save the category name as a screen visit property.
Product details page and save the product id as a screen visit property.
This means you can filter sessions based on product categories like:
Page name | Saved properties | Example |
Category view | Category name | Sweaters, Jackets, Dress |
Product details page | Product Id's | iz46971, ib98120 |
Click on Filters > Screen visit properties> Page name > select one of the saved properties.
With these saved properties, teams can:
Search for sessions where users interacted with a specific product.
Identify usability issues and trends for individual products.
Track user interactions, bounce rates, and engagement for specific categories (e.g., Jackets, Dresses).
Compare engagement metrics across different product categories.
Track conversions from category pages to product pages and checkout.