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.
