Why Your Bounce Rate Is Misleading (And What to Track Instead)
A 90% bounce rate on your blog is not a problem. A 30% bounce rate on your pricing page might be.
Open any analytics tool and bounce rate sits near the top of the dashboard, glowing red because it's 78%. Your first instinct is that something is broken. Your second instinct is to spend an afternoon "reducing bounce rate" — adding related articles, sticky CTAs, and a popup or two.
For most SaaS and content sites, this is a wasted afternoon. Bounce rate as it's usually defined doesn't measure what people think it measures, and optimising for it leads to worse user experiences. Here's what it actually represents, why it lies, and the metrics that are worth tracking instead.
What bounce rate actually measures
The classic definition is simple: a bounce is a session with exactly one page view. Bounce rate is the percentage of sessions that bounce.
That's the entire signal. It tells you nothing about whether the visitor read the page, scrolled, clicked, signed up, or forwarded the link to a colleague. A visitor who lands on your pricing page, reads it for four minutes, copies the URL into Slack, and closes the tab is recorded as a bounce, identical to a visitor who hit the back button after 200 milliseconds.
Why it's usually high — and usually fine
A high bounce rate is structural for several legitimate page types. Before you treat it as a problem, ask which of these you're looking at.
// blog posts
80–95% bounce — fine
Someone lands from Google, reads the article, leaves. There is no second page they were supposed to visit. A blog with a 30% bounce rate means most readers aren't actually finishing the post — they're hunting for the answer somewhere else on your site.
// documentation
75–90% bounce — fine
Visitors arrive at exactly the page they need from a Google search, get the answer, and leave to go implement it. Counter-intuitively, a low bounce rate on docs often means your search-engine match is wrong.
// landing pages with one CTA
60–80% bounce — fine
A landing page is supposed to do one thing: send the visitor to signup or close the tab. Sessions that go to signup are not bounces but they leave the marketing site, so they often look the same in analytics.
// pricing page
30–60% bounce — investigate
On pricing, you want visitors to either click 'start trial' or click another product page to learn more. A high bounce here suggests either pricing shock or a confusing CTA. This is the rare case where bounce rate genuinely correlates with a problem.
// signup flow
under 30% bounce — investigate
People rarely land directly on a signup form. If they do and bounce, the source is probably wrong (a deep link from outdated marketing, a bot, a stale referrer). High bounce here is a tracking problem, not a UX problem.
The GA4 plot twist
GA4 quietly redefined bounce rate in 2022 and most teams haven't noticed. The new definition is the inverse of engagement rate: a session is "engaged" if it lasts longer than 10 seconds, fires a conversion event, or has at least 2 page views. Bounce rate is now everything that isn't engaged.
This means GA4's bounce rate is no longer comparable to Universal Analytics' bounce rate, and it's also not comparable to bounce rate in any other tool. If you're reading a number labeled "bounce rate", the first question is which definition the tool uses — single-page-view or time-and-engagement-based.
What to track instead
The metrics that actually answer "is this page working" depend on what the page is supposed to do. Here is a quick map.
| page type | what to track | why it's better |
|---|---|---|
| Blog post | Engaged time, scroll depth | Distinguishes a 4-minute read from a 4-second misclick |
| Documentation | Time on page, exit-then-return rate | Captures the 'find answer, implement, return' loop |
| Landing page | Click-through to signup | Bounce rate counts signups as exits; CTR counts them as wins |
| Pricing | Click-through to signup or contact | Direct measure of intent, not session length |
| Signup flow | Step completion rate | Tells you which field is killing conversions |
| Whole site | Revenue per visitor by source | The only metric that closes the loop end-to-end |
The two metrics that actually matter
If you only have time to look at two numbers each week, these are the ones that catch real problems early:
Engaged time per page
Total seconds spent actively on a page (with the tab visible and the user interacting). This separates 'read the post' from 'closed the tab in 2 seconds' without any of bounce rate's noise.
Revenue per source
If you sell something, the source that drives the most revenue per visitor is the source you should be investing in — regardless of bounce rate, session length, or any other vanity metric. Connect your payment processor and this number tells you everything.
What to do with bounce rate
You don't need to remove it from your dashboard. As a single number, it's a weak signal — but as a per-page comparison within a category, it's useful. If one of your blog posts has a 95% bounce rate while the rest are at 80%, that's probably because the post is answering the wrong query. Investigate the deviation, not the absolute number.
The only real mistake is treating bounce rate as the headline health metric for your whole site. It isn't. It never was.
The bottom line
Bounce rate is a 1995 metric in a world where most pages are designed to do their job and let the visitor leave. Track engaged time for content, click-through for landing pages, and revenue per source for the business as a whole — and let bounce rate go back to being a footnote.
Track what actually matters
Datibase shows engaged time, top sources, and revenue attribution in one dashboard — no bounce rate panic, no consent banner.
Try Datibase free