Bounce rate in web analytics is the percentage of website or app sessions that end without meaningful engagement, traditionally a visit that viewed a single page and triggered no further interaction. In marketing analytics, it serves as a quick indicator of how well a landing page matches the expectations of the traffic it receives, and it is reported per page, per channel and per campaign.
The exact definition depends on the analytics tool. In GA4, bounce rate is the inverse of engagement rate, while older tools counted any single-page session as a bounce regardless of how long the visitor stayed. Not to be confused with the email bounce rate, which measures undeliverable messages.
How bounce rate is calculated
Bounce rate is calculated as bounced sessions divided by total sessions, expressed as a percentage. What counts as a bounced session is the crucial part, and it has changed significantly between generations of analytics tools.
In GA4, a session is engaged when it lasts longer than a set threshold, 10 seconds by default and adjustable up to 60 seconds, or includes a key event, or includes at least two page or screen views. Every session that meets none of these conditions is counted as a bounce. Bounce rate therefore equals 100% minus engagement rate.
| Analytics model | Session counts as a bounce when | Main weakness |
|---|---|---|
| Universal Analytics | Only one interaction hit was recorded | Long single-page reads counted as bounces |
| GA4 | The session was not engaged | Threshold choice changes the figure |
| Many other tools | Only one page view occurred | Ignores time and on-page actions |
Because definitions differ, bounce rates from different tools or periods are not directly comparable. A site that migrated from Universal Analytics to GA4 often saw its bounce rate drop noticeably, not because user behavior improved but because the metric itself changed.
Interpreting bounce rate by page type
A high bounce rate is not automatically a problem. Its meaning depends on the purpose of the page and on what the visitor came to do. A visitor who finds an opening time, a phone number or a short answer and then leaves has been served well, even though the session may count as a bounce.
| Page type | Expected bounce behavior | When to worry |
|---|---|---|
| Landing page for a campaign | Should be relatively low | Visitors leave before reaching the call to action |
| Blog article or guide | Often high; reading ends the task | Low scroll depth and very short sessions |
| Product page | Moderate; comparison shoppers leave | High bounce from purchase-intent traffic |
| Contact or location page | High is normal | Rarely a concern on its own |
| Checkout step | Should be very low | Any rise indicates friction or errors |
Published benchmarks for typical bounce rates vary widely by industry, device and definition, so they are of limited use for a single site. The more reliable comparison is the same page over time or similar pages within the same site.
Bounce rate compared with related metrics
Bounce rate is often confused with neighboring metrics that describe different moments of a visit. Each answers a separate question about user behavior.
| Metric | What it measures | Scope |
|---|---|---|
| Bounce rate | Share of sessions without engagement | Sessions that started on the page |
| Engagement rate | Share of engaged sessions | Inverse of bounce rate in GA4 |
| Exit rate | Share of page views that were the last in a session | All sessions viewing the page |
| Average engagement time | Time the page was in the foreground | Engaged sessions or users |
| Conversion rate | Share of sessions completing a goal | All sessions in the segment |
The difference between bounce rate and exit rate matters most in practice. Every session exits somewhere, so a high exit rate on a confirmation page is expected. A bounce, by contrast, describes a session that started and ended without engagement on the same entry page.
Common causes of a high bounce rate
When bounce rate is genuinely too high for a page’s purpose, the cause usually lies in one of a few areas: traffic quality, page experience or tracking errors. Diagnosing the right category first prevents wasted redesign work.
| Symptom | Likely cause | Typical fix |
|---|---|---|
| High bounce from one paid campaign | Ad message does not match the page | Align ad copy and landing content |
| High bounce on mobile only | Slow loading or broken layout | Improve speed and responsive design |
| Sudden jump across the site | Tracking tag removed or duplicated | Audit tags and data layer events |
| Very low bounce rate | Duplicate tag firing two page views | Fix the double implementation |
| High bounce on organic entries | Content misses search intent | Rework content for the actual query |
Suspiciously low bounce rates below a few percent are a classic sign of a tracking error rather than excellent engagement, often caused by tags installed twice through both a hard-coded snippet and Google Tag Manager.
Using bounce rate in marketing decisions
Bounce rate is most useful as a diagnostic signal combined with segmentation. Splitting it by source, campaign, device and landing page using UTM parameters quickly shows which traffic sources and pages underperform.
- Segment before judging; a site average hides very different page and channel behaviors.
- Set a meaningful engagement threshold that fits the content length and purpose.
- Pair bounce rate with conversions so that low-bounce but non-converting traffic is not overvalued.
- Track key on-page actions such as video plays or downloads as events, so engaged visitors are not counted as bounces.
Put simply
Bounce rate shows how many visitors arrive on a website and leave without really doing anything. They do not click, scroll on to another page or stay long.
Imagine people walking into a shop, glancing around and walking straight out. If that happens often, something may be wrong. Perhaps the shop window promised something else. But sometimes they found what they needed at the door, so the number always needs context.
In practice
A travel agency runs a paid social campaign promoting weekend city breaks. In GA4, the campaign’s landing page shows a bounce rate of about 75%, while the same page reached from email has a far lower rate. Segmenting by device reveals that most bounces come from mobile users.
Testing shows the page takes several seconds to load on mobile networks and opens with a large image instead of the advertised prices. The team compresses images, moves the price list above the fold and repeats the ad headline in the page title. Two weeks later, the bounce rate for the campaign falls to around half its earlier level, and booking inquiries from mobile visitors rise noticeably.