Funnels

Define the steps of a flow and see where people fall out of it.

A funnel turns a vague worry into a number attached to a step. "Checkout feels bad" becomes "62% of people who reach payment never submit it", which is something you can act on.

Build one from events you already send

A funnel is an ordered list of steps, each matching a page view or an event. Conversion is measured between consecutive steps, so the shape of the drop-off tells you where to look.

Which means the quality of your funnels is decided by the quality of your event names — this is what custom events buy you. Autocapture knows a button was clicked; only your app knows a subscription was created.

The drop is a starting point, not a finding

The number tells you which step loses people. It does not tell you why. Once you have the step:

  1. Filter Replays to sessions that reached that step and did not continue.
  2. Watch a handful. Patterns show up faster than you expect.
  3. Check Issues for a Behavior or Runtime issue on the same page — a dead click on the submit button explains a lot of drop-off.

Saved funnels persist, so the same definition is there next week and the comparison is honest.

Ask about it instead

You can also ask Home about a funnel in plain language, and have an agent watch it on a schedule and message you when a step degrades.