Client ID dimension: the device-scoped pseudonym
Client ID is the device-scoped pseudonymous identifier analytics generates to recognise a returning browser. In GA4 it is typically stored in a first-party cookie and underpins the user and session counts. It is not a person: clearing cookies, switching browsers, or using a new device all create a fresh client ID, which is why user counts drift upward and cross-device journeys split without a User-ID.
What this means
When a browser first hits a GA4-tagged page, the tool mints a client ID and stores it, usually in a first-party cookie. On the next visit the cookie returns the same ID, so the browser is recognised as returning. Client ID is what 'total users' and 'returning users' are built on when no User-ID is set.
It is deliberately pseudonymous: a random token, not anything about the person.
Why it resets and what that does to counts
Anything that drops the cookie resets the client ID: clearing browser data, private browsing, switching browsers or devices, and browser policies that cap first-party cookie lifetimes (such as Safari's Intelligent Tracking Prevention). Each reset looks like a brand-new user.
The consequence is that user counts inflate and individual journeys fragment over time — a structural reason analytics user counts are estimates, not headcounts. A persistent cross-device User-ID is the only reliable fix.
- Stored in a first-party cookie; recognises a returning browser
- Resets on cookie clearing, new browser/device, ITP caps
- Counts devices/browsers, not people
How it appears in analytics and logs
A client ID identifies a browser instance. Inflated 'new user' counts often trace to client ID churn (cookie clearing, ITP cookie caps, multiple devices), not genuinely new people.
Diagnostic use case
Understand client ID as the basis of returning-user recognition, while accepting it counts browsers/devices, not people, and resets when storage is cleared.
What WebmasterID can help detect
WebmasterID measures without relying on cross-site identity; where a first-party identifier is used it is scoped to one site and never enriched by fingerprinting.
Common mistakes
- Treating client-ID-based user counts as a headcount of people.
- Ignoring cookie-lifetime caps when explaining rising new users.
- Assuming one person equals one client ID across devices.
Privacy and accuracy notes
Client ID is a pseudonymous, first-party identifier, but it is still an identifier — consent and cookie rules apply in many jurisdictions. WebmasterID does not use cross-site identifiers and never fingerprints to make client IDs persist.
Related pages
- User-ID dimension: identity you assign, not infer
User-ID is the dimension that carries an identifier you assign to authenticated users, enabling analytics to stitch their activity across devices and sessions. Unlike a client ID, it is identity you provide, typically only after sign-in. GA4's User-ID feature requires that the value be a non-PII pseudonymous key and that you have the appropriate consent, because it links behaviour to a known person.
- Session ID dimension: scoping events to one visit
Session ID is the dimension that ties a burst of events together into one session. In GA4 it is derived from the ga_session_id parameter set when a session_start event fires, and it pairs with the client or user ID to be unique. A session ends after a timeout of inactivity (30 minutes by default), so the same person returning later gets a new session ID — which is why session counts respond to the timeout setting.
- 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.
- Privacy-first analytics
First-party, no cross-site identifiers or fingerprinting.
Sources and verification notes
- Google Analytics — Client ID (Measurement Protocol / GA4)MDN on first-party cookie storage that backs the client ID.
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.