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.
What this means
In GA4's e-commerce model, every product is an entry in the items array attached to events like view_item, add_to_cart, and purchase. The item_category parameter on each entry feeds the item category dimension, letting you roll commerce metrics up to category level.
GA4 supports a hierarchy: item_category, item_category2, through item_category5, representing nested levels such as Apparel > Men > Shirts. Each level becomes its own dimension you can break down by.
- Read from item_category on the items array
- Applies across commerce events (view, cart, purchase)
- Hierarchy: item_category through item_category5
Why consistent tagging matters
The dimension is only as clean as the data layer feeding it. If the same category is sent as 'Shoes' on one page and 'Footwear' on another, GA4 reports them as two categories and the rollup fragments. Categories are free-text, so casing and naming discipline are on you.
Missing item_category on some events also breaks funnels: a product viewed without a category and purchased with one will not line up. Validate that every commerce event sends the same category fields in the same shape.
- Free-text values fragment on naming/casing drift
- Missing category on some events breaks funnels
- Validate consistent item fields across all events
How it appears in analytics and logs
An item category value reflects what your data layer sent in item_category. Blank or '(not set)' categories mean the items array did not include the field for those products.
Diagnostic use case
Analyse revenue, views, and add-to-carts by product category to see which parts of the catalog drive the business.
What WebmasterID can help detect
WebmasterID captures structured commerce event parameters first-party, so category attribution holds without third-party cookies, provided your data layer tags items consistently.
Common mistakes
- Sending inconsistent category names across pages.
- Omitting item_category on some commerce events.
- Encoding non-product data into category fields.
Privacy and accuracy notes
Item categories describe products, not people. They carry no personal data unless a category name is misused to encode something user-specific, which should be avoided.
Related pages
- Item brand dimension
The item brand dimension groups products by their brand in e-commerce reports. GA4 reads it from the item_brand parameter on the items array. This page explains how it is populated, how it differs from device brand, and why marketplaces with many brands must tag it carefully.
- 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.
- 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.
- Events documentation
Send a consistent items array on commerce events.
Sources and verification notes
- developers.google.com — GA4 ecommerce item parametersDocuments item_category through item_category5 on the items array.
- developers.google.com — GA4 Measurement: item parametersReference for item-level parameters in commerce 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.