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.
What this means
A new visitor is one the tool has no prior record of in its lookback window; a returning visitor is recognized from a previous visit. Recognition usually depends on a first-party identifier stored in the browser (a cookie or local storage value) that the tool reads on the next visit.
Why the split is fragile
Anything that resets or hides the identifier turns a returning visitor into a 'new' one: clearing cookies, using a different browser or device, private/incognito windows, and browser storage policies (such as Safari's Intelligent Tracking Prevention capping script-set cookie lifetimes) all do this. The result is a consistent bias toward 'new'. The dimension also cannot link the same person across devices without cross-device identity, which privacy-safe analytics deliberately avoids.
- Cleared cookies and incognito count returning visitors as new
- A second device is a second 'new' visitor
- Browser storage limits cap identifier lifetime, inflating 'new'
How it appears in analytics and logs
A high 'new' share can mean genuine audience growth or simply that returning visitors were not recognized because their identifier was reset. Treat it as a lower bound on returning, not a precise loyalty figure.
Diagnostic use case
Read the new/returning split as a directional loyalty signal, while accounting for the identifier loss that inflates the new bucket.
What WebmasterID can help detect
WebmasterID determines new vs returning from a first-party identifier only, so the split never depends on third-party cookies or cross-site tracking — and degrades gracefully toward 'new' as users clear storage.
Common mistakes
- Reading the 'new' share as a precise growth or acquisition number.
- Assuming one person maps to one visitor across devices.
- Ignoring browser storage policies that reset identifiers.
Privacy and accuracy notes
The classification relies on a client identifier; privacy controls that limit storage are working as intended when they make a returning visitor count as new. WebmasterID measures this first-party and coarsely, not via cross-site identity.
Related pages
- 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.
- 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.
- Bot traffic in analytics: filtering it out
Bots — crawlers, scrapers, monitors, scanners — generate requests that, unfiltered, inflate pageviews and distort every metric. Client-side analytics often misses bots (many do not run JavaScript) or miscounts the ones that do. Server-side classification at ingest is the reliable way to keep bot traffic out of human reports.
- Privacy-first analytics
First-party identity, no cross-site tracking.
Sources and verification notes
- Google — [GA4] New vs returning users
- WebKit — Intelligent Tracking PreventionExplains storage limits that reset script-set identifiers.
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.