Engaged sessions and rate
In plain English: Engagement rate is engaged sessions divided by sessions.
A session is engaged when it lasts longer than 10 seconds, contains a key event, or has at least two page or screen views. Bounce rate is the percentage of sessions that were not engaged.
- 80 engaged sessions ÷ 100 sessions = 80% engagement rate
Engagement time and event count
In plain English: Time and counts describe different parts of behaviour.
Average engagement time reflects time the site or app was actively in focus under GA4's measurement. Event count totals collected events. A high count can indicate genuine activity or an accidentally duplicated implementation.
Key events
In plain English: A key event is an event your organisation marks as important.
Examples might include a completed enquiry, sign-up or purchase. Google renamed what Analytics previously called conversions to key events; advertising products may still use conversion terminology for their own reporting workflows.
Keep in mind: Marking an event as key does not fix incorrect event collection.
Context beats benchmarks
In plain English: A useful rate depends on the job of the page and the business outcome.
A content site may examine reading and onward navigation. A SaaS site may connect engagement with trial or demo actions. Ecommerce teams may consider product views, checkout progress and purchase outcomes. None has one universally good engagement rate.