Event count scope dimension
Event scope is the narrowest GA4 dimension scope: an event-scoped dimension's value belongs to one specific event, not to the whole session or user. GA4 assigns scope per dimension — event, session, user, or item — and that scope governs how values aggregate. Combining dimensions and metrics from incompatible scopes in one report produces (not set) rows or inflated counts, so understanding scope is essential to reading GA4 correctly.
What this means
Every GA4 dimension and metric has a scope: event (this single event), session (this visit), user (this person across visits), or item (this product). Event scope is the most granular — an event-scoped dimension value, such as a custom parameter, is bound to the one event it was attached to.
Scope determines how GA4 rolls values up. A session-scoped value applies to every event in the session; an event-scoped value does not.
Why mixing scopes breaks reports
GA4 can only combine dimensions and metrics whose scopes are compatible. Pair an event-scoped dimension with a user-scoped metric and rows collapse to (not set), or counts inflate because the engine cannot reconcile the levels. The fix is to keep each report within one coherent scope, or to use explorations that respect scope boundaries. Treat (not set) from a cross-scope query as a design signal, not missing data.
- Event scope binds a value to one event
- Scopes: event, session, user, item
- Incompatible scopes yield (not set) or inflated counts
How it appears in analytics and logs
An event-scoped value describes a single event. (not set) rows or strange totals in a report often mean event-, session-, and user-scoped fields were mixed.
Diagnostic use case
Use event-scope awareness to combine only compatible dimensions and metrics, avoiding the (not set) and double-counting artefacts of cross-scope queries.
What WebmasterID can help detect
WebmasterID encourages scope-consistent reporting so per-event, per-session, and per-user questions are answered with matching fields rather than blurred together.
Common mistakes
- Pairing event-scoped dimensions with user-scoped metrics.
- Reading cross-scope (not set) rows as missing data.
- Assuming a custom dimension's scope without checking it.
Privacy and accuracy notes
Scope is a structural property of dimensions, not user identity. It governs aggregation, not what personal data is collected.
Related pages
- Custom dimension
A custom dimension lets you report on an attribute GA4 does not collect by default — author, plan tier, content type — by registering an event or user parameter as a dimension. It must be defined before data flows, has event-scoped and user-scoped variants with quota limits, and is vulnerable to high cardinality: registering a near-unique value collapses reports into '(other)' and can edge toward identifying users.
- Is conversion event dimension
The is conversion event dimension indicates whether a given event is marked as a key event — GA4's term for a conversion — in your configuration. GA4 derives it from each event's key-event setting, which you toggle per data stream. Because marking takes effect going forward and is configured at the stream level, the same event name can be a conversion in one stream and not another, and historical events are not retroactively reclassified.
- (not set) and Unassigned values
GA4 shows `(not set)` when no value was collected for a dimension at the time data was recorded, and `Unassigned` when traffic could not be matched to any defined channel group. These are not errors so much as honest placeholders — but each has distinct, documented causes worth diagnosing rather than ignoring. This page separates the placeholders and what produces them.
- Event explorer
Build scope-consistent event reports.
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.