Study first
Review the ideas behind the questions
Review how GA4 treats signed-in identity before using User-ID in reports or audiences. Focus on the identifier value, login and logout states, reporting identity, and where raw user IDs can be analyzed.
Keep User-ID values safe and stable
GA4 User-ID works only when the identifier is a real, stable business ID for one person and is safe to send. A bad value can merge people, expose sensitive data, or make reports harder to trust.
- Each signed-in person needs a unique and persistent GA4 user ID.
- Do not send a GA4 user ID value that another party could use to identify the person.
- Do not register raw user IDs as custom dimensions just to expose them in reports.
In Practice
Identity bugs are data bugs
A shared test ID is not harmless in production. It can collapse different customers into one GA4 identity and make user counts, journeys, and audiences unreliable.
Raw IDs need a controlled path
If analysts need raw user-level joins, plan BigQuery access and governance instead of adding a raw user ID custom dimension to everyday reports.
Common mistakes
Using the customer email address directly as the GA4 user ID.
Use a non-PII identifier and confirm the privacy notice before sending it to GA4.
Q&A
Can GA4 fix a shared User-ID value after it has already collected production data?
Do not plan on that. The source-backed fix is to prevent shared IDs before launch because GA4 interprets each user ID as a separate user.
Should a raw user ID become a custom dimension for analysts?
No. GA4 recommends against a User-ID custom dimension because high-cardinality identifiers can hurt report quality.
Match tagging state to reporting identity
The implementation has to send the right identity state, and the property has to use a reporting identity that can read it. Otherwise User-ID collection may not change the reports the team expects.
- If a user has never signed in, do not send the GA4 user ID parameter.
- When a signed-in user logs out, clear the GA4 user ID with null.
- Use Blended or Observed reporting identity when reports need User-ID de-duplication.
In Practice
Late login needs an update
If the ID becomes available after the page loads, update GA4 for later events on that page instead of pretending earlier anonymous hits already carried the ID.
Identity settings do not rewrite history
User-ID is forward-looking from implementation. Old collected data is not reprocessed and attached to user IDs later.
Common mistakes
Leaving the old user ID active after logout because the browser session is still open.
Clear the GA4 user ID with null after logout so later events are not tied to the signed-in identity.
Q&A
Does Device based reporting identity use collected User-ID values?
No. Device based identity uses only the device ID, while Blended and Observed include User-ID when it is collected.
Where should raw user ID analysis happen when standard reports do not expose the value?
Use User Explorer for individual review or BigQuery export for raw ID analysis instead of expecting most explorations to show raw IDs.
Treat export and audience identity as governed data
User-ID can affect more than user counts. It can shape audience export behavior and put raw identifiers into analysis systems, so identity setup needs privacy and access review before activation.
- When GA4 is linked to BigQuery, collected user ID information can be exported regardless of consent status.
- A GA4 User-ID remarketing audience uses the user identifier and the last associated device identifier for each logged-in user.
- Raw GA4 user ID values are not standard dimensions in most reports and explorations.
In Practice
Audience exports need expectation setting
Do not promise that a User-ID audience export represents every device ever used by a customer. Use the documented last-device behavior when explaining reach.
BigQuery needs access control
Treat BigQuery export as a sensitive data path when User-ID is collected. The warning is about the export behavior, not a standard-report display setting.
Common mistakes
Assuming raw user IDs are hidden everywhere because they do not appear in most standard reports.
Check User Explorer and BigQuery export separately because those are supported raw User-ID analysis paths.
Q&A
Does BigQuery export automatically suppress collected user IDs for users without consent?
No. The GA4 User-ID page says collected user ID information is exported to BigQuery regardless of users consent status when Analytics is linked to BigQuery.