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.
What this means
New vs returning labels each visit by whether the analytics tool has seen this client before. 'Returning' requires recognising a persistent identifier from a previous visit; 'new' is the absence of one. It is a coarse loyalty signal, useful for trends in audience composition.
Why 'new' is overcounted
Recognition depends on the identifier surviving. Cleared cookies and storage, private browsing, browser caps on client-side storage lifetime, and switching between phone and laptop all break the link, so a genuine returning visitor is counted as new. The bias is one-directional: it inflates 'new', never 'returning'. Read it as a trend, not a precise tally.
- Requires a persistent client identifier
- Cleared storage and cross-device use reset to 'new'
- Bias is one-directional: 'new' is overcounted
How it appears in analytics and logs
A new/returning value depends on whether a prior identifier was found. A high 'new' share can mean genuine acquisition or simply identifier loss from cleared storage and cross-device visits.
Diagnostic use case
Use new vs returning for directional loyalty trends, not absolute counts, knowing identifier loss and cross-device use inflate the 'new' share.
What WebmasterID can help detect
WebmasterID computes new vs returning from first-party state only, so the dimension stays privacy-safe and the limits of identifier persistence are explicit rather than hidden.
Common mistakes
- Treating new/returning counts as exact.
- Ignoring cross-device use that resets returning to new.
- Adding fingerprinting to 'fix' it — a privacy anti-pattern.
Privacy and accuracy notes
This split needs a persistent client identifier. WebmasterID favours privacy-respecting, first-party state and never uses cross-site or fingerprinting identifiers to force a match.
Related pages
- First user source dimension
The first user source dimension records the origin of a user's very first session — their acquisition source — and keeps it fixed for the user's lifetime. GA4 sets it from the referrer or campaign on the first visit. It is user-scoped, so it answers 'how did we acquire this person?' rather than 'where did this visit come from?', and confusing it with session source distorts attribution.
- Device category: desktop, mobile, tablet
Device category groups visits into desktop, mobile, or tablet. It is derived from the user-agent string (increasingly, User-Agent Client Hints), so it is a classification, not a hardware fact. Tablets, desktop-mode mobile browsers, and foldables blur the boundaries, and the user agent can be spoofed.
- Cookieless analytics: how it works and its limits
Cookieless analytics records visits and events without setting cookies or persistent cross-site identifiers. It relies on first-party, server-side signals and aggregate counting. The trade-off is honest: it cannot follow an individual across sessions the way cookie-based tracking can — which is exactly the point for privacy-first measurement.
- Privacy-first analytics
Loyalty signals from first-party state 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.