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.
Two scopes in one event
A GA4 e-commerce event has event-level parameters (e.g. currency, value, transaction_id) and an items array where each entry carries item-level parameters (item_id, item_name, item_category, price, quantity). The same conceptual field can exist at both scopes for different reasons. Custom parameters can be registered at item scope too, so a per-product attribute reports against the item, not the whole event.
Why scope decides reporting
GA4 reports item-scoped parameters in item dimensions/metrics and event-scoped parameters at the event level. Put a product attribute at event scope and it cannot be broken down per product; put an event-level fact inside items and it is misattributed. Registering item-scoped custom dimensions is required for them to surface. Match each parameter's scope to the question you want to answer.
- Event-scoped: currency, value, transaction_id
- Item-scoped: item_id, name, price, quantity, custom item params
- Scope determines whether it reports per item or per event
How it appears in analytics and logs
A product attribute that never appears in item reports is often placed at event scope instead of inside the items array, so GA4 cannot attribute it per item.
Diagnostic use case
Put product attributes in the items array (item-scoped) and event-level facts at the top level (event-scoped) so e-commerce reporting attributes data correctly.
What WebmasterID can help detect
WebmasterID's first-party model keeps a simple event schema; the item-scoped vs event-scoped distinction is a GA4 e-commerce structure documented here.
Common mistakes
- Placing product attributes at event scope, losing per-item reporting.
- Forgetting to register item-scoped custom dimensions.
- Putting personal data into item fields.
Privacy and accuracy notes
Item-scoped parameters describe products, not people. Keep them to catalogue attributes; do not smuggle personal data into item fields.
Related pages
- 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.
- E-commerce events: the funnel before purchase
E-commerce events are a recommended set that model the shopping funnel before and around purchase: view_item, add_to_cart, begin_checkout, add_payment_info, and purchase. Each shares a common items array, so the same product schema flows through the journey. Implemented consistently, they let you see where buyers drop off — and they carry product data, never buyer identity.
- 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.
- Events reference (docs)
How parameters attach to events.
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.