GA4 can use different identifiers to connect activity to users. Client ID is associated with a browser or device context. User-ID is an identifier an organization can send for an authenticated user when it has a suitable implementation. They answer different identity questions and should not be treated as interchangeable person-level records.
at Client ID represents
Client ID is a pseudonymous identifier assigned to a browser or app instance when analytics storage is available. It helps GA4 associate events from the same client context over time, but it is not a verified identity for a person.
Cookie deletion, browser restrictions, device changes, consent settings, and multiple browsers can affect continuity. The same person can appear as more than one client, and a shared device can be used by more than one person.
at User-ID represents
User-ID is a value an organization supplies when a user is signed in or otherwise reliably identified within its own system. It can help connect eligible activity across devices when the implementation, reporting identity, and consent conditions allow it.
Use a stable internal identifier that does not expose a direct personal identity. Never send names, email addresses, phone numbers, or other personally identifiable information as the User-ID value.
cide whether User-ID is appropriate
Use User-ID only when the product has a legitimate authenticated context and a documented privacy basis for analytics processing. Set and clear the value at the correct moments, account for logout and account switching, and avoid assigning the same identifier to unrelated people.
If the site has no reliable login identity, Client ID and event-level measurement may be sufficient for the questions being asked. Adding an identity field without a clear use can create governance and data quality problems.
terpret reports with identity limits in mind
Reporting identity settings can affect how GA4 deduplicates or models users. Compare user counts only when identity settings and consent conditions are understood; session and event counts answer different questions.
Document which identifier is sent, how it is generated, what happens when users sign in or out, and how consent is handled. Analytics identifiers support measurement; they do not prove that every observed record maps to a unique human.
How did this article land?
Choose one reaction. You can change it anytime.