Analytics and Tracking

item_brand, item_category, item_variant

Also called Product attributes

Optional GA4 product attributes that group items by maker, by section of the shop and by version sold.

Quick facts: item_brand, item_category, item_variant

Category
Analytics and Tracking
Also called
Product attributes
Level
Beginner
Affects
Product reporting, merchandising decisions, stock planning, feed consistency
Where to see it
GA4 DebugView, GA4 product reports, Google Tag Manager Preview
In this article4
  1. What item_brand, item_category and item_variant record
  2. Why item_brand, item_category and item_variant matter
  3. Where item_brand, item_category and item_variant go wrong
  4. How to act on it

What item_brand, item_category and item_variant record

These three fields sit alongside the product identifier and name inside a GA4 ecommerce event, and they exist to group products rather than to identify them. Brand records who makes the item. Category records where it sits in your shop’s structure, and GA4 accepts several levels of it, so a deep catalogue can send a top-level section and its subsections rather than flattening everything into one label. Variant records which version of the product this is: the size, the colour, the capacity, the flavour.

All three are optional. GA4 will accept an event without them and the order value will still be right. What you lose is the ability to ask any question broader than one product at a time.

Why item_brand, item_category and item_variant matter

They turn a long list of products into something a business owner can act on. Without them the product report is a flat table sorted by revenue; with them you can see which section of the shop is growing, which brand people browse but rarely buy, and which sizes or colours are worth restocking. For a shop with a wide catalogue that difference decides whether the reports get opened at all.

Variant is the one most often left out and the one that pays back fastest. Returns, stock-outs and abandonment usually concentrate in specific versions of a product rather than the product as a whole, and without the field they are invisible — the parent product just looks moderately disappointing.

Where item_brand, item_category and item_variant go wrong

Drift is the usual fault. The category on the product page comes from the page template, the one in the basket comes from a different database field, and the two disagree — so the same order counts under two sections. The fix is to take all three attributes from one source in the shop database and pass them through unchanged at every step.

Free text is the second problem. Brands entered by hand end up with variant spellings and stray capitalisation, and each becomes its own row in the report. Variant has the same weakness when the colour comes from a supplier’s description rather than a controlled list.

The third is treating category as a marketing label. Filling it with a campaign name or a promotional phrase makes it useless for structural reporting, and it is not the place for it. And if your product genuinely has no versions, leave variant out rather than sending something like “default”, which creates a row that means nothing.

How to act on it

Populate all three from the shop database, using the same values that drive your navigation and your product feed. Consistency between the site, the analytics and the feed is worth more than richness, because it is what lets you compare a GA4 report with what the ad platforms see.

Then read them at the level you can act on. Category performance tells you where to spend attention and where to change navigation, brand performance tells you what to stock and what to negotiate on, and variant performance tells you what to reorder. Once these fields are clean, the same structure carries into your product feed and into ad platform reporting, which is why they are worth agreeing during a GA4 ecommerce setup rather than added later.

Do and do not

Do

  • Take all three from one source in the shop database
  • Use controlled values, not hand-typed brand or colour text
  • Match the categories to your navigation and product feed

Do not

  • Put campaign or promotional labels in the category field
  • Send a placeholder variant for products with no versions
  • Let the category differ between product page and basket

Questions people ask about this

Are these three fields required in GA4 ecommerce events?

No. Only an item identifier or an item name is required, and an order will report correctly without brand, category or variant. What you lose is grouped reporting: no view of which section of the shop is performing, which brands sell through, or which sizes and colours move. For a catalogue of any size, that loss is significant.

How many category levels should I send?

Send the levels your shop navigation actually uses, from the broadest section downwards, and no more. GA4 supports a nested structure, so a clothing shop might send a top-level section, then a garment type, then a use case. Inventing depth you do not use in navigation makes the reports harder to read without adding any insight.

Should item_variant hold size, colour, or both?

Whichever combination identifies the version a customer actually buys, expressed the same way every time. If a shopper picks both a size and a colour, the variant should describe both, using a fixed separator and controlled values from your database. The rule that matters is consistency: the same physical version must always produce the same variant string.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.