What Is Bounce Rate? How GA4 Redefined an Old Metric
Bounce rate is the share of sessions that count as bounces, but what counts as a bounce changed with Google Analytics 4. In Universal Analytics, a bounce was a single-page session that sent only one request to Analytics. In GA4, bounce rate is the share of sessions that were not engaged, and a session counts as engaged if it lasts longer than 10 seconds (the default setting), includes a key event, or includes two or more page or screen views. The same visit can be a bounce under the old definition and an engaged session under the new one, so the two numbers cannot be compared.
The Old Definition
Google’s Universal Analytics help page, now marked as legacy, defined it plainly: “A bounce is a single-page session on your site.” The same page counts the sessions in which users “viewed only a single page and triggered only a single request to the Analytics server,” so a tracked interaction on that page, such as an event for a video play, kept a session from counting as a bounce. Bounced sessions were recorded with a duration of 0 seconds, because no second hit arrived to measure time against. A visitor who read an article for ten minutes and left counted the same as one who left after two seconds.
The GA4 Definition
GA4 starts from engagement. Google’s documentation on engagement rate and bounce rate states: “An engaged session is a session that meets any of the following criteria”: it lasts longer than 10 seconds, has a key event, or has 2 or more screen or page views. Engagement rate is the percentage of engaged sessions, and the page continues: “The bounce rate is the opposite of the engagement rate.”
Google’s own example: a visitor reads a page for less than 10 seconds, triggers no events, views no other page, and leaves. That session is not engaged. “If this were the only session on your website, the engagement rate would be 0% and the bounce rate would be 100%.”
| Universal Analytics | GA4 | |
|---|---|---|
| A bounce is | A single-page session that sent only one request to Analytics | A session that is not engaged |
| Time on the page counts | No | Yes, a session longer than the engagement timer (10 seconds by default, adjustable) is engaged |
| One page view for 15 seconds, no events, default settings | A bounce | Engaged, not a bounce |
| How the rate is derived | Single-page sessions that sent only one request, divided by all sessions | The opposite of engagement rate |
Because a single long page view now counts as engaged, GA4 bounce rates for the same traffic can come out lower than Universal Analytics showed, by an amount that depends on the timer setting and on which events each property tracked. A drop at the time of the migration reflects the new definition, not changed behavior.
GA4 also hides the metric by default: “By default, most reports in Google Analytics do not include the engagement rate and bounce rate metrics.” An editor or administrator can add both to a detail report, such as Pages and screens, through Customize report.
Is Bounce Rate a Ranking Factor?
Bounce rate is a number in your own analytics, calculated from your own tag’s data. It is not a measure Google has documented as a ranking input. The underlying question, whether a page satisfies the searcher, matters to search; the analytics number is one rough way of looking at it, not the thing Google measures.
What Counts as a Good Bounce Rate
There is no universal benchmark, because the right number depends on the page’s job. Google’s old guidance put it directly: a high bounce rate depends on the site, and “if you have a single-page site like a blog, or offer other types of content for which single-page sessions are expected, then a high bounce rate is perfectly normal.” A page that answers one question and lets the visitor leave satisfied is working. A high bounce rate on a cart page or the first step of a sign-up is a problem.
Published industry averages exist from third-party data providers, each with its own sample and method. They describe other sites, not your page’s purpose; compare a page against similar pages on your own site instead.
Why Sessions Fail to Engage
- The page does not deliver what its title or snippet promised.
- The page is slow to become usable.
- The mobile layout is hard to read or use.
- The visitor has no obvious next step.
- The ad, email, or post that sent the visitor promised something else.
Lowering Bounce Rate Without Chasing the Number
- Compare each page’s title and description with what the page delivers, and fix mismatches.
- Speed up what visitors see first.
- Test on a real phone, not only a resized browser.
- Give engaged visitors a relevant next step: related content, the next page in a process, or a specific action.
- Segment by page type and traffic source before drawing conclusions; a site-wide average mixes pages that should bounce with pages that should not.
Questions About Bounce Rate
Why did my bounce rate drop when we moved to GA4?
Because the definition changed. Sessions with one page view and no other tracked interaction that last longer than the engagement timer (10 seconds by default) were bounces in Universal Analytics and are engaged sessions in GA4.
Should I compare bounce rate across different GA4 properties?
Only with care. Check that the properties count the same key events and track the same interactions, since both change which sessions qualify as engaged.