Sessions
27
Visits included after brand, date, device, and path-depth filters.
User Journeys
User Journeys combines page paths, search requests, chat requests, downloads, route maps, top paths, and session drill-downs so teams can see how visitors move from first page to meaningful action.
User Journeys
Product workflow
Filter journeys by the traffic that matters
Choose the brand, tracking site, date range, device segment, minimum sessions, and maximum steps before refreshing the report.
Read the journey map and top paths
Use the bubble map, sessions, visitors, average steps, and common path table to understand where visitors start, branch, and continue.
Investigate visitor-level sessions
Open the session explorer when aggregate data needs proof: inspect visitor IDs, session timestamps, route activity, and step counts.
Journey Snapshot
User Journeys summarizes sessions, visitors, and average path depth before you inspect maps, top paths, route activity, and individual visitor sessions.
27
Visits included after brand, date, device, and path-depth filters.
14
Unique visitor IDs represented in the selected journey window.
3.1
Average route depth across the sessions being analyzed.
Journey Controls
The journey view starts with practical controls for brand, tracking site, date range, device, minimum sessions, and maximum path depth.
Explore user journeysChoose a verified brand and confirm the site collecting journey events.
Set from and to dates to inspect a launch week, campaign window, or recent behavior.
Compare all traffic or narrow the report to desktop, tablet, or mobile sessions.
Use minimum sessions and maximum steps to remove noise or expand the map.
Intent Signals
Request cards connect navigation behavior to intent signals from Compass Search, Campaigns, and MagnetHub during the same reporting window.
7
Search requests
Count search requests alongside page paths to see when visitors need help finding content.
7
Campaign events
Track campaign activity during the same window so triggered messages are visible in the journey context.
4
Download requests
Measure download requests so resource interest can be compared with navigation paths.
Path Diagnostics
Plot routes by step so teams can see which pages dominate entry, where visitors move next, and how deep exploration goes.
Rank the most common single-page and multi-step paths so high-volume behavior is easy to compare with intended funnels.
Move from aggregate paths into visitor-level sessions when a pattern needs closer inspection.
Review route activity over time to understand when a selected visitor or segment moved through the site.
Keep search, chat, and download requests visible next to page behavior so intent signals do not sit in separate reports.
Workflow
Pick brand, dates, device, minimum sessions, and max steps before refreshing the journey report.
Use sessions, visitors, average steps, and the bubble map to understand how broad or deep exploration is.
Review top paths to see whether visitors follow expected navigation or branch into confusing detours.
Open the session explorer for visitor-level evidence before changing navigation, copy, or calls-to-action.
Choose the brand, tracking site, date range, device segment, minimum sessions, and maximum steps before refreshing the report.
Use the bubble map, sessions, visitors, average steps, and common path table to understand where visitors start, branch, and continue.
Open the session explorer when aggregate data needs proof: inspect visitor IDs, session timestamps, route activity, and step counts.
Start with the page that matters most