Engagement rate tells you what proportion of visits showed some sign of real interest. GA4 calculates it as engaged sessions divided by sessions, so a page with 1,000 sessions and 600 engaged sessions has a 60% engagement rate (illustrative). It is the mirror image of GA4's bounce rate: the two always add up to 100%.
Formula
The calculation is simple, and the inputs carry all the nuance. Anything that changes what counts as an engaged session (the timer, the list of key events) changes engagement rate.
Engagement rate = Engaged sessions / Sessions
Bounce rate = 1 - Engagement rateWhere it is useful
Engagement rate works best as a comparison metric within your own site: one landing page against another, organic search against paid social, this month against the same month last year. It is a quick way to spot pages whose traffic does not match their content, or channels that send low-quality visits.
It is less useful as an absolute target. A pricing page, a documentation reference page and a long guide naturally produce very different engagement rates, and there is no universal benchmark worth chasing.
Example
Comparing channels on the same landing page
Suppose Tallowgate, an HR software company, sends paid social and organic search traffic to the same comparison page. Organic visits show a much higher engagement rate. That suggests the paid audience is less qualified or the ad promises something the page does not deliver, and it is a better prompt for the paid team than a blanket page redesign.
Common mistakes
Benchmarking against other companies' numbers
Definitions, timers and key events differ between properties, so cross-company comparisons rarely mean much.
Reading it without volume
A 90% engagement rate on 12 sessions says almost nothing. Always look at the session count next to the rate.
Questions
No. Social platforms use engagement rate for likes, comments and shares relative to reach or followers. GA4's engagement rate is about sessions on your own site or app.
