What is engagement rate?

How is engagement rate calculated?

Engagement rate = engaged sessions ÷ total sessions × 100
Bounce rate (GA4) = 100% − engagement rate

A session is engaged if any one of three conditions is met: it lasted at least 10 seconds in the foreground (the threshold can be raised to 60 seconds), it had at least two pageviews or screen views, or it fired a key event (formerly called a conversion). Time only counts while the tab is visible.

Engagement rate example

Out of 5,000 sessions, 1,800 viewed two or more pages, another 1,200 stayed on one page for more than 10 seconds, and 150 single-page, short visits fired a signup event. Engaged sessions = 1,800 + 1,200 + 150 = 3,150, so engagement rate = 63% and GA4 bounce rate = 37%.

Why engagement rate matters

It fixes the classic bounce rate's blind spot: a visitor who reads one article for four minutes and leaves satisfied is engaged, not bounced. That makes it fairer for content sites, docs and landing pages where one page is the whole experience.

Common engagement rate pitfalls

• The 10-second bar is low. Many people who skim and leave pass it. Treat engagement rate as "didn't leave instantly," not "read the page."
• Events inflate it. Any key event marks a session engaged; if you mark a scroll or a click as key, nearly every session qualifies.
• Not comparable across tools. Only GA4 uses this exact definition. Other tools report engaged time, scroll depth or classic bounce rate instead.
• Background tabs. Sessions opened in a background tab and never viewed are counted as sessions but rarely as engaged, which can drag the rate down on sites with lots of middle-click traffic.

How VisitTrack measures engagement

VisitTrack doesn't compute a GA4-style engagement rate. Instead, for every pageview it measures active time on the page (counted only while the tab is visible) and the furthest scroll depth reached, and reports time on page and scroll depth per page in the Pages tab — see engagement and scroll depth. Combined with the classic bounce rate and your goals, that answers the same question with fewer hidden thresholds. You can also fire scroll-depth events for specific sections you care about.