Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Meta Ads › Troubleshooting

Meta Catalog Products Not Showing in Ads

Why catalog products do not appear in Meta ads: item rejections, feed errors, product sets filtering them out, pixel and catalog ID mismatch, and stock.
Troubleshootingintermediate6 min readUpdated

First, confirm which items are missing

Start with a list rather than an impression. Pick a handful of items you expected to see and look up each one in Commerce Manager: its status, any errors or warnings, its availability and price, and when it was last updated. Then open the product set the ad set uses and check whether those items appear in its preview. Finally, read the ad's breakdown by product in Ads Manager over a period long enough to cover normal delivery, which shows which items actually served.

Three patterns emerge. Items that are rejected or erroring point at diagnostics. Items that are healthy but absent from the set preview point at set rules. Items that are healthy and in the set but never serve, especially in retargeting, point at event matching or stock. The creative and set strategy behind catalog ads is covered in the catalog ads guide; here the job is only to find where each item drops out.

Diagnosis table

Diagnosis

SymptomCheckLikely causeFix
Items show errors or a rejected status in Commerce ManagerDiagnostics tab, item-level issuesItems rejected or with errors in catalog diagnosticsCorrect the field, image, link or policy issue at the feed source
Healthy items absent from the product set previewSet filter rules against the items' attributesProduct set rules excluding the itemsEdit the rule or the attribute the rule reads
Retargeting shows bestsellers instead of viewed itemsEvent matching report in the catalog; content IDs in pixel eventsPixel content IDs not matching catalog item IDsSend the catalog's item ID as the content ID
Items vanish when stock runs low or after a price changeAvailability and price in the catalog against the landing pageOut-of-stock or price-mismatched items suppressedKeep availability and price in sync with the site
Catalog details lag days behind the shopData source schedule and last fetch resultFeed fetch failing or not refreshedRepair the fetch and set a schedule that matches the shop

Fix, verify and prevent each cause

Rejected or erroring items

The diagnostics tab lists missing required fields, wrongly formatted values, images that fail the size or content rules, broken links, and items rejected under policy. An item in any of those states may not be eligible for delivery.

Fix: correct the problem at the feed source, not by editing the item in Commerce Manager, which the next fetch will overwrite.

Verify: after the next update the item's issue clears and its status changes.

Prevent: read diagnostics after every feed change and on a schedule; the feed quality section of the catalog ads guide lists the fields that matter.

Product set rules that leave items out

A product set is a saved filter. A rule on a custom label that the feed stopped filling, a price band set before a sale, or a category value that changed in the shop's taxonomy can silently drop healthy items.

Fix: change the rule, or restore the attribute the rule reads.

Verify: the set preview lists the items and the product breakdown shows them receiving impressions.

Prevent: document which feed field each set depends on and review sets whenever the feed's structure changes, as the product set section of the catalog ads guide advises.

Content IDs that do not match catalog IDs

Dynamic Remarketing works by matching the content IDs in view, add-to-cart and purchase events to item IDs in the catalog. If the pixel sends the parent product ID while the catalog lists variant SKUs, or the reverse, nothing matches and the system cannot show people what they viewed.

Fix: send the exact catalog item ID as the content ID on every product event, from the data layer.

Verify: the catalog's event matching report shows a high share of matched events, and Test Events shows content IDs that exist in the catalog.

Prevent: define the ID rule once and apply it to both the feed and the tags, following the product event steps in the Meta Pixel setup tutorial. If events are missing entirely, the pixel events not showing page comes first.

Out of stock or mispriced

Items marked out of stock are not promoted, and an item whose catalog price differs from the landing page can be flagged, because an ad showing the wrong price wastes the click and can breach Meta's advertising standards.

Fix: make availability and price come from the same source the site uses, including sale prices.

Verify: availability and price in Commerce Manager match the product page for a sample of items.

Prevent: use a scheduled fetch or platform connection rather than manual uploads, as the catalog ads guide recommends for keeping details current.

A feed that stopped refreshing

A changed feed URL, an expired password on a hosted file, or a platform update that renamed a field can make scheduled fetches fail. The catalog then keeps old data while the shop moves on, and new products never arrive.

Fix: open the data source, read the last fetch result, repair the URL or field mapping, and run a manual fetch.

Verify: the last update time is recent and new products appear in the catalog.

Prevent: set the schedule to match how often the shop changes and check fetch results weekly; the commerce hub describes the catalog as the shared source for every commerce surface, which is why a stale feed affects them all.

Prevention: catalog diagnostics on a schedule

Catalog problems are quiet: nothing in Ads Manager warns that a quarter of the range has stopped serving. The defence is a schedule. Each week, open the diagnostics tab, note the number of items with errors and the top issue, and read the last fetch result for each data source. Each month, compare the product breakdown in Ads Manager with the catalog, looking for categories that never serve, and check the event matching report for retargeting. After any change to the shop platform, theme or feed tool, run all three checks the same day, because a renamed field or a new ID format breaks things on the day it ships.

Keep a short record of the fields each product set depends on, and of the ID rule shared by the feed and the tags. Give one person ownership of the catalog, with a named contact on the development side. A new or reconnected catalog can be checked against the Meta catalog setup checklist before its first campaign, which catches most of these causes at the start. Where server events carry product data through the Conversions API, include them in the ID rule too, so browser and server events agree. Judge product sets on return on ad spend (ROAS) only after confirming the items in them are actually serving.

Illustrative example — not a real result

A fashion retailer whose new season never appeared

A fashion retailer launches 240 new-season items. Two weeks later the catalog retargeting ads still show last season's coats. Commerce Manager shows the new items as active with no errors, but the product set used by the ad set filters on custom label 0 equal to "core", and the new items were loaded with that label empty. The event matching report also shows only 52% of view events matched, because the new theme sends the parent style code as the content ID while the catalog lists colour variants. The team fills the label in the feed, changes the data layer to expose the variant ID, and runs a manual fetch. Within a week the product breakdown shows 205 of the new items serving and matched events above 90%.

Common mistakes

Editing items by hand in Commerce Manager when the feed will overwrite them. Assuming an active item is an eligible one. Building product sets on labels that nobody maintains. Sending parent IDs from the pixel and variant IDs in the feed. Treating stale prices as a creative problem.

Frequently asked questions

Why does a product appear in the catalog but never in my ads?

Being in the catalog does not make an item eligible. It may be rejected or carry an error in the diagnostics tab, fall outside the product set the ad set uses, be marked out of stock, or never be matched to visitor behaviour because the pixel sends a different content ID. Check the item's status, then the product set preview, then the event matching report, in that order.

Do catalog ads need the pixel?

Prospecting with the catalog can run on the catalog alone, but dynamic retargeting depends on pixel or app events that carry content IDs matching catalog item IDs. Without that match the system cannot show people the items they viewed, and it falls back to whatever it can predict, often a few bestsellers.

How quickly do feed changes reach the ads?

That depends on how the catalog is supplied. A scheduled fetch updates on its schedule, a platform connection syncs on its own cycle, and a manual upload changes nothing until the next upload. If prices or stock change faster than the catalog refreshes, items can be suppressed or shown with stale details, so align the refresh with how often the shop changes.

Terms used on this page

Where this page is used

Also related

Sources

  1. Meta Business Help Centre — Meta Business Help Centre
  2. About the Meta Pixel — Meta Business Help Centre

Related