New vs established user dimension
The new vs established user dimension classifies a user as 'new' or 'established' based on whether GA4 had recorded prior activity for them before the reporting window. It is user-scoped and derived from the user's first-seen timestamp. This differs from the session-scoped new-vs-returning split, which classifies each visit; conflating the two produces mismatched user and session counts.
What this means
New vs established user is a user-scoped classification: GA4 marks a user 'new' if their first-seen time falls inside the reporting window and 'established' if they were known before it. It answers 'is this person part of our existing base or just acquired?'
Because it is anchored to the user's first-seen timestamp, it stays consistent for a given window regardless of how many sessions the user has within it.
Versus new vs returning
New-vs-returning is session-scoped — it labels each visit as a first or a repeat session. New-vs-established is user-scoped — it labels the person. A user can be 'established' yet still generate a session that, in a different scope, looks new after identity loss. Reporting them as the same number is a scope error that makes users and sessions disagree.
- User-scoped first-seen classification
- Distinct from session-scoped new-vs-returning
- Identity loss can reset a user to new
How it appears in analytics and logs
'New' means GA4 first saw the user within the period; 'established' means earlier. It is about the person across time, not whether a single visit is a return.
Diagnostic use case
Use new vs established to separate freshly acquired users from your existing base when reading retention and engagement.
What WebmasterID can help detect
WebmasterID can distinguish freshly acquired from established users from first-party signals while noting that identity resets reclassify users as new.
Common mistakes
- Equating established users with returning sessions.
- Comparing user-scope and session-scope counts directly.
- Ignoring identity loss when users appear newly acquired.
Privacy and accuracy notes
The split derives from a first-party first-seen timestamp on the device identity, not cross-site identity. Cleared identifiers reset a user to 'new'.
Related pages
- New vs returning dimension
The new vs returning dimension classifies a visitor as new (no prior recorded visit) or returning. The classification depends on a persistent client identifier surviving between visits. When cookies or storage are cleared, browsers cap identifier lifetime, or a user switches devices, returning visitors are recounted as new — so this dimension systematically tilts toward 'new' and should be read with that bias in mind.
- Days since last session dimension
The days since last session dimension reports how many days have elapsed since the user's previous session. GA4 computes it from the stored last-session timestamp on the current identity. It supports recency and re-engagement analysis, but it can only be calculated when GA4 still recognises the user — if the identifier was cleared, the prior session is invisible and the return is counted as new, so the gap is undercounted.
- New vs returning misclassification
New-vs-returning depends on recognising the same visitor across visits, which relies on a stored identifier. When that identifier is missing — cleared cookies, tracking prevention, a different device or browser, or declined consent — a returning visitor is recorded as new. The result over-states 'new' visitors and understates loyalty. This page explains the failure modes.
- Privacy-first analytics
New vs existing users without cross-site profiling.
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.