Conversion Tracking
Part of Paid social product catalogue campaigns
Troubleshooting mismatched product events
Trace product IDs from site events to catalogue items, separate missing IDs from unmatched IDs and confirm the repair.
Trace one product ID from the store page through the event to the imported catalogue item. First distinguish an event with no product ID from one that sent an ID the catalogue does not contain; each fault has a different cause. On Meta, inspect the event’s content_ids field.
Find where the match fails
Choose a permitted sample item and record its sellable variant ID, catalogue item ID and the event source connected to that catalogue. In Meta Events Manager, use Test Events to inspect a product view and cart action; for a cart containing several products, inspect each item’s content_ids. Compare event IDs with imported catalogue IDs: they must match exactly.
In Meta Commerce Manager, select your catalogue and open Events/Diagnostics. Look for the percentage of events that match, then compare individual IDs: the percentage alone may not show which item or issue is responsible.
Use Test Events to distinguish an event with no product ID from one with an ID that does not appear in the catalogue. Treat these as separate issues and check the event ID against the imported item ID.
For example, Shoporama’s variant scheme uses 154585:45789 for product ID 154585 and variant ID 45789. If the event sends 154585 but the variant’s feed ID (g:id) is 154585:45789, they do not match; sending 154585:45789 matches that item.
| Finding | Next check |
|---|---|
| Event absent | Whether the intended source sent the event and is connected to the catalogue |
| Event present, ID absent | The page or integration constructing product parameters |
| ID present, no item matched | ID format, imported item, variant level and connected catalogue |
| Some items match | Recently added items, regional catalogues and inconsistent variant IDs |
Check the product level and catalogue
A parent product and a sellable variant can have different IDs. Determine which one the event represents and keep that choice consistent with the catalogue and destination. Do not switch to a parent ID solely to improve a metric if the ad needs the selected variant.
An item may be absent because its import has not succeeded. Check the product source and the catalogue measured in Events/Diagnostics. In Meta Commerce Manager, select the intended catalogue; if you use Shoporama, its built-in Google Shopping feed can be uploaded there. Confirm the intended catalogue and market before changing the setup.
Record which event source is connected to the catalogue you are checking. Compare its event IDs with the items in that same catalogue, rather than a different catalogue or feed.
Catalogue match rate diagnostics
- Match Rate
- View in Meta Commerce Manager → Events/Diagnostics
- Feed Source
- Shoporama Google Shopping feed (if applicable)
- Event ID Match
- Must exactly match imported catalogue item ID
Confirm the repair
Repeat the same permitted product journey after a mapping change. In Meta Events Manager Test Events, check that the event contains the intended content_ids value and that the ID exists in the connected catalogue.
Review Events/Diagnostics after the platform has processed the events. Check a second variant and a cart with several items so the repair covers more than one example. Keep diagnostic records without customer details.
This procedure addresses product-to-catalogue matching, not purchase-event deduplication or whether attributed sales equal store orders.
