GA4 reporting identity
Reporting identity is the GA4 setting that decides how events are joined into individual users for reporting: User-ID, Google signals, device, and modeling, applied in a chosen order (Blended, Observed, or Device-based). Because attribution depends on knowing which touches belong to the same person, the identity space directly affects path lengths, deduplicated user counts, and credit distribution.
The identity spaces
GA4 can use, in priority order: a User-ID you provide when signed-in users are known; Google signals from consenting signed-in Google users; device identifiers; and behavioral modeling to fill gaps. The chosen reporting identity (Blended, Observed, or Device-based) sets which of these GA4 uses and in what order.
The more identity GA4 can resolve, the more it can join touches across sessions and devices into one user.
Why it changes attribution
Attribution credit assumes you can tell which touchpoints belong to the same journey. A richer identity space stitches more touches together, producing longer, more complete paths and more accurate multi-touch credit.
A device-only space fragments cross-device journeys into separate users, inflating user counts and shortening paths — which biases models toward whatever touch happened on the converting device.
- Spaces: User-ID, Google signals, device, modeling
- Modes: Blended, Observed, Device-based
- Richer identity = longer, more complete paths
How it appears in analytics and logs
If paths look unusually short and users unusually high, a device-based identity may be splitting one person across devices, breaking multi-touch credit.
Diagnostic use case
Check the reporting identity before trusting cross-session paths — a device-only space fragments the same person into several users and shortens paths.
What WebmasterID can help detect
WebmasterID's first-party, consent-aware session model gives an independent view of how fragmented your traffic is across devices and sessions.
Common mistakes
- Comparing user counts across different reporting identities.
- Ignoring identity when cross-device paths look broken.
- Assuming device-based and blended report the same numbers.
Privacy and accuracy notes
Identity options like Google signals and modeling are bounded by consent and privacy controls. Educational, not legal advice on identity configuration.
Related pages
- Cross-device attribution and its broken paths
Cross-device attribution is the problem of a single person using multiple devices in one journey. Default cookie-based tracking treats each device as a separate visitor, so paths fracture and credit lands on the wrong channel. Closing the gap usually requires a logged-in identity — which carries its own privacy weight.
- GA4 attribution settings
GA4's attribution settings (Admin > Attribution settings) define the property-wide reporting attribution model and the lookback windows for acquisition and other conversions. Changing them re-attributes credit across the property's reports going forward and, for the model, retroactively in attribution reports. Understanding these settings is prerequisite to reading any GA4 attribution number correctly.
- Deterministic vs probabilistic matching
Identity resolution in attribution uses two approaches. Deterministic matching links touchpoints when they share a known, persistent identifier (a logged-in user ID, a hashed email). Probabilistic matching infers that two touchpoints belong to the same user from circumstantial signals — IP, device, behavior — without a confirmed identifier. The two differ sharply in accuracy and privacy posture.
- Privacy-first analytics
Consent-aware first-party identity for measurement.
Sources and verification notes
- Google Analytics Help — Reporting identityDocuments identity spaces and Blended/Observed/Device modes.
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.