Funnel Analysis for Designers: Where People Drop Off and How to Read It
A funnel analysis measures what share of users completes a sequence of steps and where they leave. How to define steps, set the window, and read the results.
What is a funnel?
A funnel is an ordered list of events that represents an important path: landing on a product page, adding to cart, paying. Each step is an event that someone triggers in the product. The analysis counts how many users enter the first step and how many reach the next ones.
Amplitude defines it as the count of users who complete a defined sequence of events, in order, within a time limit (Amplitude, “Funnel analysis: interpret”). The total conversion is the percentage of those who entered who reached the end.
Why should a designer care?
Because a flow you designed has the shape of a funnel, and you usually know which step worries you but not how much it costs. The funnel gives you the number. If 40% of the people who reach “shipping details” don’t move on to “payment”, the conversation changes: you’re no longer arguing about whether the form looks good, but about what it asks for and when.
It also protects you from easy conclusions. A total conversion of 3% can hide one step with a huge drop and another that is nearly perfect. Looking at the funnel step by step keeps you from changing the wrong screen.
How do you define a good funnel?
Three decisions define the quality of the analysis:
- The steps. DoubleTick recommends three to five events. Each step should follow the previous one on a logical path. Mixing unrelated events produces a number nobody can interpret.
- The order. A step may happen before another in real life and after it in the product. Tools such as Amplitude offer three options: this order (other events may happen between steps), any order, or exact order (no events in between). Pick one and document the decision.
- The conversion window. Amplitude sets it to one day by default and allows between one second and 90 days. DoubleTick recommends matching it to the typical behavior of your users. If the window is too short, you lose people who buy slowly; if it is too long, you count conversions that have nothing to do with the flow.
How do you read the drop-off?
A funnel has two useful readings:
- The absolute loss, how many people leave at each step. It measures the volume of the problem. If 1,000 people reach the payment step and 600 leave, that weighs more than a 30% drop at a step that only receives 50 people.
- The relative loss, what share of those who reached a step leave. It tells you which step performs worst, regardless of its size.
Describing its largest drop-off step, Amplitude says the relevant comparison is the absolute decrease, not the percentage decrease. It is worth looking at both: the absolute for prioritizing, the relative for understanding the quality of the step.
Example
Illustrative example: a booking app has a four-step funnel. 10,000 people enter the search; 6,000 pick a time slot; 2,400 reach customer details; 900 book. Total conversion is 9%. The step with the largest absolute loss is customer details: 1,500 people leave. When segmented by device, that step looks fine on desktop and very poor on mobile. The hypothesis changes: the form is the problem on mobile. The funnel doesn’t say why people leave. For that, the team reviews session recordings and interviews a few people who abandoned that step.
Which readings mislead?
- Looking only at total conversion. It hides the step that loses the most.
- Not segmenting. A 70% overall rate can hide 45% on mobile. Compare by device, source, and user type.
- Forgetting that a funnel only sees people who entered. Someone who arrived through another route doesn’t appear. The analysis describes those who already started, and that biases any conclusion you draw.
- Trusting badly instrumented events. A duplicated or badly named event creates a leak that doesn’t exist. Verify the tracking before changing the product.
- Acting on small samples. A step with few users can swing a lot from week to week. Wait for volume.
When NOT to use a funnel
- To explain why people leave. The funnel shows where, not why. Combine it with heatmaps and session recordings or interviews.
- In flows without a clear sequence. If people can do the steps in any order, a funnel forces a reading that doesn’t exist.
- To measure satisfaction. A funnel measures behavior. Satisfaction requires asking.
- If the tracking isn’t reliable. A funnel built on bad data is worse than having no funnel.
Common mistakes
- Defining steps that don’t reflect what the person actually did.
- Changing the conversion window in the middle of the analysis.
- Comparing periods with different seasonality without saying so.
- Ignoring absolute loss and prioritizing by percentage.
- Treating a problem as real without checking the tracking.
How to start tomorrow
Pick the flow that worries you most and write its steps in a list of four at most. Agree on the conversion window with your team and write it down. Build the funnel in your analytics tool, for example Amplitude or Mixpanel, and look at the absolute loss at each step. Then segment by device. Write down the hypothesis before you change anything, and check with cohort analysis whether people who arrive after the change behave the same way.