funnel
A funnel is a series of steps a visitor is expected to move through toward a goal, such as landing on a page, then calling, then booking, tracked so you can see exactly where people drop off.
A funnel is a set of steps laid end to end, each one narrower than the last, showing how many people made it from one to the next. Picture a hundred visitors landing on a service page. Forty of them scroll far enough to see the phone number. Ten of them tap it. Three of those calls turn into a booked job. That sequence, a hundred, forty, ten, three, is the funnel.
The point of building it is not the shape, it is the drop. Every step loses people, and the step where you lose the most tells you exactly where to spend your attention. A funnel that leaks at the very first step has a different problem than one that leaks at the last step, and the fix is different too.
Funnels are built out of events, one event per step, in the order you expect people to take them. Without events defined cleanly first, there is nothing to build the funnel out of.
Why it matters to you
Most business owners look at a website and ask “is it working.” A funnel turns that vague question into a specific one: where, exactly, are the people I am paying to attract falling away. That is a far more useful question, because it points straight at the fix.
It also stops effort from going to the wrong place. If a landing page gets plenty of traffic and plenty of phone taps but very few of those calls turn into bookings, the fix is not a better ad or a faster page. It is what happens on the phone. A funnel keeps you from redesigning a page that was never the problem.
How I set it up
I define the funnel around the real path a customer takes for that business, not a generic template. For a service business that usually means landing page to phone tap or form submission to booked job. For a content or membership site it might be different steps entirely. I build the events first, then wire them into a funnel report in Google Analytics or PostHog.
I keep funnels short. A funnel with eight steps looks thorough but usually just spreads a small amount of traffic across too many boxes to draw a real conclusion from any single one. Two or three steps that map to real decisions a visitor makes gives you a much clearer picture.
What it looks like in practice
In a monthly report, a funnel shows up as a short list of numbers narrowing from top to bottom, with a drop-off percentage between each step. It is one of the few analytics views where the fix is often obvious just from looking at it: a big drop between two adjacent steps means look at what stands between them.
When I make a change meant to fix a leak, a new headline, a shorter form, a clearer call button, the funnel is where I check whether it worked. If the drop at that step gets smaller the next month, the change did its job. If it does not move, the fix was aimed at the wrong step.
Questions I get about this
- What is a good number of steps for a funnel?
- As few as the business actually needs. Landing page to phone tap is a two-step funnel and often enough. A longer sales process with a quote request, a follow-up call and a signed job might justify more steps, but every extra step is another place to lose people, so I do not add steps for the sake of detail.
- What does it mean if most people drop off at the first step?
- It usually means the page itself is not doing its job, either the offer is not clear, the page is slow, or the wrong people are landing on it in the first place. That is different from dropping off at the last step, which usually points at the form or the booking flow.
- Can a funnel tell me why people are dropping off, not just where?
- Not by itself. A funnel shows you the where. Finding the why usually means looking at session recording and heatmaps for that specific step, or just reading the page again with fresh eyes.
Want this set up properly for your business?
This is the kind of thing I build every week. Grab a time and we will talk through what fits.