Users: counting people vs identifiers
The users metric estimates how many distinct visitors a site had, but it actually counts distinct identifiers, not individuals. GA4 reports several user metrics — Total users, Active users (its headline), and New users — that mean different things. Because a person on three devices is three identifiers, and a cleared cookie is a new one, the count diverges from the real number of people.
What this means
A 'user' is the analytics tool's unit for a distinct visitor, derived from an identifier (a first-party cookie, a device/app instance ID, or a signed-in ID where available). It is the closest analytics gets to 'people', but it is an approximation of people, not a census of them.
GA4's several user metrics
GA4 reports more than one user number and they are not synonyms. Total users is the count of distinct users with any event. Active users — GA4's primary 'Users' metric in most reports — counts users who had an engaged session or other engagement signal. New users counts those whose first-ever session falls in the range. Citing 'users' without saying which one invites mismatched comparisons.
- Total users: any user with at least one event
- Active users: GA4's headline 'Users' (engagement-based)
- New users: first session in the date range
How it appears in analytics and logs
A user count approximates distinct visitors. It drifts above the real number when one person uses several browsers/devices, and below it when identifiers are merged — so read it as an estimate with a known direction of error.
Diagnostic use case
Use the users metric as an audience-size estimate, noting which user metric a report shows and that it counts identifiers rather than people.
What WebmasterID can help detect
WebmasterID estimates users from first-party identifiers without cross-site tracking, so the headline audience figure carries no third-party-cookie dependency.
Common mistakes
- Equating the users metric with the number of people.
- Comparing Total users in one report to Active users in another.
- Forgetting that each device is a separate identifier.
Privacy and accuracy notes
Counting users requires only a first-party identifier, not a name or profile. Coarser identity reduces precision but protects privacy.
Related pages
- New vs returning visitors
New vs returning classifies a visitor by whether the analytics tool recognizes them from a prior visit, usually via a client identifier. The split is fragile: cleared cookies, multiple devices, private browsing, and privacy-driven storage limits all make returning visitors look new. So the 'new' share is systematically overstated, and the dimension says more about identifier persistence than loyalty.
- Sessions: what a session is and when it resets
A session is a group of interactions from one visitor within a bounded time window. It starts on the first event and ends after a period of inactivity (commonly 30 minutes, configurable). The reset rules differ by tool — and historically Universal Analytics also restarted sessions at midnight and on a new campaign — so the same traffic produces different session counts in different products.
- Unique pageviews vs pageviews
Unique pageviews count how many sessions included at least one view of a given page, collapsing repeat views of the same page within one session into a single count. It was a Universal Analytics metric; GA4 does not report it and uses 'Views' (closer to raw pageviews) instead. Knowing the difference avoids comparing a de-duplicated UA number to a non-de-duplicated GA4 one.
- Privacy-first analytics
Estimate audience with first-party identity only.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.