Engagement rate and engaged sessions
Engagement rate is the percentage of sessions that were 'engaged'. In GA4 an engaged session is one that lasted longer than a threshold (10 seconds by default), had a key event/conversion, or had at least two pageviews. Engagement rate is the inverse of GA4 bounce rate, and its threshold is configurable — so the number depends on a setting most people never check.
What this means
Engagement rate is engaged sessions divided by total sessions. GA4 calls a session 'engaged' if it met any one of three conditions: it lasted longer than the engagement threshold, it included a key event (conversion), or it produced two or more pageviews/screenviews.
The configurable threshold
The time threshold defaults to 10 seconds but can be set per data stream (up to 60 seconds). Because the threshold is a knob, two properties measuring identical behavior can report different engagement rates. Engagement rate is also the exact inverse of GA4's bounce rate — bounce rate is 100% minus engagement rate — so the two metrics carry the same information.
- Engaged = >threshold time, OR a key event, OR 2+ pageviews
- Default threshold 10 seconds, configurable per stream
- Engagement rate = 100% − GA4 bounce rate
How it appears in analytics and logs
A high engagement rate means most visits crossed an engagement threshold — time, a key event, or a second pageview. A shift can reflect real behavior or a changed threshold, so confirm the engaged-session definition before reading trend changes.
Diagnostic use case
Use engagement rate as a quality signal that is harder to game than raw bounce, while knowing the engaged-session thresholds that produce it can be changed.
What WebmasterID can help detect
WebmasterID derives engagement from first-party events, so engaged-session ratios are available without third-party cookies or cross-site tracking.
Common mistakes
- Assuming the engagement threshold is fixed at 10 seconds.
- Reading engagement rate and GA4 bounce rate as independent signals.
- Comparing GA4 engagement rate to a non-GA4 'engagement' metric.
Privacy and accuracy notes
Engagement rate comes from event timing and counts, not identity. It needs no personal identifiers to compute.
Related pages
- Bounce rate: definition and why it misleads
Bounce rate is the percentage of sessions with only one interaction. Its definition shifted: classic tools counted single-pageview sessions; GA4 derives it from engaged sessions instead. A high bounce rate is not inherently bad — for a single-answer page it can mean success — which is why context matters more than the number.
- Sessions: what a session is and when it resets
A session is a group of interactions from one visitor within a bounded time window. It starts on the first event and ends after a period of inactivity (commonly 30 minutes, configurable). The reset rules differ by tool — and historically Universal Analytics also restarted sessions at midnight and on a new campaign — so the same traffic produces different session counts in different products.
- Average engagement time (GA4)
Average engagement time is a GA4 metric for how long your site or app was in the foreground and focused, averaged per active user or per session. Unlike classic session duration, it is measured directly from visibility — the timer pauses when the tab is hidden or backgrounded. That makes it a more honest attention signal, but it is GA4-specific and not comparable to older duration metrics.
- Website observability
Engagement signals from first-party events.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.