Engagement Rate vs Bounce Rate in GA4: What Changed and Why
Basics3 minInnovialabs editorial team
In short
In GA4 a bounce is any session that was not engaged, and an engaged session lasts over 10 seconds, has a key event or has two or more page views; so GA4 bounce rate is simply the inverse of engagement rate.
The short answer
In GA4 the main visit-quality metric is engagement rate: the share of engaged sessions among all sessions. Bounce rate in GA4 is its exact inverse:
Bounce rate = 1 − Engagement rate
If engagement rate is 62%, bounce rate is 38%. It is no longer a separate metric with its own logic.
What counts as an engaged session
A session is engaged if at least one condition is met:
- it lasted longer than 10 seconds (the threshold can be changed in the web data stream tag settings, up to one minute);
- it included a key event (formerly called a conversion);
- it had 2 or more page or screen views.
Anything that meets none of these is a bounce. Time counts while the page is active on screen, not just open in a background tab.
How Universal Analytics did it
In Universal Analytics a bounce was a single-hit session — usually one pageview with no other interaction events. Time on page was not considered.
That created a classic problem: someone opened an article, read it carefully for five minutes and left — UA recorded a bounce. For blogs and one-page landing pages, bounce rate looked alarmingly high and said little about quality.
GA4 fixed this: an article read for five minutes is an engaged session, even with a single pageview.
And in Yandex Metrica
In Metrica a bounce is a visit with a single page view lasting less than 15 seconds. There is an accurate bounce rate option: the tag sends an extra signal so time on page is captured more reliably in single-page visits.
| GA4 | Universal Analytics | Yandex Metrica | |
|---|---|---|---|
| Basis | Non-engaged session | Single hit | One page and short time |
| Time considered | Yes, default threshold 10 s | No | Yes, threshold 15 s |
| Goals considered | A key event makes the session engaged | Only via interaction events | Depends on goal and tag settings |
| Configurable | Time threshold, key event list | Via events | Accurate bounce option |
Takeaway: you cannot compare bounce rates across systems directly — they use different definitions. Compare trends within one system.
How to interpret the metrics
For a landing page:
- Mark form submissions, phone clicks and messenger clicks as key events — then sessions with a target action are always engaged.
- Break engagement down by source and campaign. Low engagement in one channel usually means untargeted traffic or a mismatch between the ad and the page.
- High engagement with no leads is a signal to check the offer, the form and load speed, not just the traffic.
For a blog:
- Single-page visits are normal: the reader found the answer. Average engagement time and the share of engaged sessions matter more.
- It helps to add scroll or reading events and track clicks on internal links.
- Compare articles of the same type with each other, not with the home page or catalog.
Common mistakes
- Comparing GA4 bounce rate with historical UA numbers and concluding the "site got better".
- Inflating engagement by marking overly frequent events, such as a small scroll, as key events.
- Setting the time threshold too low — the metric stops distinguishing real interest from accidental visits.
- Looking at site-wide averages instead of segments by page, device and source.