Where Is Bounce Rate in GA4?

Does GA4 have a Bounce Rate metric?

Yes. GA4 defines Bounce Rate as the percentage of sessions that were not engaged sessions. It is the inverse of Engagement Rate. This definition is also documented in the official Google Analytics Data API schema, where the metric is available as bounceRate.

A session is considered engaged when it lasts longer than 10 seconds, includes a key event, or records at least two page views or screen views. If a session meets none of those conditions, it contributes to Bounce Rate. Google’s session documentation confirms the same three engaged-session criteria.

For example, if a page receives 1,000 sessions and 620 are engaged, 380 are non-engaged. Its GA4 Bounce Rate is therefore 38%. This is a calculation example, not a benchmark: whether 38% is healthy depends on the page’s purpose, traffic source, and expected user action.

Where is Bounce Rate in GA4?

The metric can be added to a GA4 detail report. The exact navigation can vary when a property uses customised report collections, because Editors and Administrators can change the reports shown in the left navigation. The usual route is:

1. 1
   Open your GA4 property
   Choose the correct account and property before editing a report.
2. 2
   Go to Reports
   Open a detail report, such as Engagement → Pages and screens or Engagement → Landing page.
3. 3
   Select Customise report
   Use the pencil icon in the top-right corner of the report.
4. 4
   Open Metrics
   Select Add metric, search for “Bounce rate”, and add it to the report.
5. 5
   Apply and save
   Choose whether to save the changes to the current report or create a new report.

Google’s detail-report documentation confirms that a report can contain up to 12 metrics and explains the same Metrics → Add metric → Apply → Save process.

You can also use GA4 Explorations when you need a temporary analysis rather than a permanent report change. Add Bounce Rate as a metric and combine it with a relevant dimension, such as Landing page, Page path, Device category, or Session default channel group.

Which GA4 report should you add Bounce Rate to?

Choose the report according to the question you need to answer. Adding the metric everywhere creates noise; adding it to a small number of decision-focused reports makes it more useful.

The official GA4 Landing page report guide explains that this report is session-scoped and identifies the first page visited in a session. Google also documents how to add Session source / medium as a secondary dimension. For channel-level investigation, use the Traffic acquisition report.

GA4 Bounce Rate vs Universal Analytics

The name is familiar, but the calculation is not the same as the Universal Analytics version. That means the two metrics should not be placed in one continuous trend line or treated as directly comparable.

Google’s archived Universal Analytics Bounce Rate documentation defines the legacy metric as single-page sessions divided by all sessions. The current GA4 definition is based on non-engaged sessions, so establish a fresh GA4 baseline and compare similar page types, traffic sources, devices, and date ranges.

What does a high Bounce Rate mean?

A high Bounce Rate is a prompt to investigate, not proof that a page is failing. Even Google’s legacy guidance says whether a high rate is undesirable depends on the site and page purpose. A visitor may read an answer, get what they need, and leave without generating another engagement signal. That can be a successful visit even though GA4 records it as non-engaged.

Interpret the metric alongside the page’s purpose and supporting data:

• Landing page intent: Does the content answer the query visitors used?
• Traffic source: Are campaigns or search snippets setting the right expectation?
• Device experience: Is the page fast, readable, and easy to use on mobile?
• Key events: Are meaningful actions configured correctly in GA4?
• Internal journeys: Is there a clear, relevant next step for the visitor?

If the issue looks technical rather than behavioural, run a website audit to check page speed, mobile rendering, broken links, and other problems that can interrupt the visit. Google describes Core Web Vitals as measures of real-world loading performance, responsiveness, and visual stability; they are useful diagnostic context, but they are not interchangeable with Bounce Rate.

A reliable workflow for analysing a Bounce Rate change

Start with measurement quality, then narrow the data. This prevents a tracking change or a poor comparison from being mistaken for a content problem.

1. Confirm that the definition and implementation have not changed

   Check whether key events, tags, consent settings, or report filters changed near the date of the movement. Because a key event can make a session engaged, changing event configuration can change Bounce Rate even when users behave similarly.

2. Compare like with like

   Use equivalent date ranges and the same GA4 property, report, dimensions, and filters. Avoid comparing GA4 directly with a Universal Analytics baseline.

3. Start with landing pages, not the site-wide average

   A site-wide number blends pages with different purposes. Segment by landing page to find whether the change belongs to a specific template, content group, or entry page.

4. Break the result down by channel and source

   Google recommends checking whether low engagement is concentrated in channels, source/medium pairs, or particular pages. A mismatch between campaign promise and landing-page content can produce a different pattern from a site-wide usability problem.

5. Compare desktop and mobile

   If the increase is isolated to one device category, inspect layout, navigation, performance, consent behaviour, and interactive elements on that device before rewriting the content.

6. Check the intended outcome

   Review key events, leads, purchases, or the next-page journey. A low Bounce Rate with no meaningful outcome is not automatically better than a higher Bounce Rate on a page that answers the visitor’s question.

What is a good Bounce Rate in GA4?

There is no single trustworthy percentage that applies to every website. An ecommerce checkout, a pricing page, a support answer, and a one-page article have different jobs. Traffic mix also matters: brand visitors, paid campaigns, email subscribers, and first-time informational searchers rarely behave identically.

Use your own data to create a defensible benchmark:

• Group pages by purpose or template instead of comparing every URL with the site average.
• Use a sufficiently long date range and compare the same days of the week where seasonality matters.
• Segment by device category and acquisition channel before deciding that content is responsible.
• Track Bounce Rate with key-event rate, engagement time, and the next page or action.
• Record major tracking and site releases so unexplained changes can be matched to implementation dates.

The goal is not to force every page towards the lowest possible rate. The goal is to identify meaningful changes, explain their cause, and improve the outcome that the page is meant to produce.