Engaged Session

An engaged session is GA4's way of separating real visits from glances. A session counts as engaged if it meets any one of three conditions: it lasted longer than 10 seconds, it triggered a key event, or it included at least two pageviews. Just one is enough. This single definition underpins both engagement rate and the modern bounce rate, which is simply the share of sessions that weren't engaged.

Why it matters

The engaged session is the building block of every engagement metric in GA4. It replaced the old, blunt idea that a one-page visit was automatically a failure. By rewarding any genuine sign of attention — time, a meaningful action, or a second page — it gives a fairer picture of whether people are actually using your site rather than bouncing straight off.

A concrete example

A visitor lands on your pricing page from search, reads it for 25 seconds, and leaves without clicking anything. Under the old rules that was a "bounce". In GA4 it's an engaged session, because it cleared the 10-second bar. That's the more honest reading: the person paid real attention, even though they only saw one page and didn't convert this time.

The common misreading

People assume an engaged session means someone did something valuable — converted, enquired, signed up. It doesn't. The bar is deliberately low; it measures attention, not outcome. A high engaged-session count is a good sign that visitors aren't bouncing, but it's not a stand-in for results. Read it alongside your key events to see whether attention is turning into action.