How a content ID works
When someone views a product, adds it to a basket or buys it, your website sends an event to Meta. That event carries parameters describing what happened, and the content identifier is the parameter that says which item. It travels alongside the content type, the value and the currency, and it is sent as a list because a basket or an order can contain several items at once.
On its own the identifier means nothing. It becomes useful when Meta finds the same string in your catalogue, at which point the event stops being an anonymous page view and becomes a recorded interest in a specific product with a known price and image. That is what allows an ad to show the exact item someone was looking at.
The same identifier must be sent whether the event comes from the browser or from your server through the Conversions API, otherwise the two versions of one event will not deduplicate cleanly and your reporting will double-count.
Why content IDs matter
Everything downstream depends on them. Dynamic retargeting, product-level reporting, value-based bidding and cross-sell audiences all need to know which item was involved, and none of them can infer it from a page URL. A shop sending events without item identifiers has working analytics and broken commerce advertising at the same time.
They also feed the catalogue match rate shown in Events Manager, which is the quickest health check available on this whole setup. A poor match rate almost always points at identifiers rather than at anything more exotic.
Common mistakes with content IDs
Sending the wrong field is the frequent one. Shop platforms often expose a database row number, a variant code and the stock code that actually appears in the feed, and it is easy to pick the one that reads most like an identifier rather than the one the catalogue uses.
Formatting differences cause the rest. A string sent where a list is expected, an identifier with a prefix on one side and not the other, or a variant code sent while the catalogue is built at parent level — all of these leave the event unmatched. And on a purchase event, sending only the first item in a multi-item order quietly hides everything else that was bought.
How to act on it
Test it directly rather than trusting the plugin’s description of itself. Open a product page and a completed order with Events Manager’s test tool or the Pixel Helper, read the identifiers being sent, and compare them character for character with the corresponding rows in your feed.
Confirm the content type matches how the catalogue is structured, since the identifier and the type have to agree. Check that a basket with several items sends all of them, not just one. Then watch the catalogue match rate after any change to your theme, plugins or checkout, because those are the moments identifiers usually break — and a broken match makes even a well-built product set useless.
