User-scoped parameters and properties
User-scoped parameters — set as user properties — describe an attribute of the user that persists across their events, such as a membership tier or preferred language, rather than a fact about one event. They contrast with event-scoped parameters (per event) and item-scoped ones (per product). GA4 reports them as user dimensions once registered. The scope you choose decides whether a value follows the user or stays with a single event.
What user scope means
A user property is a value GA4 associates with the user and applies to their subsequent events until changed — for example a plan level or a UI preference. Unlike an event parameter, you do not resend it on every event; you set it once and it persists. Registered user properties become user-scoped custom dimensions you can use to segment reports.
Choosing the right scope
Three scopes coexist: event (one event), item (one product in an items array), user (the person across events). Misplacing a value wastes effort or breaks reporting — sending a durable attribute as an event parameter on every hit is redundant, while putting a per-event fact at user scope erases its variation. Decide by asking whether the value belongs to the action, the product, or the person — and keep user-scope values non-identifying.
- User properties persist across a user's events
- Set once, not resent per event
- Registered user properties become user-scoped dimensions
How it appears in analytics and logs
An attribute you expect on every event but see only sometimes may belong at user scope (a user property) rather than being resent as an event parameter.
Diagnostic use case
Store durable user attributes as user properties (user scope) and per-action facts as event parameters, so each value reports at the right level.
What WebmasterID can help detect
WebmasterID's cookieless model avoids per-user identity; the GA4 user-scope concept is documented here so you can map durable attributes correctly.
Common mistakes
- Storing personal identifiers as user properties.
- Resending a durable attribute as an event parameter every hit.
- Putting a per-event value at user scope and losing its variation.
Privacy and accuracy notes
User properties must never carry personal identifiers or sensitive categories. Keep them to coarse, non-identifying attributes; this is educational, not legal advice.
Related pages
- Item-scoped event parameters
Item-scoped parameters are parameters attached to each entry inside an e-commerce event's items array — item_id, item_name, price, quantity, and custom item parameters — describing the product rather than the event as a whole. They contrast with event-scoped parameters that describe the event (currency, value, transaction_id). Knowing the scope determines where a parameter belongs and how it can be reported in GA4.
- User properties vs event parameters
User properties are attributes that describe a user across all their events — a plan tier, a preferred language, a logged-in state — rather than a single action. They differ from event parameters, which describe one event. Used well, user properties let you segment behaviour by audience. Used badly, they become a place where people stash personal data, which is exactly what they must not hold.
- Event parameters: adding context safely
Event parameters are the key-value details attached to an event: which button, which product, which step. They are what turns a bare event name into something analysable. The craft is choosing a small, stable set of parameters with consistent names and values — and the discipline is keeping every one of them free of personal data, because parameters are stored and widely visible in tooling.
- Privacy-first analytics
Segment without per-user identifiers.
Sources and verification notes
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.