How funnel analysis works
You define an ordered set of steps that lead to something valuable — viewed the service page, opened the form, started filling it, submitted it — and the tool counts how many people reached each one. The result is a staircase, and the height of each drop tells you what the journey costs at that point.
Two settings change the picture more than most people realise. The first is whether steps must happen in sequence or merely at some point in the session: a strict funnel is precise but discards anyone who wandered, while an open one is forgiving and can flatter you. The second is the window. A journey allowed a day looks very different from the same journey allowed a fortnight, and for considered purchases the short window will show a collapse that is really just people taking their time.
Everything downstream depends on the steps being tracked correctly. A step that fires on the wrong page, or a form event that never fires on mobile, produces a dramatic drop-off that exists only in the tracking. Confirm the events before you interpret the shape.
Why funnel analysis matters
A single conversion rate tells you something is wrong without telling you where. The funnel converts that into a location, and a location is something you can brief work against — the page, the form, the delivery step or the payment options.
It also stops money being spent in the wrong place. If most visitors never reach the enquiry form, buying more traffic multiplies the same loss, and improving the step where they leave is much cheaper than replacing them at the top. In markets like Nepal, where payment options and delivery expectations vary, the drop-off often sits at a step nobody in the office thinks about because it works fine on their own device and connection.
Common mistakes with funnel analysis
The first is fixing the biggest drop rather than the most valuable one. The largest fall is often the earliest, where most of the audience was never going to buy anyway; a smaller improvement close to the money can be worth far more.
The second is defining steps around your internal process instead of the customer’s. People do not move in a straight line — they leave, compare, come back on another device and return through a different channel — and a funnel that assumes an orderly path reports abandonment that never happened.
The third is trusting a funnel nobody has tested, and the fourth is reading it in aggregate only. A journey that works on desktop and fails on a phone shows up as a modest overall drop rather than the serious problem it is.
What to do about it
Build the funnel around what the customer is trying to do, keep it to a handful of meaningful steps, and verify each event fires on real devices before you draw conclusions. Then look at the drops in order of value rather than size, and pick one to work on.
Take that step apart with tools that explain behaviour rather than count it: a session recording, a scroll map, or form analytics if a form is involved. The funnel says where; those say why. Then split the same funnel by device and by traffic source, because segmentation of results regularly turns a mild average into an obvious fault in one group. Fix, measure the same steps again, and move to the next drop.
