Event-scoped describes a dimension or metric in GA4 whose value belongs to a single event and nothing else. Page path, link URL and a custom form_name are all event-scoped: each describes the moment it was sent with, not the whole visit and not the visitor.
How event scope works
GA4 attaches every dimension and metric to a level, called its scope. The levels you meet most often are:
- Event: describes one action, such as the page path on a page_view or the file name on a download.
- Session: describes the whole visit, such as session source or landing page. These are built in; GA4 does not let you create your own session-scoped custom dimensions.
- User: describes the person, strictly the browser or signed-in ID, across visits. First user source is one; a custom value such as customer type is another.
- Item: describes a product inside an ecommerce event, such as its category.
When you register a custom dimension, you choose its scope. Most custom parameters sent with events, such as which form, which button or which plan, belong at event scope.
Scope matters when you combine dimensions and metrics in a report. Pair an event-scoped dimension with an event-level metric, such as Page path with Views, or form_name with Event count, and the figures are clean. Pair it with a session or user metric and GA4 has to place each session or user on every row it touched. A session that viewed three pages appears on three page path rows, so the Sessions column adds up to more than the real total.
Why it matters
A large share of “GA4 numbers don’t add up” worries come back to scope. A business owner sees 1,000 sessions in the overview, then a pages report where sessions sum to well over that, and assumes the tracking is broken. It is not: the same session is counted once on each page it included. Knowing the scope tells you which totals you can add up and which you cannot.
It matters at setup too. GA4 fixes the scope of a custom dimension when you create it and does not let you change it afterwards. Choosing wrongly means archiving the dimension and creating a new one, which starts collecting from that day and leaves the history behind.
Common mistakes
- Adding up overlapping rows. Summing sessions or users across an event-scoped dimension double counts.
- Registering a fact about the person at event scope. A value such as “trade customer” sent once at login appears only on that one event. If you want to filter all of a customer’s activity by it, it should be user-scoped.
- Registering a fact about one action at user scope. A user-scoped value is overwritten by the latest one sent, so storing “form used” at user scope loses every earlier form.
- Confusing Page path with Landing page. Page path is event-scoped and covers every page viewed; Landing page is session-scoped and covers only the first. To judge where ad traffic arrives, use Landing page.
- Expecting a parameter to fill other events. An event-scoped value sent only with form_submit shows as (not set) on every page_view and scroll event.
How to act on it
- Before registering a custom dimension, ask what it describes: one action (event), the person (user) or a product (item).
- When building a report or exploration, pair dimensions with metrics at the same level where you can: event dimensions with event counts, session dimensions such as session source with sessions.
- When totals look wrong, check whether a session or user metric is sitting beside an event-scoped dimension before suspecting the tracking.
- Note the scope of every custom dimension in your tracking plan, so whoever reads the reports next knows how to interpret them.
Getting scope right is part of the measurement groundwork in performance marketing, where reports have to stand up when budgets are decided.