Most reporting treats traffic as if it were the thing of value. Sessions, clicks, cost per click, source, campaign, conversion rate — the dashboard measures movement. It tells you how many people arrived and, eventually, how many of them did the thing you wanted. What it doesn't tell you is what any of them actually wanted when they got there.
That gap matters more than it gets credit for. Two visitors can arrive through the same channel — same keyword, same ad, same landing page, same time of day — and be carrying completely different situations. One is comparing three options and wants proof this will work for their specific case. Another already knows what they need and is checking price. A third isn't sure the problem is worth solving yet. The traffic report can't tell these apart. It records the same source, the same page, the same eventual outcome column. The people were never the same visit.
This is the distinction worth sitting with: traffic is transport. Intent is cargo. A revenue path that only measures the transport is optimizing the wrong layer of the system.
The honest reason we measure traffic instead of intent is that traffic is easy to see and intent is not. Every ad platform and analytics tool was built to count things that happen at a click or a page load. None of them were built to answer what a specific person actually came to figure out. So teams optimize what the tools show them — more visits, cheaper visits, higher-converting visits — rather than the harder, less visible question of what's arriving underneath the visit.
That isn't a criticism of measurement. Movement is real and it costs real money. But movement is a proxy, and proxies eventually get treated as the target. A team that spends a year improving click-through rate and conversion rate can still be surprised to learn that a meaningful share of their "qualified" traffic never had a realistic path to converting — not because the page was weak, but because the path never asked what that visitor was actually trying to accomplish.
Most revenue paths are built around a small set of questions: where did this person come from, what page are they on, did they convert. These are useful operational questions. They are not the same as understanding the visitor. A narrower and harder question is more useful: what is this person actually trying to accomplish right now? Not which segment they belong to in aggregate, but what situation brought this specific visit into existence. Sometimes the answer is obvious from context — a branded search for a return policy isn't ambiguous. More often it's a mix of signals that only mean something read together: how someone arrived, what they're spending time on, what they've already seen, what they haven't done yet. No single signal is definitive. Together, they start to describe a situation.
When a path is built around "where did they come from and did they convert," it tends to treat every visitor from a given source the same way, regardless of what they actually need from the page. That flattening is where value quietly leaks — the visitor who needs proof this fits their specific circumstance gets the same generic credibility messaging as someone already sold, and the one still deciding whether the problem is worth solving gets pushed toward a purchase decision they aren't ready to make. Neither failure looks like a bug. The page loads. The funnel reports normally. The intent just never got answered.
I want to be careful here, because it would be easy to overstate this. Intent is often genuinely uncertain. The signals available are incomplete, and inferring what someone wants from a handful of behavioral traces isn't a solved problem — it's closer to an ongoing judgment call than a formula. Personalizing everything for everyone isn't automatically an improvement either; it can just as easily add complexity without adding accuracy. Not every visitor needs a bespoke journey, intent can't be read perfectly, and this isn't a problem anyone has fully solved, including us.
What follows instead is more modest: when a revenue path responds more accurately to the actual situation someone is in, there's reason to expect room for better outcomes — stronger matching between visitor and offer, better use of acquisition spend that's already being paid for. Whether that room turns into results is a question for evidence, not assumption — which is exactly why testing and measurement matter here: the only credible way to close that gap is to test a specific hypothesis against real behavior and look at what the economics say afterward.
This also changes the order of the optimization question. When a revenue path underperforms, the instinct is almost always to ask how to get more traffic: a bigger budget, a new channel, a broader audience. That's sometimes the right move. But it's worth asking first what intent is already being attracted, and what actually happens to it once it arrives. A path that doesn't understand the intent it already has is unlikely to do meaningfully better with more of the same intent arriving faster.
Traffic carries intent. Intent encounters a revenue path. Whether that path recognizes the situation someone is actually in has a lot to do with the economic outcome that follows — and that's the layer worth understanding before spending more to bring in additional traffic.
It's also why T/M/Digital starts a revenue path engagement by trying to understand the intent already arriving, rather than assuming the answer is simply more of it.
Apply this thinking to your revenue path.
Get your Revenue Path Brief — $295 →