Articles on: Omega Google & Facebook Feed

Fix Meta catalog errors

This page covers the Meta catalog problems merchants ask us about most. You see them on a Facebook feed's page in Omega Feed: in the Approval status card and the Catalog match rate card.


Product not in Facebook catalog


Error code: MISSING_IN_CATALOG. Shown as "Product not in Facebook catalog" in Approval status.


Why it happens: Omega Feed sent the product to Meta, but it isn't in the catalog when we check. Meta processes new products in stages, so this is usually a delay. Less often, the product was deleted or archived in the catalog, or the feed now points to a different catalog.


Omega Feed checks the catalog 20 to 60 minutes after a sync, depending on catalog size. It checks up to 3 more times before it reports a product as missing, so it can take about 2 hours before you see this error.


Fix it in Omega Feed


  1. Open the feed and click Re-sync.
  2. Wait about 30 minutes. Check Approval status again.
  3. Still missing? Click Open in Commerce Manager on the feed's issues, or search for the product in Commerce Manager > Catalog > Items.
  4. Check the feed still uses the right catalog. Send your feed to a Meta catalog.


Fix it in Shopify


Make sure the product is Active and published to the sales channel your feed uses. A draft or archived product is not sent.


Low catalog match rate


Why it happens: your Meta pixel and your feed describe the same product with different IDs. When a shopper views a product, the pixel sends a Content ID. Meta compares it, character for character, with the Content ID your feed sends. When the two differ, Meta can't link the visit to a product, and dynamic ads and retargeting lose it.


Omega Feed sends the Shopify Variant ID as the Content ID by default, for example 42647978475616. Pixels added by a theme, a tracking app or an agency often send another format, such as the Product ID, the SKU or shopify_US_8123456789_42647978475616.


Check your match rate


  1. Go to Feeds and open your Facebook feed.
  2. Read the Catalog match rate card. It lists every pixel connected to the catalog with its rate for the last 28 days. Meta can take up to 48 hours to update it.
  3. Read the badge:
  • Green (90% and above) — the pixel and the feed agree. Nothing to fix.
  • Yellow (75–89%) or red (below 75%) — some events don't match. Read the next step before changing anything.
  • Not enough data — the pixel hasn't sent product events yet. On a new feed, allow 48–72 hours plus new store visits.

Catalog match rate card with one pixel, its status badge and How to improve


If the card shows Grant access or Reconnect, reconnect your Meta account to see the rates. No pixel listed? Click Add pixels to connect one in Commerce Manager.


Your match rate

Likely cause

What to do

0%

The pixel and the feed use different ID formats

Compare the IDs and fix the mapping (below)

Low, above 0%

The format is right; the feed or its products are new

Don't change the mapping. Wait a few days and check again


Compare the two IDs


  1. On the Catalog match rate card, click How to improve. It shows the Content ID format your feed sends and an example.
  2. Open a product page on your store. In Meta Events Manager, go to your pixel > Test events and look at content_ids on the ViewContent event.
  3. Compare the two values. If they are identical, the feed is not the cause; see "My rate is still low" below.


Fix it in Omega Feed


  1. Open the feed's Settings tab.
  2. In Product info, set Content ID to the option that matches your pixel:
  • Variant ID (recommended) — the pixel sends 42647978475616.
  • SKU — the pixel sends ABC-RED-M. Use it only when every variant has its own SKU.
  • shopify_{{country}}{{product ID}}{{variant ID}} — the pixel sends shopify_US_8123456789_42647978475616.
  • shopify_ZZ_{{product ID}}_{{variant ID}} — the pixel sends shopify_ZZ_8123456789_42647978475616.
  1. Save and click Re-sync.

Facebook feed Settings, Product info section with the Content ID dropdown


Pixel sends another format? Choose Custom and build the ID from variables (Pro plan or higher). Map attributes.


Changing the ID makes the channel treat every product as a new one. Products go through review again and lose their history. Change it once, when you are sure of the format.


My rate is still low


  • The rate counts the last 28 days, so it rises only as new events arrive after your fix. Give Meta a few days.
  • Products excluded from the feed or rejected by Meta can't match. Fix those in Find and fix product issues.
  • Two feeds send to the same catalog? Fix the Content ID in both.




Need help? Chat with us from the app.

Updated on: 13/11/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!