Funnel analysis: finding the leak
Funnel analysis follows visitors through an ordered set of steps (view → add to cart → checkout → purchase) and shows where they fall out. It turns a single conversion rate into a map of where the loss happens. The pitfalls are step definition, small-sample noise, and assuming a strict order where users actually skip around.
What this means
A funnel is an ordered list of steps you expect visitors to pass through. At each step you count who reached it; the gaps between steps are drop-off. The biggest gap is usually where to focus.
Reading it honestly
Define steps from real events, not assumptions. Watch sample size: a funnel with a handful of users at the bottom shows wild drop-offs that are noise. And remember real users skip steps, return later, and convert across sessions — a strict linear funnel can overstate 'loss' that is really just non-linear behaviour.
- Biggest drop = where to focus
- Small samples make noisy drop-offs
- Real journeys are non-linear
How it appears in analytics and logs
A big drop between two steps points at friction there — but only if the steps are correctly defined and the sample is large enough. Small funnels produce noisy drop-offs that look like leaks.
Diagnostic use case
Use a funnel to locate the biggest drop-off step, then focus effort there — while checking that the step counts are large enough to trust.
What WebmasterID can help detect
WebmasterID's event model lets you define funnel steps from your own events and read drop-off without cross-site tracking.
Common mistakes
- Reading small-sample drop-off as a real leak.
- Defining funnel steps from assumptions, not events.
- Forcing a strict order onto non-linear behaviour.
Privacy and accuracy notes
Funnels aggregate step completion from events; they need no personal identity. WebmasterID builds them from first-party events.
Related pages
- Conversion rate: definition and denominators
Conversion rate is the share of some base that converted. The trap is the denominator: conversions per session, per user, and per unique visitor give different numbers and mean different things. Without stating the base, a conversion rate is ambiguous — and comparing rates with different bases is meaningless.
- The page_view event: the base of web analytics
page_view is the event fired when a page loads. It is the base of almost every web-analytics model: sessions, pageviews, and most reports build on it. In classic sites the tracker fires it automatically on load; in single-page apps you fire it on each route change. Its properties (path, title, referrer) drive most downstream reports.
- Analytics sampling: when reports estimate
Sampling is when an analytics tool computes a report from a fraction of the data and extrapolates. It keeps big queries fast, but it adds estimation error — worst for small segments and rare events, where a few sampled sessions get scaled into a confident-looking number. Knowing when a report is sampled is the first defence.
- Event Explorer
Investigate where visitors drop in the funnel.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.