The Most Misunderstood GA4 Metrics and What They Actually Mean

Why GA4 Metrics Cause Confusion

Google Analytics 4 changed the definitions of many metrics from Universal Analytics and introduced new ones with similar-sounding names. Understanding exactly what each metric counts is essential for interpreting reports correctly — and for not making decisions based on a misread metric.

Users vs Active Users

In UA, "Users" meant all users including those with very brief sessions. In GA4, the default "Users" metric shown in most reports is actually "Active Users" — users who triggered an engaged session (10+ seconds, 2+ pageviews, or a conversion) or a key event. This is a stricter definition that produces lower user counts but represents more genuinely engaged visitors.

GA4 does have a "Total Users" metric (includes all users, even single-second sessions) — but it is not the default. When you see "Users" in GA4 standard reports, you are seeing Active Users.

Sessions vs Sessions with Engagement

"Sessions" in GA4 counts all sessions including very brief ones. "Engaged sessions" is a subset — only sessions meeting the 10-second/2-pageview/conversion threshold. Engagement Rate = Engaged Sessions / Sessions. Neither metric is "better" — they measure different things. Use Sessions for reach measurement and Engaged Sessions for quality measurement.

Conversions vs Key Events

GA4 renamed "Conversions" to "Key Events" in 2024 within GA4's interface. The metric in the standard reports is now labelled "Key events." However, when these are imported into Google Ads, they are still called "Conversions" in Google Ads. The concepts are the same — the naming changed only in GA4's interface, not in Google Ads. Do not confuse "Key Events" in GA4 reports with a new type of event.

Event Count vs Conversions

An event can fire many times in a session (you can add many items to a cart — many add_to_cart events). When an event is marked as a Key Event, GA4 reports "conversions" which counts sessions where the event fired at least once — not the total number of event firings. This is why your Conversions count is always less than or equal to your Event Count for Key Events.

New Users

In GA4, "New Users" counts users whose first_visit event occurred during the reporting period. For Safari users with ITP (7-day cookie cap), a returning user who comes back after 8 days appears as a new user — because their GA4 cookie expired and a new first_visit was recorded. This inflates new user counts for properties with a high Safari user percentage that have not implemented server-side tracking.

Average Engagement Time

This replaces UA's "Average Session Duration." It counts the time when the page was actually in the foreground of the user's device (active tab), not the total elapsed time between first and last hit. It tends to be lower than UA's session duration because it excludes time when the user had the tab in the background.

Views

GA4 "Views" counts page_view events. In UA, "Pageviews" and "Unique Pageviews" were different metrics. GA4 has Views (total page_view fires) — there is no direct equivalent to UA's unique pageviews within a session at the standard report level.

Summary

The most impactful misunderstandings: GA4's "Users" is Active Users (higher bar than UA Users), "Conversions" are now "Key Events" (naming change, same concept), and "New Users" is inflated by Safari ITP for properties without server-side tracking. Always verify what a metric counts before making decisions based on it.

See our GA4 Setup & Audit service for metric interpretation training.

Confused by your GA4 metrics? Contact Adslytics.