·Web analytics 101 / Bounce Rate / Exit Rate / GA4 / Engagement Rate

Bounce Rate vs Exit Rate — The GA4 Basics You Were Afraid to Ask

Bounce Rate and Exit Rate look similar but are completely different metrics. How GA4 redefined Bounce Rate against Engagement Rate, why GA4 dropped Exit Rate from default reports, and how to read 'exit quality' from a revenue lens.

Bounce Rate vs Exit Rate — The GA4 Basics You Were Afraid to Ask

"Bounce Rate is high, that's a problem, right?" "What's the difference between Bounce Rate and Exit Rate?" — these are the two metrics most often confused on the analytics floor. On top of that, the move from Universal Analytics (UA) to Google Analytics 4 (GA4) redefined Bounce Rate completely and removed Exit Rate from the default reports.

This article walks through the difference between Bounce Rate and Exit Rate, contrasts the UA and GA4 definitions, and ends with the question every EC operator actually cares about: which one should we be looking at when revenue is on the line?

TL;DR#

  1. Different sessions are counted

    Exit Rate counts every session that included the page. Bounce Rate counts only sessions that started on that page[2]

  2. GA4 redefined Bounce Rate

    What used to mean "single-page session" in UA now means "session without engagement" (1 minus Engagement Rate) in GA4[1]

  3. EC operators read 'exit quality' against revenue

    A high Bounce Rate or Exit Rate is not automatically bad. Combining it with RPS (Revenue Per Session) is how you decide whether to fix or to leave alone

Bounce Rate vs Exit Rate definition

1. Bounce Rate — The metric GA4 redefined#

Bounce Rate means very different things in GA4 and Universal Analytics. The classic UA shortcut "percentage of single-page sessions" no longer holds in GA4.

Bounce Rate in UA (the old definition)#

In UA, Bounce Rate was "the percentage of sessions that started with the page where there was only one pageview"[2].

The shorthand "people who left after seeing only one page" became the standard mental model.

Bounce Rate in GA4 (the new definition)#

GA4 redefined Bounce Rate as "the percentage of sessions that were not engaged" (1 minus Engagement Rate)[1].

A session counts as engaged when any one of the following is true[1].

  • The session lasts longer than 10 seconds
  • A Key Event (formerly Conversion) fires
  • There are 2 or more page or screen views

A single-page visit that lasts more than 10 seconds is no longer a bounce. Conversely, a 2-page visit under 10 seconds with no Key Event can still be counted as a bounce.

GA4 engaged session — 3 conditions

The simple "high Bounce Rate equals bad" reading is even harder to defend in GA4. Whether a sub-10-second exit means "bounced" or "read through" depends entirely on the page's purpose.

2. Exit Rate — Where each page becomes the last stop#

Exit Rate is the percentage of sessions including the page where that page was the session's last[2].

Exit Rate = Sessions that ended on the page / All sessions that included the page

The fundamental difference from Bounce Rate is the session pool. Bounce Rate's denominator is sessions that started on the page. Exit Rate's denominator is every session that passed through the page.

GA4 dropped Exit Rate from default reports#

UA had Exit Rate as a default column. GA4 does not list Exit Rate as a default metric[3].

To see exit behavior in GA4, use one of these instead.

  • Path Exploration — visualize where users came from and where they exited
  • Distribution of session_end events — aggregate the page right before the session ended
  • Combine with Engagement Time — find pages with short stay and high exit

The very habit of looking at "Exit Rate" as a single metric is downstream of UA's session-based model. Under GA4's event-based model the framing has shifted.

3. Bounce Rate vs Exit Rate — At a glance#

A side-by-side table makes the difference clearer.

Bounce Rate vs Exit Rate at a glance

AspectBounce RateExit Rate
Sessions countedSessions that started on the pageAll sessions that included the page
NumeratorNot-engaged sessions (GA4)Sessions ending on the page
GA4 default metricYes (re-defined)No (use Exploration)
Primary useLP / entry-page evaluationIdentify exit pages

A simpler analogy:

  • Bounce Rate = the share of visitors who turned around at the front door (entry-page lens)
  • Exit Rate = the share of visitors who walked out from each room (per-page lens)

4. From a revenue lens — Are Bounce Rate and Exit Rate "bad" metrics?#

Both metrics are often labeled "high equals bad", but in practice that shortcut breaks down quickly.

When high Bounce Rate is fine#

  • Single-page LPs: a landing page that completes purchase or inquiry on one screen will, by design, see almost everyone "leave after one page". A 90% Bounce Rate is healthy if CVR is good
  • Article media: search visitors who read an article and return to results are technically "bounces" but completed the page's actual job

When Exit Rate is a problem#

  • EC product detail pages: if buyers with intent are dropping off here, the button placement, stock indicator, or shipping copy all become candidates
  • Mid-funnel checkout steps: when the cart → shipping → payment sequence shows a spike on one step, form design is the natural suspect

In other words, where the bounce or exit happens, and in what context, is the actual signal. A standalone rate number rarely points to an action.

5. EC operators should read "exit quality" with RPS#

Both metrics ultimately need to be judged against revenue. RevenueScope reads page-level exits in combination with revenue indicators.

Use RPS (Revenue Per Session) to read "exit quality"#

RPS = Revenue / Sessions. It expresses how much revenue one session generates.

Read exit quality with RPS

  • High exit, low RPS → fix priority ★★★ (revenue leakage is largest)
  • High exit, high RPS → fix priority ★ (post-conversion natural exit)
  • Low exit, low RPS → traffic flows but revenue does not (rethink CTA)
  • Low exit, high RPS → keep as is and replicate elsewhere

Plotting Exit Rate × RPS as a 2 × 2 matrix makes it instantly clear which page deserves the next hour of work. The same idea sits behind the revenue dashboard design.

For the full Web Analytics 101 thread, see the rest of the series.

FAQ#

Q1. Is GA4's Bounce Rate lower than UA's?

In most cases yes. GA4's Bounce Rate is "not engaged" — meeting any one of (10s+ stay / Key Event / 2+ PV) keeps the session out of the bounce bucket, so the bar is more lenient than UA's[1].

Q2. How do I see Exit Rate in GA4?

GA4 does not include Exit Rate as a default metric. Use Path Exploration in the Explore section or aggregate session_end events to approximate it[3]. Pages with low engagement time plus high exit volume are usually where you should start.

Q3. What is a "good" Bounce Rate target?

There is no universal target — it depends on industry and page intent. Article media routinely sit at 70 to 90 percent. EC product detail pages often land at 40 to 60 percent. Single-page LPs can be healthy above 90 percent. Read Bounce Rate against CVR or RPS, not in isolation.

Q4. How should I prioritize Exit Rate fixes?

Revenue impact tends to be largest on mid-funnel checkout steps, then product detail pages, then category and search pages. Form-input friction, stock visibility, and shipping copy are the usual UX-level levers.

References#

See which ads actually drive revenue, at a glance

14-day free trial. No credit card required. Up and running in 5 minutes.

Start 14-day free trial

RevenueScope

EC revenue strategy, grounded in data and practice

Bounce Rate vs Exit Rate — The GA4 Basics You Were Afraid to Ask