Paths

Paths show how readers move after they arrive: the journeys they repeat, the pages that start and end a visit, and the 404s that interrupt them.

Journeys

Dashboard > Paths lists repeated page sequences for the current window. Each journey has a visitor count so you can see whether traffic concentrates on one route or spreads across many. / → /docs → /docs/start

Journeys group same-day events with the daily visitor bucket. They are not a durable identity across days. Sequences exist only inside the 90-day pageview window; a longer range returns 400. Entry and exit totals stay available as daily counts for three years. See privacy for how that bucket is derived. Privacy

Entry and exit

The same view breaks out entry pages and exit pages. Entry is where a visit starts. Exit is where it ends. Use the two together: a strong entry that also absorbs most exits is a different problem from a strong entry that feeds a longer route.

Filters for country, device, and source apply to journeys and to entry/exit, so you can ask whether one campaign dumps people on a dead-end page.

404s

Dashboard > Broken routes lists missing paths, how many visitors hit them, and which sources sent those requests. Use it after a docs move or a nav refactor, and again next to a release marker when you want to know whether a ship created new dead ends. Releases

One loud missing path is usually a stale link. A wide spray of 404s often means an old sitemap, a renamed tree, or an external index that never updated.