What Is an Engaged Session in GA4? The Three Rules, and How It Replaced Bounce Rate

What is an engaged session in GA4? It is a session that meets at least one of three rules: it lasts longer than 10 seconds, it has a key event, or it has two or more page or screen views [1]. Engagement rate is the share of sessions that were engaged, and GA4's bounce rate is the share that were not [1]. The two always add up to 100%.

Where the examples come from: Anobee's own GA4 property, for the 28 days from 24 September to 21 October 2026. Anobee read the numbers in the GA4 interface and through the Google Analytics Data API on 24 October 2026, and both matched.

What is an engaged session in GA4? The three rules

A session needs to pass only one of these [1]:

The second rule depends on your own setup. Anobee's property recorded no key events at all in the 28 days. Its custom events did fire, including 30 cta_click and 20 internal_link_click events. On a site like that, a session can only become engaged through time or a second page view. Marking a meaningful action as a key event lets a short but useful visit count as engaged.

Engaged sessions, engagement rate and bounce rate in GA4

Google's metric definitions give the exact formulas [2]:

• Engaged sessions: the number of sessions that lasted longer than 10 seconds, had a key event, or had two or more screen views.
• Engagement rate: engaged sessions divided by sessions.
• Bounce rate: sessions minus engaged sessions, divided by sessions.

Anobee's 28 days show how that plays out. There were 466 sessions, of which 157 were engaged. That gives an engagement rate of 33.7%. The other 309 sessions were not engaged, so the bounce rate was 66.3%.

How GA4's bounce rate differs from the old one

In Universal Analytics, a bounce was a single-page session [3]. GA4 counts a bounce as a session that was not engaged [1]. The difference matters for blogs. Someone who lands on one article and reads it for three minutes was a bounce in Universal Analytics. In GA4 the same visit is engaged, because it lasted longer than 10 seconds.

So you cannot compare a GA4 bounce rate with an old Universal Analytics one. They measure different things under the same name.

What Anobee's own GA4 data shows

The site-wide engagement rate of 33.7% hid a large spread between channels:

Visitors from search were engaged in seven of every ten sessions. Direct traffic was engaged in fewer than two of ten. The country split points to part of the reason. The 67 sessions from China were 4.5% engaged, and the 17 from France had no engaged session at all. Sessions from Nepal, Anobee's largest country with 188 sessions, were 62.2% engaged. Anobee reads this as automated or accidental direct traffic rather than real readers. GA4 alone cannot prove it.

That is the practical use of the metric. A single site-wide engagement rate is too blunt to act on. Break it down by channel, country and landing page before deciding that content needs fixing.

Engagement time and session duration are not the same

The same report showed an average engagement time of 17 seconds per session, while the API's average session duration was about 232 seconds. Google defines user engagement as the time your site was in the foreground of the visitor's device [2]. Session duration covers the whole session. Time a tab spends in the background can count toward session duration but not toward engagement time, so the two numbers can drift far apart.

How to change the 10-second engaged session timer

GA4 lets you raise the time rule if 10 seconds is too low a bar for your content. Google's steps are [4]:

1. Go to Admin, then Data streams, and select your web stream.
2. Select Configure tag settings, then Show more, then Adjust session timeout.
3. Under Adjust timer for engaged sessions, choose the number of seconds.
4. Select Save.

On anobee.com both settings are at Google's defaults: a 30-minute session timeout and a 10-second engaged timer [4]. Google's help page does not say whether a new timer applies to past data. Treat the dates before and after a change as separate periods when you compare them.

How to see bounce rate in GA4 reports

Most GA4 reports do not show engagement rate or bounce rate by default [1]. To add them, an Editor or Administrator can customize a detail report and add both metrics as columns [1]. The Traffic acquisition report on anobee.com already showed engagement rate, but bounce rate needed adding.

Whether a high bounce rate affects rankings is a separate question, covered in Anobee's article on whether bounce rate affects SEO. To set up GA4 or check that your key events are in place, start with the Google Analytics setup guide.