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.
