Catalog match rate: keep your pixel and catalog in sync
Catalog match rate: keep your pixel and catalog in sync
Catalog match rate tells you how many of your pixel events Meta can link to a product in your catalog. When it's high, catalog ads and retargeting can show people the exact products they viewed or added to cart. When it's low, Meta can't tell which product an event was about, and those ads lose their edge.
The tricky part is that a low match rate is silent. Your pixel still looks healthy, events still arrive in Events Manager, and your catalog still syncs. You only notice when you check the match rate in Commerce Manager.
Why it drops
Most of the time it comes down to one of these:
Your pixel and catalog use different IDs. Your pixel sends either a Variant ID or a Product ID with each event (you set this in Settings > Event settings). Your catalog uses an Item ID based on how you sync variants. If one says Variant ID and the other says Product ID, Meta can't match anything.
Your pixel doesn't track the products in this catalog. If your pixel only tracks some pages (selected or excluded pages), and none of the catalog's products are on those pages, there's nothing to match.
The catalog has no pixel. Without a pixel connected, Meta has no events to match to your catalog.
How Omega checks it for you
When you create or edit a catalog, the Summary on the right shows your catalog match rate status. It updates as soon as you change a setting, so you can fix things before you save.
- Setting matched: your pixel and catalog line up.
- At risk: something doesn't match. The reason is shown right below, so you know what to change.
- Not checked: you haven't picked a pixel for this catalog yet.
You can still save a catalog that's at risk. Omega just makes sure you know before you do.
Feeds aren't checked, because Omega can't see which catalog or pixel you use with a feed link.
Which settings match
How you sync variants | Pixel sends Variant ID | Pixel sends Product ID |
|---|---|---|
Each variant as a separate item | Matches | Doesn't match |
Each product's variants as one group | Matches | Matches |
Only the first variant, Item ID = Variant ID | Matches | Doesn't match |
Only the first variant, Item ID = Product ID | Doesn't match | Matches |
Meta recommends Variant ID, so events match the exact product people view and buy.
How to fix "At risk"
If the IDs don't match, the easiest fix is in the catalog form: change how you sync variants or the Item ID so it matches what your pixel sends. Grouping variants works with both.
You can also change what your pixel sends in Settings > Event settings.
Keep in mind this applies to all your catalogs and feeds, so a catalog that matches today might stop matching. Open your other catalogs afterwards to check them.
If your pixel doesn't track the catalog's products, either add products your pixel tracks to the catalog, or set the pixel to track all pages.
When everything matches but the rate is still low
Omega checks that your setup lines up. Your match rate can still be lower than expected if Meta rejected some products, some events are missing product IDs, or another app or code on your store sends events with IDs in a different format.
If that happens, contact us through the chat with your store domain and catalog name, and we'll take a look.
Updated on: 20/10/2026
Thank you!