Meta Ads

Product ID

Also called Item ID, retailer ID

The unique code identifying one item in your catalogue and tying your website events back to it.

Quick facts: Product ID

Category
Meta Ads
Also called
Item ID, retailer ID
Level
Intermediate
Affects
Dynamic retargeting, catalogue match rate, per-product reporting
Where to see it
Meta Commerce Manager, Meta Events Manager, Meta Pixel Helper, your shop's feed export
In this article4
  1. How a product ID works
  2. Why the product ID matters
  3. Where product IDs go wrong
  4. How to act on it

How a product ID works

Every row in a catalogue needs a code that belongs to that item and to nothing else. That is the product ID. Meta uses it as the join between three things: the row holding the price and image, the website event fired when someone views or buys the item, and the ad that gets built from the row. Change any one of those and the join breaks.

The code itself does not have to be pretty. It can be your internal stock code, a shop-generated number, or a barcode-style identifier. What it must be is stable and identical everywhere. A shop platform that adds a prefix to its exported feed while sending the bare number in the pixel event creates two different codes for one product, and no amount of budget will make dynamic ads work until that is reconciled.

Variants complicate it. If a shirt comes in several sizes and colours, you decide whether each combination gets its own ID or whether they share the parent item’s. Both approaches are workable; mixing them within one catalogue is not.

Why the product ID matters

It is the difference between showing someone the jacket they looked at and showing them a generic brand advert. Retargeting a browsed item only works when the browsing event and the catalogue row carry the same code, so the whole promise of dynamic advertising rests on this small field.

It also decides whether your reporting is readable. Sales, spend and return get attributed per ID, so inconsistent codes scatter one product’s performance across several rows and make the best and worst sellers impossible to see.

Where product IDs go wrong

Silent mismatch is the common failure, because nothing errors. The catalogue imports, the pixel fires, the campaign spends, and the ads simply fall back to showing whatever the system can. The account looks live while the mechanism that justified it is not working.

Reusing a retired code for a new product is the other one. Old browsing data attaches to the new item, and the wrong people are retargeted with something they never looked at. Case differences, stray spaces and platform prefixes belong in the same family: to a computer these are different codes, whatever they look like to a person.

How to act on it

Verify rather than assume. Open a product page with the Meta Pixel Helper or the Events Manager test tool, read the identifier that actually leaves the browser, then find that exact string in your exported feed. If they differ by so much as a prefix, fix it at the source in your shop rather than editing the catalogue by hand.

Decide your variant rule once and apply it to the whole product catalogue. Never recycle an identifier from a discontinued item; retire it. And whenever you migrate shop platform or re-import stock, re-run the check, because a platform change is the single most likely moment for these codes to shift underneath a working dynamic product ads setup.

Do and do not

Do

  • Read the identifier the pixel actually sends, then match the feed
  • Keep one variant rule across the whole catalogue
  • Re-check identifiers after any shop platform migration

Do not

  • Reuse a code from a discontinued product
  • Assume a prefix added on export is harmless
  • Edit identifiers by hand inside Commerce Manager

Questions people ask about this

Can I use my SKU as the product ID?

Yes, and it is usually the sensible choice, because your stock system already treats it as unique and stable. The only requirement is that the same string appears in the catalogue feed and in the events your website sends. If your shop platform alters the SKU on export, use whatever it actually exports rather than what you expected.

What happens if the pixel sends an ID that is not in my catalogue?

The event is recorded but cannot be matched to an item, so it cannot power dynamic retargeting for that product. Nothing visibly fails; the ads just fall back to less relevant items. The mismatch shows up as a low catalogue match rate in Events Manager, which is worth checking before assuming a targeting or creative problem.

Should each size and colour have its own product ID?

It depends on how you sell. Separate identifiers let you advertise a specific variant and report on it, which suits shops where colour or size drives the choice. A shared parent identifier keeps the catalogue simpler where variants are interchangeable. Choose one approach and apply it consistently, because a mixed catalogue is very hard to debug later.

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.