What is bounce rate in GA4? Definition, formula and where to find it
GA4 bounce rate is the share of sessions that were not engaged: no 10-second visit, key event or second page. How it is calculated, where to find it and FAQ.
Bounce rate in Google Analytics 4 is the percentage of sessions that were not engaged. A session counts as engaged if it lasted longer than 10 seconds, triggered a key event or included at least two page or screen views; every other session is a bounce. So bounce rate = (sessions − engaged sessions) ÷ sessions, which is 100% minus engagement rate. This differs from Universal Analytics, where a bounce was any single-page session, so old and new bounce rates cannot be compared directly.
How to read GA4 bounce rate in 3 steps
Confirm the definition. In GA4 a bounce is a session that was not engaged. The 10-second threshold can be raised in the data stream’s tag settings (up to 60 seconds), which changes bounce rate for the whole property, so note the setting next to the number.
Calculate it from counts. Bounce rate = (sessions − engaged sessions) ÷ sessions × 100, or 100% minus engagement rate for the same report scope. When combining pages or channels, recompute from the counts rather than averaging percentages.
Judge it against the page’s job. A contact page that gives a phone number in five seconds can bounce and still succeed. Compare pages with similar purposes and traffic sources, and look at sessions and key events alongside the rate.
Where to find bounce rate in Google Analytics 4
Bounce rate is not shown in GA4’s default reports, but you can add it. In Reports, open a detail report such as Engagement › Pages and screens or Engagement › Landing page, select Customize report (the pencil icon), choose Metrics, add Bounce rate and save. You need Editor access to change the report for everyone. In Explore, add Bounce rate as a metric in a free-form exploration with Landing page or Session default channel group as the dimension.
GA4 bounce rate vs Universal Analytics bounce rate
The name stayed the same but the meaning changed, which is why a page’s bounce rate often looks very different after moving to GA4.
| GA4 | Universal Analytics | |
|---|---|---|
| A bounce is | A session that was not engaged | A single-page session with one hit |
| Formula | Non-engaged sessions ÷ sessions | Single-page sessions ÷ all sessions |
| A 3-minute read of one article | Not a bounce (longer than 10 seconds) | A bounce (only one page) |
| A 4-second visit to two pages | Not a bounce (two page views) | Not a bounce |
| Related metric | Engagement rate, its exact complement | None; time on page was separate |
GA4 bounce rate worked example
The figures are invented to show the calculation; they are not a benchmark. A blog post receives 1,000 sessions in a month.
| Sessions | What happened | Engaged? |
|---|---|---|
| 520 | Stayed longer than 10 seconds on the post and left | Yes |
| 130 | Clicked through to a second page | Yes |
| 30 | Signed up to the newsletter (a key event) within 10 seconds | Yes |
| 320 | Left within 10 seconds without another page or key event | No: bounces |
Engaged sessions = 680, so engagement rate is 68% and bounce rate is 320 ÷ 1,000 = 32%. Under Universal Analytics the 520 single-page readers would also have been bounces, giving roughly 84%, which is why the two definitions must not share a trend line.
One page, two bounce rates
An engagement rate of 72% corresponds to a bounce rate of 28% for the same scope. If a theme update stops a key event from firing, bounce rate can jump overnight without any change in how people use the page, so check measurement before rewriting content.
What to keep in mind
A high bounce rate is not automatically bad and a low one is not automatically good. Pages that answer a question quickly can bounce and still serve the visitor, and a confusing page can hold people longer than 10 seconds. There is no universal good bounce rate; compare a page with its own history and with pages that do the same job. Reports using the Universal Analytics definition are not comparable with GA4.
Bounce rate: common questions
How is bounce rate calculated in GA4?
Bounce rate = sessions that were not engaged ÷ total sessions. A session is engaged if it lasted longer than 10 seconds, had a key event or had two or more page or screen views. Bounce rate is therefore 100% minus engagement rate.
Why can’t I see bounce rate in GA4?
It is not in the default report layout. Add it through Customize report › Metrics in a detail report such as Pages and screens or Landing page, or use it as a metric in an Explore report.
What is a good bounce rate?
There is no single good number. It depends on the page’s purpose, the traffic source and your engagement settings. Track each page against its own baseline and investigate sudden changes rather than chasing an industry average.
Is bounce rate the opposite of engagement rate?
Yes, in GA4 they are exact complements for the same scope: an engagement rate of 65% means a bounce rate of 35%. Engagement rate is the metric GA4 shows by default.
Does bounce rate affect SEO rankings?
Google has not said that it uses Google Analytics bounce rate as a ranking signal, and many sites do not use GA4 at all. Treat bounce rate as a diagnostic for page experience, not as a ranking factor.
Your next useful step.
Add bounce rate to your Landing page report, note the engagement time threshold in your data stream settings, and pick the three landing pages whose bounce rate changed most against their own baseline. LiftSEO can read that GA4 report alongside Search Console so you can see whether the change came from search traffic or the page.
Working with this in LiftSEO
A metric needs a numerator, denominator, reporting period and source. Record those alongside the result. The examples in these notes are invented to explain the calculation; they are not industry benchmarks or LiftSEO customer results.
Explore the workspaceSources & context
This note combines original practical guidance with the reporting references below. Follow provider documentation for current definitions and availability; suggested investigations are not guarantees of a particular result.