engaged sessions

Engaged sessions replaced the Universal Analytics bounce model, which counted any single-page visit as a bounce. GA4 flips the frame: it defines what counts as engaged first, then treats bounce rate as everything left over. A session qualifies on an OR, so meeting any one of the three conditions is enough.

How GA4 counts it

The 10-second rule uses engagement time, not raw duration. GA4 only counts seconds while your page is in the foreground and in focus, so a tab left open in the background does not accrue engagement. That timer defaults to 10 seconds and is adjustable up to 60 seconds per web data stream (Admin, Data streams, Configure tag settings, Show all, Adjust session timeout).

One thing to watch: because two pageviews OR one key event also qualify, engagement rate can read as healthy even when nobody is reading. A visitor who lands, clicks one internal link, and leaves in four seconds still counts as engaged. If your engagement_rate looks strong but conversions stay flat, that gap is usually intent mismatch or thin content, not a tracking bug.

The math is simple: engagement rate = engaged sessions / total sessions, and bounce rate is its inverse (a page at 70% engagement has 30% bounce). The useful move is to segment engaged sessions by landing page and channel, so you can see which URLs actually hold organic visitors versus which ones just clear the 10-second bar.