Item list dimension
The item list dimension identifies the list context in which a product appeared — a search results page, a category grid, a recommendation rail. GA4 reads item_list_id and item_list_name from view_item_list and select_item events. This page explains list context and why consistent list naming makes it analyzable.
What this means
A product is almost always seen inside a list: search results, a category grid, a 'related products' rail, or a wishlist. GA4's item list dimension captures that context via item_list_id and item_list_name on view_item_list (the list was shown) and select_item (an item in it was clicked).
This answers a merchandising question the item dimensions alone cannot: not just which products perform, but which surfaces make them perform. The same product can convert well from search and poorly from a rail.
- Captures the list a product was seen/clicked in
- Fields: item_list_id, item_list_name
- Events: view_item_list and select_item
Why list naming discipline matters
List value is only useful if lists are named consistently. If 'Search Results' is also sent as 'search', 'SRP', and '(not set)' from different templates, the dimension fragments and you cannot compare surfaces. Define a stable vocabulary of list names and apply it everywhere a list renders.
List scope can also be ambiguous on pages with multiple rails. Decide whether each rail is its own list or part of a page-level list, and tag accordingly, so a click is attributed to the surface that actually earned it.
- Inconsistent list names fragment the dimension
- Define a stable list-name vocabulary
- Decide rail-level vs page-level list scope
How it appears in analytics and logs
An item list value reflects the list context your events sent. Missing list data means view_item_list / select_item events omit the list fields or are not firing.
Diagnostic use case
See which product lists — search, category, recommendations — surface items that get clicked and bought, to optimize where products appear.
What WebmasterID can help detect
WebmasterID captures list-context parameters on commerce events first-party, so list-attribution analysis holds without third-party cookies when your data layer sets the fields.
Common mistakes
- Naming the same list differently across templates.
- Firing select_item without item_list context.
- Leaving list scope ambiguous on multi-rail pages.
Privacy and accuracy notes
Item list identifiers describe merchandising surfaces, not visitors. They are commerce metadata with no personal data.
Related pages
- Item category dimension
The item category dimension groups products in e-commerce reports — Apparel, Electronics, and so on. GA4 reads it from item_category (through item_category5) on the items array of commerce events. This page explains the category hierarchy, how it is populated, and why inconsistent tagging fragments reports.
- Promotion dimension
The promotion dimension measures internal promotions — banners, hero slots, on-site campaigns — distinct from paid ad campaigns. GA4 reads promotion_id, promotion_name, creative_name, and creative_slot from view_promotion and select_promotion events. This page explains the model and how it differs from UTM campaigns.
- Item variant dimension
The item variant dimension separates variations of the same product — a shirt's size or color. GA4 reads it from the item_variant parameter on the items array. This page explains how variants relate to item ID and name, and why mixing variant axes into one field undermines analysis.
- Events documentation
Set item_list_id/name consistently on commerce events.
Sources and verification notes
- Google Analytics Help — [GA4] Measure ecommerce (item lists)Documents item_list_id/item_list_name and related events.
- developers.google.com — GA4 Measurement: view_item_list / select_itemReference for item-list parameters and events.
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.