The funnel is a filing system, not a map

Here is something odd about the way most teams talk about their data: they describe movement through a funnel, but almost nobody moves through a funnel. People loop. They skip. They vanish for three weeks and reappear on a pricing page at midnight with no referrer. The funnel is not wrong, exactly. It is just a filing system — a way to sort people into buckets after the fact. It tells you where someone ended up. It does not tell you how they got there, or why.

We have been studying engagement sequences across a few hundred B2B journeys, and the pattern that keeps surfacing is not a funnel shape. It is a thread. A single concern that a person carries from their first visit to their last, expressed differently at each touchpoint but recognizably continuous if you read the whole arc. We have started calling it the through-line, borrowing from screenwriting, because that is what it feels like: not a stage progression but a narrative question the visitor is trying to answer.

Take a real example. One SaaS company we looked at had a visitor who hit their blog post on API rate limits, left, came back nine days later to the integrations page, left again, returned four days after that directly to pricing, then started a trial. In the funnel view, this person moved from awareness to consideration to decision — three clean stages. But the through-line was one thing the entire time: can this tool handle our throughput at scale? The blog post was about limits. The integrations page was about architecture. The pricing page was about whether the plan that could handle their volume was affordable. Three "stages," one question.

This matters because how you read the journey determines what you do about it. The funnel read says this person converted and took 13 days, which is above average, so maybe we should shorten the cycle. The through-line read says this person needed to resolve a specific technical anxiety before they could buy, and the site answered it — eventually, accidentally, across three pages that were never designed to work together. The intervention is completely different. In one case you try to speed people up. In the other you make the answer easier to find.

Most analytics stacks are not built to surface through-lines. They are built to count events, attribute channels, and score leads. The event stream is the raw material, but the interpretation layer — the part that connects "read blog post about rate limits" to "checked enterprise pricing tier" and recognizes them as the same concern — barely exists in most tools. What sits in its place is either a human analyst doing it manually in a spreadsheet, or a lead score that compresses the whole narrative into a number. Neither scales. Neither reads.

The objection we hear most often is that this sounds like intent data, or like the predictive scoring that half a dozen vendors already sell. It is not. Intent data tries to tell you that someone is likely to buy. A through-line tries to tell you what they are trying to figure out. The difference is the difference between a probability and a story. Probabilities are useful for prioritizing a sales queue. Stories are useful for knowing what to say when you get there.

There is a real limitation to acknowledge. Not every journey has a clean through-line. Some visitors are genuinely browsing. Some are competitors. Some are bots. The pattern does not explain 100 percent of traffic, and claiming it does would be dishonest. In our data, roughly 40 to 60 percent of journeys that reach a meaningful depth — say, three or more sessions — show a readable through-line. That is not universal coverage. But it is the 40 to 60 percent that matters most, because these are the people who are actually trying to decide something.

The deeper issue is that the funnel became the default unit of analysis not because it best describes buyer behavior, but because it best describes organizational structure. Marketing owns the top, sales owns the bottom, and the funnel gives everyone a stage to optimize. The through-line does not map to org charts. It cuts across them. Which is probably why it has been so slow to get adopted as a framework, even though anyone who has watched a real person navigate a website recognizes it immediately.

If you have ever sat behind someone in a usability test and watched them ignore your carefully designed "journey" to follow their own question across six pages you never expected them to visit in that order — you have already seen a through-line. The data just needs to catch up to what observation already knows.