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.
