Analytics and Tracking

Item Array

Also called items array, items parameter

The list of product details carried inside a GA4 ecommerce event, one entry for each product involved.

Quick facts: Item Array

Category
Analytics and Tracking
Also called
items array, items parameter
Level
Intermediate
Affects
Product reporting, ecommerce funnels, dynamic product ads, feed matching
Where to see it
GA4 DebugView, Google Tag Manager Preview, browser dataLayer inspection
In this article4
  1. How the item array works
  2. Why the item array matters
  3. Common mistakes with the item array
  4. How to act on it

How the item array works

Every GA4 ecommerce event carries a list of the products it concerns, and that list is the item array. Each entry describes one product: its identifier and name, which are the required pair, plus optional detail such as brand, category, variant, price, quantity, the discount applied and where in the shop it was found.

The same structure is used at every stage. A product page view sends one entry; a basket view, a checkout start and an order send one entry per line. That is deliberate — because the shape does not change, GA4 can follow a single product from the moment it is seen to the moment it is bought or returned, and report on it at each step.

The array lives inside the event, not beside it. Send the event without it and you still get a count of the action, but nothing about what the action was about.

Why the item array matters

All product-level reporting comes from here. Which products are viewed but never added, which are added but never bought, which quietly carry the revenue while getting no attention on the homepage — none of that exists as a report unless the array is populated correctly and consistently.

It also feeds outside GA4. Google Ads and Meta both use product identifiers to match your website activity to a product feed, and dynamic product ads only work when the identifier sent by the website is the identifier sitting in the feed. A mismatch does not throw an error; the ads simply show the wrong products or nothing at all.

Common mistakes with the item array

Inconsistency is the big one. If the product page sends a SKU, the basket sends a database row number and the order confirmation sends the product’s URL slug, GA4 treats them as three different products and the funnel for any single item collapses. Pick one identifier and use it everywhere, including in your feeds.

The second is a partial array — an order that lists the first line and forgets the rest, usually because the code loops incorrectly. The order value stays right, so nothing looks broken, but product reporting silently under-counts. The third is filling the array with everything available: a dozen custom parameters that nobody will ever open a report for. Send what you will use.

How to act on it

Agree the identifier with whoever owns the shop data before any tagging starts, and write it down: one field, used by the website, the analytics events and every product feed. That single decision prevents most of the problems described here.

Then verify with a real product. Follow one item through a listing page, a product page, the basket, the checkout and the order, checking in GA4’s DebugView that the identifier and name are identical at every step and that the quantities are right. Check a multi-line order too, because that is where loops break. Getting this right is the foundation of useful ecommerce tracking, and it is worth settling during a GA4 setup rather than discovering it in a report months later.

Do and do not

Do

  • Use one product identifier across site, events and feeds
  • Send the array on every product-related ecommerce event
  • Test a multi-line order, not just a single item

Do not

  • Change the identifier between page, basket and order
  • Send an ecommerce event with an empty array
  • Add custom fields you will never report on

Questions people ask about this

Which fields in the item array are actually required?

An item identifier or an item name — GA4 needs at least one of the two, and sending both is the sensible default. Everything else is optional but useful: price, quantity, brand, category and variant are what make the product reports worth reading. The identifier matters most, because it is what links your website data to your product feeds.

Should the item array be sent on every ecommerce event?

On every event that concerns products, yes. Viewing an item, adding to the basket, viewing the basket, starting checkout and purchasing should all carry it. Events that are not about specific products, such as a newsletter signup, do not need it. Sending an ecommerce event with an empty array gives you a count and no ability to explain it.

What happens if the same product has different identifiers on different pages?

GA4 records them as separate products. Your funnel for that item breaks into fragments, the product reports understate every version, and dynamic product ads that rely on matching the identifier to a feed stop matching. Nothing warns you, because each individual event is technically valid. Agree one identifier across the site and feeds before tagging.

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.