What item_id and item_name do
These are the two fields that identify a product inside a GA4 ecommerce event. GA4 requires at least one of them, and sending both is the sensible default because they do different jobs. The identifier is the machine key — a SKU or product code that never changes and that also appears in your product feeds. The name is what a human reads in a report.
Keeping both matters because each is useless alone in a different way. An identifier on its own gives you accurate reports that nobody can interpret without a lookup table. A name on its own gives you readable reports that fall apart the moment a product is renamed, because GA4 then treats the old name and the new one as separate products with separate histories.
Why item_id and item_name matter
The identifier is the join between systems. Your website sends it, your Merchant Center or Meta catalogue holds it, and dynamic product ads only work when the two agree. If a shopper views a product and the identifier the website reports does not exist in the feed, the retargeting ad cannot show that product — and nothing tells you, because both systems consider themselves correct.
The name is what makes the analytics usable by the people who run the business. A product report a shop owner can read without translating codes is a report they will actually use, and that is worth as much as the accuracy.
Common mistakes with item_id and item_name
The most damaging is an identifier that varies by page — a SKU on the product page, an internal database row number in the basket, a URL slug on the confirmation. Every event is individually valid, so nothing breaks visibly, but the product’s journey splits into fragments and no funnel for it can be trusted.
The second is using a variant-level identifier in one place and a parent-level one in another, so a size or colour choice appears as a different product depending on the step. Decide which level you report at and hold to it. The third is names carrying formatting from the shop database — trailing spaces, stray HTML, or a price appended to the title — which produces near-duplicate rows in every report. The last is renaming products freely and expecting history to follow: it will not, unless the identifier stayed the same.
How to act on it
Choose the identifier once, before any tagging is written, and make it the same field your product feed uses. Write it down where the developer, the person managing the feed and whoever reads the reports can all see it. Almost every problem on this page comes from that decision being made three separate times by three separate people.
Then check it. Follow one product from listing page to order confirmation in DebugView and confirm the identifier and name are byte-identical at every step, then look for near-duplicate names in the GA4 product report, which is where formatting problems surface first. If the identifiers on the site and in the feed disagree, fix the site rather than the feed — the feed is what the ad platforms and your ecommerce SEO work both depend on, and it should stay the reference.
