Why improving funnel analysis is worth the effort
Funnel analysis follows scanners through each step from exposure to conversion: seen, scanned, page loaded, action started, action completed. It shows exactly where people drop out, so fixes go to the step that leaks most.A funnel with only two steps hides the problem. Break the journey into the real steps a scanner takes.
Diagnose before you change anything
Improvement starts with diagnosis, not with redesign. Before changing a code, split funnel analysis by placement, device, step, and week and look for the weakest segment. The weakest segment is where a fix buys the most, because it holds the largest pool of lost value. Also check the steps around funnel analysis: a problem upstream, such as poor placement, can masquerade as a problem with the code itself, and a problem downstream, such as a slow landing page, can waste scans that were earned fairly. Fix the constraint, not the symptom.Write down your diagnosis in one paragraph before you touch anything. State what you observed, which segment is weakest, and what you believe is causing it. This paragraph is your hypothesis, and it keeps the work honest: if the fix does not move the number, the hypothesis was wrong, and you learn something instead of merely changing things.
Levers that move funnel analysis
- Fix the largest leak first, since that is where the most people are lost. - Shorten the step with the worst conversion before redesigning the whole page. - Remove distractions on the step where scanners hesitate.Work through the levers in order of expected impact per unit of effort. A lever that costs nothing and affects every scanner beats a lever that costs a print run and affects one placement. For each lever, state the change, the cost, and the segment it should move, then implement only that change. Bundling several changes together feels productive, but it destroys your ability to learn which one worked.
Test the change properly
Step conversion = people who reach a step divided by people who reached the previous step, multiplied by 100. Overall conversion = conversions divided by exposures, multiplied by 100.Illustrative example numbers, not real-world data: 5,000 exposures lead to 400 scans, 120 action starts, and 60 completions. Scan-to-start is 120 / 400 x 100 = 30%, and start-to-complete is 60 / 120 x 100 = 50%, so the bigger leak in this example is between scan and start.
Run the change as a comparison wherever you can: the old version against the new version, on comparable placements, over the same kind of period. Keep everything else stable, and decide in advance how long the test runs and what counts as a win. A test that ends the moment one variant pulls ahead is not a test, it is a reaction. If traffic is too small for a formal test, change one thing, record the before and after numbers, and treat the result as suggestive rather than proven.