Bounce rate in GA4: where it is and what it means

Short answer: In GA4, bounce rate is the percentage of sessions that were not engaged, the opposite of engagement rate. A session counts as engaged if it lasts longer than 10 seconds, has a key event, or has two or more page or screen views. Most GA4 reports don't show bounce rate by default. Add it with Customize report on a detail report or import it into an Exploration, or read engagement rate in Traffic acquisition and subtract it from 100%. Then compare similar pages and channels over time instead of chasing one magic number.

What bounce rate means in GA4

Google's help page on engagement rate and bounce rate is short. It says an engaged session is one 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. Then: "The bounce rate is the opposite of the engagement rate. The bounce rate is the percentage of sessions that were not engaged."

The API reference gives the arithmetic: (sessions minus engaged sessions) divided by sessions. Take 1,000 sessions, 640 of them engaged (hypothetical numbers). Engagement rate is 64%, bounce rate is 36%. Our glossary entry on bounce rate has the short version.

Two details matter:

• Reading for three minutes counts as engaged. A visitor who lands on a long article, reads it for three minutes and leaves is engaged, because the session lasted longer than 10 seconds. That's a big change from the old definition below.
• Some events don't count. Google says first_visit, first_open and session_start are excluded from the engaged-session calculation, even if you mark them as key events.

It isn't the old bounce rate

Universal Analytics, the previous version, defined bounce rate as the percentage of single-page sessions "in which there was no interaction with the page," with a bounced session lasting 0 seconds. A reader who spent minutes on your homepage and clicked nothing was a bounce. In GA4 they're engaged. Numbers from the two versions don't compare.

Google makes the point that suits content sites: "if you operate a blog, you might not mind if customers visit your site to read an article and then leave. You probably care more about the number of customers who visit your site, don't find what they were looking for, and then quickly leave." That second group is what GA4's bounce rate is closer to.

Where to find bounce rate in GA4

Google says "most reports in Google Analytics do not include the engagement rate and bounce rate metrics." Here is what the main reports show out of the box, from each report's own help page.

You have three routes, quickest first.

1. Read engagement rate and subtract. The Traffic acquisition report (Reports, Acquisition, Traffic acquisition) includes Engaged sessions and Engagement rate by default. Search "google / organic" in its search bar for Google organic traffic only. Bounce rate is 100% minus the engagement rate.

2. Add bounce rate to a detail report. The Landing page and Pages and screens reports don't list it among their default metrics. To add it:

1. Open Reports, then the detail report, such as Engagement, Landing page.
2. Click Customize report in the upper right. If you don't see it, you need the Editor or Administrator role.
3. Under Report data, click Metrics. If you only see Cards, you're in an overview report, and metrics can only be added to detail reports.
4. Click Add metric, type "Bounce rate" and click Apply.
5. Click Save, then Save changes to current report.

Bounce rate is added as the last column, so scroll right if you have many metrics. A detail report holds up to 12.

3. Import it into an Exploration. In Explore, open a free-form exploration. In Variables, click the plus beside Metrics, search "Bounce rate" and click Import, then drag it into Values in Tab Settings. Google's Explorations guide lets you use up to 20 metrics per exploration. This is the better route for comparing pages against each other.

A route for SEO. If you've linked Search Console to GA4, the Google organic search traffic report shows landing pages with clicks, impressions, CTR and average position next to engagement rate. It's hidden by default: publish the Search Console collection from Library.

What changes your bounce rate without changing your visitors

Two settings move the number on their own.

• Key events. Any session with a key event counts as engaged. Mark a routine event, such as a scroll or a click, as a key event and bounce rate drops, with no change in what visitors do.
• The engaged-session timer. Under Admin, Data streams, your web stream, Configure tag settings, Show all, Adjust session timeout, there's "Adjust timer for engaged sessions." Google says the default is 10 seconds and it can be changed.

Decide your key events once, leave the timer alone, and write the date down if you change either. Otherwise next quarter's comparison will mislead you.

How to read it for SEO

Google's own guide on using Search Console and Analytics together says organic sessions show volume and "engagement rate shows the quality of the traffic." If it drops, it says to check whether the page is "closely related to the queries your audience is using to find you." That's the useful reading: engagement rate is a check on whether the page matches the search.

A 15-minute routine:

1. Open the Landing page report for organic traffic. Add the secondary dimension "Session source / medium" and search "google / organic." Google's guide suggests this report to see how useful a page is to organic visitors.
2. Compare like with like. Glossary pages with glossary pages, pricing with pricing. A definition page where people read and leave isn't a failure.
3. Check outcomes next to bounce rate. Look at key events per session. A page with a high bounce rate that sends readers to a tool may be doing its job.
4. For an outlier, read its queries. Open the page in Search Console and compare its queries with what the page actually answers. Our Search Console reports guide shows where.
5. Fix the match, then measure properly. Rewrite the title and first paragraph (how we write titles), then compare 28 days before and after with the method in SEO A/B testing on a small site.

Here is why step 3 matters, with hypothetical numbers. Two organic landing pages each get 800 sessions and a 72% bounce rate. On the glossary page, 4.0% of sessions trigger a key event. On the pricing page, 0.4% do. Same bounce rate, different stories: the glossary page is passing readers on, and the pricing page has a problem. In Traffic acquisition, the Session key event rate column gives you the share of sessions that triggered a key event.

Don't expect GA4's organic sessions to match Search Console clicks. Google says clicks and sessions are calculated differently, so the numbers will differ.

Pair it with click-through rate

Search Console's click-through rate says whether your snippet earned the click. GA4's engagement rate says whether the page satisfied it. Read together, they point at different fixes. This is our rule of thumb, not Google's:

Bounce rate isn't a ranking factor

Search Engine Journal's roundup of Google statements, published in November 2022, quotes John Mueller at a June 2022 office-hours: "I think there's a bit of misconception here that we're looking at things like the analytics bounce rate when it comes to ranking websites, and that's definitely not the case." It also quotes Matt Cutts (2010) and Gary Illyes (2015) saying the same. Treat bounce rate as a diagnostic for your own pages.

Bounce rate isn't retention

Bounce rate describes one session. Retention asks whether people come back. GA4's Retention overview report (Reports, Life cycle, Retention, if it's in your navigation) shows the percentage of users who return each day in their first 42 days. A page can have a high bounce rate and a returning audience, and the reverse.

If the number looks wrong

Google's advice for a low engagement rate is to find out whether it's "uniformly low or whether it's the result of certain channels, source/medium pairs, pages or screens." Work through it in this order:

1. Is it one channel or page? Break the report down by channel, then by landing page. One bad page is a content problem. Everything bad is more likely a setup problem.
2. Is tracking complete? Google says to check that "all the necessary pages are tagged and that they are tagged correctly." A page without the tag drops out of the data altogether.
3. Did a setting change? If bounce rate sits near 0%, check whether a routine event, such as a scroll or a click, was marked as a key event. Any session that triggers it counts as engaged.

Mistakes to avoid

• Comparing GA4 with Universal Analytics. Different definitions.
• Using one benchmark for every page. Compare within a page type and channel.
• Judging a handful of sessions. On a page with 40 sessions, eight visits move the rate by 20 points.
• Changing key events and forgetting. The trend will break and nobody will know why.
• Reading tiny differences. Google says session and user metrics are "calculated through an estimation," so a point or two of movement on a busy page is noise.

If you're launching, tag your links so GA4 can split launch traffic from organic. Our UTM builder makes consistent tags, the UTM checker audits a list of tagged links for what breaks GA4 reporting, and launching free on LaunchRanked gives you a page to point them at. Then compare each channel's engagement rate against organic for the same weeks. Our GA4 glossary entry covers the rest of the vocabulary.