Meta Ads

Catalogue Diagnostics

Also called Feed diagnostics, catalogue issues

The error and warning report showing which products cannot be advertised, and why the platform rejected them.

Quick facts: Catalogue Diagnostics

Category
Meta Ads
Also called
Feed diagnostics, catalogue issues
Level
Intermediate
Affects
Product eligibility, retargeting coverage, wasted spend
Where to see it
Commerce Manager, Google Merchant Center, Meta Events Manager
In this article4
  1. How catalogue diagnostics work
  2. Why catalogue diagnostics matter
  3. Common mistakes with catalogue diagnostics
  4. How to act on it

How catalogue diagnostics work

Every time a catalogue refreshes, the platform validates it. Diagnostics is the report of what failed. It works at two levels: problems inside the feed itself, and problems in how the feed lines up with what your website reports through the pixel.

Feed-level issues are things the file gets wrong — a missing required field, an image that cannot be fetched, a price in the wrong currency format, a link that returns an error page. Matching issues are subtler. Your site fires a view or purchase event carrying a product identifier, the platform looks for that identifier in the catalogue, and it is not there or it does not match. Nothing appears broken to a visitor, but dynamic product ads quietly have nothing to retarget with.

Diagnostics usually separate errors, which stop a product being shown at all, from warnings, which allow it but reduce how well it competes.

Why catalogue diagnostics matter

This is the single most common place where money is lost invisibly. The campaign is live, the budget is spending, the reports look normal, and a chunk of the range is simply never eligible to appear. Nothing in the ad account announces that. Only diagnostics does.

It matters most for the products you least expect. New lines, sale items and anything recently edited are the usual casualties, because they are the records most likely to have an incomplete field or a stale image. Those are also the products a business most wants to push.

Common mistakes with catalogue diagnostics

The first is never opening the screen. Diagnostics is not surfaced in day-to-day reporting, so it goes unread for months while the same errors repeat at every refresh.

The second is dismissing warnings. A warning means the product runs with a handicap — weaker matching, a poorer listing, less chance of being selected — which is harder to notice than an outright failure and just as expensive over time.

The third is fixing the symptom in the catalogue when the fault is on the website. If identifiers disagree between your product pages and your feed, editing the feed by hand papers over a mismatch that will return the next time stock changes. The four usual root causes are worth checking in order:

  • The product identifier sent by the pixel does not match the identifier in the feed, often because one uses the variant and the other uses the parent.
  • Images are blocked, too small, or hosted somewhere the platform cannot reach.
  • Required fields such as availability, condition or brand are empty for part of the range.
  • Product links return an error, a redirect chain, or a page that is out of stock.

How to act on it

Check diagnostics on a schedule, not after a problem. Sort by the number of products affected rather than by severity, because one broken rule usually explains most of the list. Fix the source data where the same value also appears on your website, and use feed rules only for genuine platform formatting.

For matching errors, verify the identifier your site sends against the identifier in the feed before touching anything else — that single check resolves most mismatch reports. If your pixel and Conversions API setup is sending inconsistent identifiers, no amount of catalogue editing will hold the fix in place.

Do and do not

Do

  • Check diagnostics on a schedule, not after a problem
  • Sort issues by how many products they affect
  • Compare the identifier your site sends against the feed

Do not

  • Ignore warnings because the products still appear
  • Hand-edit the catalogue to hide a website data fault
  • Skip the check after a migration or stock system change

Questions people ask about this

My catalogue shows warnings but my ads still run. Should I care?

Yes. A warning means the product is allowed to appear but competes with a handicap, usually because a field is missing or an image is poor. That cost is spread thinly across the whole account, so it never shows up as an obvious failure. Clear warnings on your best-selling lines first.

What causes a pixel and catalogue mismatch?

Almost always an identifier disagreement. Your website sends one product ID with the view or purchase event, and the catalogue stores a different one — commonly a variant code on one side and a parent code on the other. Compare what your site actually sends against the feed before editing either, then fix whichever is wrong at its source.

How often should I check catalogue diagnostics?

Make it a routine check rather than a reaction, and always look after a stock system change, a website migration or a large range update. Those three events are when identifiers, links and images break in bulk. A quick look at the affected product count each week is enough to catch problems while they are still small.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.