Engaged sessions vs sessions in GA4, explained
GA4 talks about sessions and engaged sessions as if the difference is obvious. It is not. A session is any visit; an engaged session is one that actually did something meaningful, and that distinction underpins GA4's whole engagement model.
The definitions
- Session: a single visit to your site, any visit, however brief.
- Engaged session: a session that lasted longer than 10 seconds, OR had a conversion, OR had two or more page views. Anything less counts as not engaged.
How this replaced bounce rate
GA4's engagement rate is the share of sessions that were engaged, and bounce rate is simply its inverse. So a "bounce" in GA4 is a session that failed all three engagement tests. This is why GA4's bounce numbers look nothing like the old Universal Analytics ones, and why a tracking bug can send the rate to 0% or 100%.
Why it matters for your reports
When you build dashboards or compare channels, decide whether you mean sessions or engaged sessions, because they tell different stories. A channel with many sessions but few engaged ones is bringing low-quality traffic. Mixing the two, especially in Looker Studio, is a common reason numbers seem to disagree.
Want us to check your tracking in 10 seconds?
Pop in your domain and we will show you what is firing, what is not, and where data is leaking. Free, no signup.
Check my tracking freeGet a plain-English audit
We check your live GA4, Google Tag Manager and consent setup by hand and tell you exactly what is wrong. The audit comes off any build.
See how it works & pricingDatahound are analytics and ad-tracking specialists. We fix broken GA4, Google Tag Manager and server-side tracking so every sale, form and call gets counted. Back to datahound.agency · All tracking guides · Why your bounce rate hit 0% or 100%