Follow the paths people really take
Journeys show how people move from page to page, or screen to screen, within a session. Start from any page, see where people go next, and split it by accessibility setting, device, campaign or what they told you in a survey.
| Step | From | To | Share |
|---|---|---|---|
| 1 → 2 | /cart | /checkout | 58% |
| 1 → 2 | /cart | /search | 17% |
| 2 → 3 | /checkout | /checkout/pay | 71% |
| 2 → 3 | /search | /cart | 64% |
| 2 → 3 | /checkout | /delivery-info | 12% |
One in six carts goes to search, and most come straight back. Search is being used as a back button: the cart doesn’t show what people came to change.
Anchored where you need it
Start from session start or from any page or screen, and choose how many steps to follow. Every chart has a table view with the count behind each move, for keyboard and screen reader users and for anyone who wants the numbers.
- Re-anchor on any page: select a page to start the journey there.
- Three to six steps deep, with the smaller paths grouped so the main ones stay readable.
- Top entry pages one click away, and per-visitor session timelines for the detail.
- Web and mobile: pages on the web, named screens in the iOS, Android, Flutter and React Native SDKs.
Whose journey went wrong
The same filters work everywhere, so a journey can be just the people using a keyboard, just the ones on Android, or just the ones who gave checkout a low effort score.
| Setting | Chart | To checkout |
|---|---|---|
| None | 61% | |
| Zoom | 52% | |
| Large text | 49% | |
| Keyboard | 27% |
Keyboard users rarely make it from cart to checkout. Their next page is most often the cart again, after a reload.
Journeys that went wrong, already pulled out
Reading a flow chart for problems takes time. When a held task contract breaks, its case files every attempt that started and then wandered under wrong path: extra screens, search used as a back button, u-turns. The case names the step and the setting, with recordings.
Use journeys to explore. Use contracts to be told.
From a strange path to a fix
Spot the detour
Anchor on the step where a funnel leaks and see where people go instead.
Check who takes it
Split by accessibility setting, device or survey answer, then open the friction on the page they detour to.
Hold it to a contract
Save the task, and the next release that sends people the wrong way opens a case.
Common questions
Do journeys follow people across sessions or devices?
Not yet. A journey covers one session. Linking an anonymous visitor to a signed-in person across devices is on the roadmap. Retention and per-visitor timelines show what happens across sessions in the meantime.
Can a journey include events, not just pages?
Journeys show pages and screens. For a path made of events, such as add to cart and apply coupon, build a funnel or a task: both accept events and pages.
Is the journey chart accessible?
Every page in the chart is a focusable button, and a table view lists every move with its count and share, so nothing depends on hovering with a mouse.
Which plans include journeys?
All of them, including Free.
See where your apps break, and who they break for
Free to start. One script tag on the web, one SDK on mobile, and no cookie banner in cookieless mode.
Get early access