MISLEADING — GA4 "engagement rate" / "engaged sessions" — rests on arbitrary 10s default threshold (adjustable to 60s); measures THAT something happened, not that it was VALUABLE; one practitioner study found GA4 underreports engagement time by avg 54.7%

Claim — MISLEADING: GA4 "engagement rate" / "engaged sessions."

Per Google Analytics Help, an engaged session "is a session that lasts longer than 10 seconds, has a key event, or has at least 2 pageviews or screenviews" — the 10-second default is adjustable up to 60 seconds per web data stream.

How it deceives:

• The threshold is arbitrary. A visitor who stares at a loading page for 11 seconds is "engaged"; one who reads an answer in 8 seconds is not.
• It measures THAT something happened, not that it was VALUABLE. Two pageviews from a confused user counts the same as two pageviews from a converting one.
• GA4 underreports engagement time — one practitioner analysis found GA4 underreports average engagement time by an average of 54.7% (foreground-tab focus only, not reading).

Source: Google Analytics Help; compass_artifact research document; practitioner analysis (single source, methodology noted).

Confidence: Verified (threshold + definition); Single-source (54.7% underreport figure).

Caveat: Treat engagement rate as a diagnostic, NEVER as a success KPI (Rule: engagement is DIAGNOSTIC, not predictive — never promote engagement rate or engaged-session count to the primary success KPI). The 54.7% underreport figure is a single practitioner study — directionally useful for "engagement time is not what it looks like," not as a calibrated correction.