How to Do Funnel Analysis: Steps, Metrics and Finding Why Users Drop Off

To do a funnel analysis: define the outcome, list the three to six steps users take to reach it, set a conversion window, then measure the completion rate and drop-off at each step. Segment the result by source, plan and device, rank the leaks by lost users multiplied by their value rather than by percentage, and find out why users abandoned the worst step before you change anything. The measurement takes an afternoon. The diagnosis is where the value is.

Funnel analysis is the most-used and most-misused technique in product analytics. Most teams can build the chart. Far fewer get past the moment where someone points at the biggest cliff and asks why, because the funnel itself has no answer to that question. This walkthrough covers how to build a funnel that is actually decision-grade, and how to close the gap between seeing a drop-off and knowing its cause.

What is funnel analysis?

Funnel analysis measures how many users move from one defined step to the next in a sequence, and where they stop. A trial funnel might run visit pricing, start signup, verify email, connect a data source, run first report. Each step has a conversion rate to the next, and the whole funnel has an end-to-end rate. The shape shows you where users leave.

The technique is popular because it is intuitive and available in every analytics tool. The trap is that a funnel is a model you invented, not a fact about your users. Define the steps badly, pick the wrong window, or include traffic that was never going to convert, and you get a confident-looking chart pointing at the wrong problem.

Step 1: Define the outcome and work backwards

Start at the end. Pick one outcome that matters to the business: a paid conversion, an activated account, a completed checkout, a second-week return. Then list only the steps a user must complete to get there. The temptation is to include every event you track. Resist it, because each extra step adds a place for the funnel to look broken when it is not.

Three to six steps is the useful range. Fewer than three and you learn nothing you did not already know from a conversion rate. More than six and the chart becomes a staircase where every step loses a little and no single leak stands out. If you genuinely need more detail, build a short top-level funnel first, then a separate deep funnel for the step that turns out to be the problem.

Step 2: Choose a conversion window that matches real behavior

A conversion window is how long a user has to complete the next step before the tool counts them as dropped. This single setting can swing a funnel's numbers by tens of percentage points, and it is the most common reason two people report different conversion rates for the same funnel.

Match the window to how the product is actually used. A checkout funnel should probably allow an hour, because nobody buys a week later in the same session. A B2B onboarding funnel that requires an admin to invite a colleague may need a two-week window, since real teams do that work across several days. Look at the actual distribution of time between steps and set the window near the point where the curve flattens, then keep it fixed so your trend stays comparable.

Step 3: Measure completion and drop-off at each step

For every step, you want three numbers: how many users reached it, the conversion rate to the next step, and the absolute number lost. The percentage tells you how bad a step is. The absolute number tells you how much it costs you, and those two often disagree.

In this funnel, the verify-to-connect step is both the worst rate and the biggest absolute loss, so it is unambiguously where to look. That agreement is convenient and not typical. When percentage and volume disagree, follow the volume, weighted by how valuable those users are.

Step 4: Segment before you conclude anything

An aggregate funnel is an average, and averages hide the thing you need to see. Break every funnel by at least three cuts: acquisition source, plan or account type, and device. A 61% step often turns out to be 80% for one channel and 22% for another, which changes the fix completely. In that case you do not have a step problem, you have a traffic-quality or expectation problem, and redesigning the step would have wasted the sprint.

The other cut worth running is new versus returning cohorts over time. If your funnel is stable in aggregate but each month's new cohort converts a little worse, something upstream is degrading and the blended number will not show it for another two quarters. That is the point where a funnel stops being the right report and you want a cohort analysis instead, since it holds cohort age constant and makes the trend readable.

Step 5: Rank the leaks by what they cost

Order your opportunities by users lost multiplied by their expected value, not by the size of the percentage drop. A 12% loss at a step 40,000 users reach is worth far more than a 65% loss at a step 300 reach, even though the second one looks alarming on the chart. If your plans differ in price, weight the loss by plan, because losing enterprise-sourced signups at a low rate can outweigh losing self-serve signups at a high one.

This one reordering is usually the highest-value output of the whole exercise. Teams that skip it end up fixing the most visually dramatic step in the chart, which is frequently a low-traffic edge of the product.

Step 6: Find out why users dropped off

Here is where most funnel analysis stops and most of the value is lost. The chart shows the leak. It cannot distinguish between the four reasons users actually leave a step:

• Friction: the step demands too much work, asks for information the user does not have yet, or breaks on certain devices.
• Unclear value: the user does not yet believe the next step is worth doing.
• Mismatched expectation: the traffic arriving was never a fit, so the drop-off is a marketing signal, not a product one.
• Technical failure: an email that never arrives, a timeout on a specific integration, an error visible only to a subset.

All four produce an identical-looking cliff. The usual first instinct is to reach for session replay and watch a few abandonments, which is useful for spotting a broken control but slow at proving how widespread the problem is. The way to tell the four apart at scale is to read what the users who dropped actually said. Their support tickets, exit survey answers, in-app comments and reviews usually name the barrier plainly, and when you cluster those by theme you can see whether it affects 200 users or 2,000. If the same cohort that abandoned the verify step also filed tickets about missing verification emails, you have a deliverability bug, not a UX problem, and no amount of copy testing would have found it.

This is the loop a funnel analysis tool should close for you: measure the drop-off, attach the themed feedback from the users who stalled at that exact step, and rank the causes by the revenue behind them. When the leak is genuinely about the page itself rather than the product, it is worth running a focused audit of the copy, layout and calls to action on that step before rebuilding it, since wording and hierarchy fixes are far cheaper than a redesign.

Step 7: Change one thing and re-measure the same funnel

Once you have a named cause, fix it and watch the same funnel definition, with the same window and segments, over a comparable period. Changing the funnel definition at the same time as the product is how teams end up unable to tell whether anything improved. Keep the measurement stable so the only variable is the change you shipped.

Give it enough time to accumulate a meaningful sample at the step you touched, and check the downstream steps too. Removing friction at one step sometimes just relocates the drop-off, which is a real result: it means the users you rescued were never qualified for the next step either.

Common funnel analysis mistakes

Treating the funnel as linear when users are not. Real users skip steps, return days later, and sometimes complete them out of order. If a large share of converters never hit step two, your model is wrong, not your users.

Comparing your rate to a published benchmark. Broad references put self-serve trial-to-paid conversion somewhere in the 15% to 25% range, but the step definitions behind any published figure are almost never yours. Compare against your own trend and across your own segments instead.

Only measuring the happy path. The users who dropped are the entire subject of the analysis. If your instrumentation only fires on success, you can see that people left but nothing about what they encountered on the way out.

Analyzing the funnel without the voice. A drop-off rate is a symptom. Deciding what to build from symptoms alone is guessing with extra steps, and it is why so many funnel-driven redesigns move the number by nothing.

Turning a funnel into a decision

The version of this work that pays off looks like a short document: here is the funnel, here is the step costing us the most in absolute users and revenue, here are the three reasons those users gave in their own words, here is the count behind each reason, and here is the one we are fixing first. Everything above is in service of producing that.

If you want the reasons to arrive with the numbers instead of chasing them across three tools, that is exactly what unified customer analytics software is for, and it is the same discipline that drives product adoption work once users are past signup. For the metrics that sit around your funnel, our rundown of product analytics metrics covers what to track alongside it, and if the drop-off you find is late in the lifecycle rather than early, reducing churn is the same method applied further down the journey.