A traffic graph going up and to the right feels like progress. The P&L doesn't care about sessions, it cares about what those sessions actually turned into, and those two numbers respond to different things.
Traffic Isn't One Thing
The first problem with treating "traffic" as a single number is that it isn't one. Contentsquare's Digital Experience Benchmark, published March 2026 from 99 billion sessions across more than 6,500 sites, found conversion rates that vary enormously depending on where a session came from: paid search converted at 2.8%, returning visitors at 2.9%, new visitors at only 1.7%, and organic social traffic at just 0.7%. A blended traffic total can grow entirely from the lowest-converting sources while the actual number of buyers stays flat or even shrinks. Two businesses with identical total-session counts can have completely different revenue outcomes depending on the mix behind that number.
A "Session" Is a Lower Bar Than It Sounds
Google's own GA4 documentation defines an engaged session as one lasting longer than 10 seconds, containing a key event, or including at least two pageviews. Anything that doesn't clear that bar counts toward the bounce rate instead. That's a genuinely low threshold, and it means a rising "traffic" number can include a large, growing share of visits that barely registered at all, let alone moved anyone closer to a purchase decision.
Vanity Metrics vs. Actionable Metrics
Digital analytics expert Avinash Kaushik has spent years making a version of this same argument: stop chasing metrics that just report what happened, and start tracking the ones that explain why it happened and what to actually do about it. His framework groups metrics into three categories, Behavior (pageviews, paths, time on site), Outcomes (conversions, sales, qualified leads), and Experience (repeat visits, feedback, satisfaction), and argues a metric only earns a place on a dashboard if it can genuinely change a decision. Raw traffic, on its own, rarely does.
Why the Gap Shows Up So Often
A few specific, common causes. Ranking for informational queries that attract visitors who were never going to buy anything, which grows traffic without growing revenue potential. A reporting layer that doesn't actually reconcile with what's happening in a CRM or payment processor, a real, common pattern covered in more depth in our Website Health Scorecard's Analytics factor. And simply treating every session as equally valuable in a report, when the data above shows they clearly aren't.
What This Means for How a Report Actually Gets Read
A marketing report built around total sessions and a finance team looking at the P&L are effectively speaking two different languages, and the disconnect isn't anyone being dishonest, it's that the two documents were built to measure different things. The practical fix isn't to stop reporting traffic entirely, it's to stop presenting it as the headline number and start showing it next to what it actually produced: leads, qualified conversations, or sales, broken down by the source that generated them. Once that pairing exists, a traffic increase either shows up as a revenue increase too, or it becomes obvious exactly where the gap is instead of staying hidden inside one blended total.
Want to know which of your traffic is actually driving revenue?
Get Your Visibility Audit →Frequently Asked Questions
Why doesn't more traffic automatically mean more revenue?
Because traffic isn't one uniform thing. Contentsquare's March 2026 Digital Experience Benchmark, drawn from 99 billion sessions, found conversion rates vary enormously by channel: paid search converted at 2.8%, returning visitors at 2.9%, new visitors at only 1.7%, and organic social traffic at just 0.7%. A session from one source can be worth several times more than a session from another, so a rising total-traffic number can hide a shrinking or flat number of actual buyers.
What counts as a "session" in Google Analytics, and does that matter?
Google's own GA4 documentation defines an engaged session as one lasting longer than 10 seconds, that has a key event, or that has at least two pageviews; anything short of that counts toward the bounce rate instead. That means "traffic" as a raw number includes a large share of visits that never crossed even that low bar, let alone got close to a purchase decision.
What's the difference between a vanity metric and an actionable metric?
Digital analytics expert Avinash Kaushik's widely used framework distinguishes metrics that just report what happened (like raw pageviews or session counts) from those that reveal why it happened and what to do next. He groups useful metrics into Behavior, Outcomes, and Experience, and argues a metric is only worth tracking if it can actually change a decision.
Why do traffic and revenue often move in different directions?
A few common causes: ranking for informational keywords that attract visitors with no buying intent, a reporting layer that doesn't match what's actually happening in a CRM or payment processor, and treating every visit as equally valuable when different traffic sources convert at very different rates. Each of these can make a traffic chart look healthy while revenue stays flat.
What should a business track instead of just traffic?
Metrics tied to an actual outcome: qualified leads or sales by channel, conversion rate by traffic source rather than blended across all of them, and whether analytics numbers reconcile with the CRM or payment processor. A full practical breakdown of which specific metrics to track is covered separately.