Metrickle

Follow the paths people really take

See the detours that stop people buying. 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.

Journeys after /checkoutquillmere.example · last 30 days
Where sessions went from checkout, step by step, with the share of sessions leaving each page
StepFromToShare
1 → 2/checkout/checkout/pay58%
1 → 2/checkout/help/vat17%
2 → 3/checkout/pay/checkout/done71%
2 → 3/help/vat/checkout64%
2 → 3/checkout/pay/pricing12%

One in six checkouts detours to the VAT help page, and most come straight back. The checkout form doesn’t say which VAT number it wants.

Anchored where you need it

On every plan, Free included. 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 people using a keyboard or a screen reader, 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. For a path made of events, build a funnel or a task.

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.

After /checkout/pay, by settingquillmere.example · since v4.12
Share of payment-page sessions whose next page was the confirmation, or the payment page again, for each accessibility setting
SettingChartTo confirmationPayment page again
No accessibility settings74%6%
Zoomed in70%8%
Large text52%11%
Keyboard navigation31%44%

Since v4.12, people using keyboard navigation rarely get from payment to confirmation. Their next page is most often the payment page again, after a reload: focus skips “Pay now”.

Journeys that went wrong, already pulled out

Reading a flow chart for problems takes time. When a release breaks a protected task, its case lists 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 group, with recordings from Growth.

Use journeys to explore. Protect a task to be told.

How protected tasks and cases work

From a strange path to a fix

  1. Spot the detour

    Anchor on the step where a funnel leaks and see where people go instead.

  2. Check who takes it

    Split by accessibility setting, device or survey answer, then open the friction on the page they detour to.

  3. Protect it

    Save the task and protect it, and the next release that sends people the wrong way opens a case.

See which release is costing you conversions, and who it broke for

Free to start. One script tag on the web, one SDK on mobile, and no cookie banner in cookieless mode.

Start free