What is bounce rate in GA4, and should you worry about it?

According to Google's Analytics Help, a session is engaged if it meets any one of these:

• It lasts longer than 10 seconds.
• It has a key event, such as a form submission you have marked as important.
• It has 2 or more page or screen views.

Miss all three and the session counts as a bounce. Google gives its own example: a visitor reads for less than 10 seconds, triggers no events, views no other pages and leaves. If that were the only session on the site, engagement rate would be 0% and bounce rate 100%.

Picture a visitor who lands on your contact page, finds your phone number in 8 seconds and calls you. That visit did its job perfectly. Unless the call or the click on the number is tracked as a key event, GA4 counts it as a bounce.

The same goes for a blog post that answers a question in the first paragraph, or a menu page a customer checks before driving over. Our read: a high bounce rate on a page built to give a fast answer is often a sign the page works.

That is why one sitewide figure says so little. Bounce rate earns its keep when you compare like with like:

• the same page before and after a change
• one traffic channel against another, using GA4's default channel groups
• mobile against desktop
• one landing page against a similar one

Most GA4 reports do not show bounce rate or engagement rate by default. Google's steps:

1. Open a detail report, such as Pages and screens.
2. Click Customize report.
3. Under Report data, choose Metrics, then Add metric.
4. Add "Engagement rate" and "Bounce rate," apply, and save.

You need an Editor or Administrator role to customize reports, and you can only add metrics to detail reports, not overview reports.

Google's own advice is to dig in before you change anything. Check whether engagement is low everywhere or only on certain pages, channels or source and medium pairs. Then work through these:

1. Check the promise. If one channel bounces more, compare the ad or link with the page it leads to. Google gives exactly this example: if visitors from display ads bounce, make sure the ads are relevant to the content.
2. Track the actions that matter. Mark calls, form submissions and bookings as key events, so a quick visit that converts stops looking like a failure.
3. Make the next step obvious. If a page answers the question and then stops, add the logical next click: a related guide, a price page or a way to reach you.
4. Check page speed on phones. A slow first screen sends people back before the 10 seconds are up.
5. Check the tag. If the problem is sitewide, Google suggests confirming that every page is tagged, and tagged correctly.

Use engagement rate in reports to owners and clients. It says the same thing as bounce rate, framed as the share of visits that did something, and it keeps the conversation focused on what people do on the page instead of what they did not do.

Keep bounce rate for diagnosis, page by page.

Worry about bounce rate page by page, with key events set up properly. A sitewide number on its own tells you very little, and a high rate on a page that answers a question quickly can be perfectly healthy.

Is bounce rate the same as it was in Universal Analytics? No. In GA4 it is defined through engaged sessions: a bounce is any session that was not engaged, so a long single-page visit no longer counts as a bounce once it passes 10 seconds.

What is a key event? An action you mark as important in GA4, such as a form submission or a purchase. A session with a key event counts as engaged even if it is short.

Does bounce rate affect Google rankings? Google has not said that it uses your GA4 data for ranking. Treat bounce rate as a diagnostic for your own pages, not a ranking lever.

What should I report to clients? Engagement rate, by page and by channel, with key events listed beside it.