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.
What this means
An item variant is a specific version of a product that shares an item ID family but differs on an attribute — the same t-shirt in Large/Blue versus Small/Red. GA4's item_variant parameter on the items array carries this, enabling variant-level breakdowns of views, carts, and revenue.
Variant sits alongside item_id, item_name, item_category, and item_brand. Together they describe a purchasable line; variant is the axis that distinguishes otherwise identical entries.
- Variant = a specific version of a product
- Read from item_variant on the items array
- Complements item_id, item_name, category, brand
Why variant tagging is tricky
A single product can vary on several axes at once — size and color and material. Cramming all of them into one item_variant string (for example 'L / Blue / Cotton') makes the dimension hard to slice, because you cannot isolate 'color = Blue' across sizes.
The cleaner pattern is to keep item_variant for the primary axis and push secondary axes into custom item parameters, then report on each independently. Decide a convention up front; retrofitting variant structure after data has accumulated rarely reconciles cleanly.
- Multiple axes crammed into one string limit slicing
- Use custom item parameters for secondary axes
- Set a convention up front; retrofits rarely reconcile
How it appears in analytics and logs
An item variant value reflects the item_variant string sent for a product. Sparse variant data usually means the field was only tagged on some events or some products.
Diagnostic use case
Find which specific variants — sizes, colors, configurations — sell and which sit idle, to guide inventory and merchandising.
What WebmasterID can help detect
WebmasterID captures the full items array first-party, so variant-level commerce reporting works without third-party cookies when your feed populates item_variant.
Common mistakes
- Packing multiple variant axes into one item_variant string.
- Tagging variant on only some commerce events.
- Reusing variant strings inconsistently across products.
Privacy and accuracy notes
Item variant describes a product configuration, not a person. It is commerce metadata and carries 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.
- 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.
- 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.
- Events documentation
Populate item_variant consistently in the items array.
Sources and verification notes
- developers.google.com — GA4 ecommerce item parametersDocuments item_variant on the items array.
- developers.google.com — GA4 Measurement: item parametersReference for item_variant 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.