User Journey

Instead of evaluating pages in isolation, the User Journey report maps the continuous sequence and flow of user movement: from the entry point, through the paths users take across different sections, to the moment of exit. This analysis helps you identify and address the drop-off bottlenecks and the points where users abandon their path.

This dashboard splits into three key parts:

This part gives you the macro state of user journeys at a glance. Imagine you want to know how much users explore your site after arriving; Multi-page Sessions tells you what share continue past the landing page, Avg. Journey Depth tells you how many pages they see on average, and Top Entry Point tells you where they mostly arrive from — the homepage or directly on an article.

This part pictures the real flow of user movement. User Journey Map shows each step as a column and each page as a rectangle; each flow's thickness shows user volume, and the exit point's distinct color reveals exactly where traffic drops off. The map's controls include Steps (path depth from 2 to 6, default 3), Paths (a cap on distinct rendered paths from 10 to 200, default 50; anything beyond rolls into an Other node), and a step filter (pick one page per step so the chart draws only that exact sequence). Alongside the map, two lists — Top Entry Pages and Top Exit Pages — show the site's busiest entry and exit points with exact session counts and share, and Exit vs. Continue puts side by side, in one quick chart, the same ratio Multi-page Sessions measures — exits right after step 1 versus continued browsing.

Journey chains are extracted automatically from each session's pageview order and need no manual setup. The Top Exit Pages list measures the absolute volume of ended sessions, not a percentage rate; so a high-traffic page topping the list isn't necessarily a sign of poor performance. To distinguish pages that share a title, every page is logged by the combination of its title and unique URL. This report identifies the exact drop-off point, not the reason; to evaluate the cause behind an exit, reviewing the user's interaction video in Session Replay at that same point is recommended.