Meta Catalog Data Quality: An Identity and Availability Diagnostic

For the surrounding account decisions, compare Meta Ads Founder Operations: A Sustainable Review Cadence and use Meta Ads Lookalikes: A Source-Quality Decision as the next diagnostic.

In short

This guide owns one decision artifact: the filled, auditable structure below. Reader-supplied thresholds stay explicit; missing evidence stays missing.

Catalog-field diagnostic

Field	Expected	Common mismatch	Check	Advertising impact
id	One immutable catalog ID per sellable variant, matching event content_ids	Parent SKU in events, variant SKU in feed	Join a sample of view, cart, and purchase IDs to the current feed	Unjoined items cannot support reliable item-level delivery or reporting
availability	Feed state agrees with the commerce inventory snapshot	Feed says in stock after inventory reaches zero	Compare feed generation time, ingestion time, and stock ledger	Ads may reference an unavailable variant
price	Currency and amount match the destination at extraction time	Sale price expired or decimal/currency differs	Parse feed amount and crawl the matching destination	Price inconsistency breaks offer continuity
gtin	Valid product identifier where one genuinely exists	Placeholder, reused, or parent-level identifier	Validate format and uniqueness against product master	Identity quality and downstream matching can be impaired; do not invent a GTIN
image_link	Reachable image for the exact variant and current product	Blocked URL, obsolete asset, wrong color	Fetch with a clean request and compare variant mapping	Creative can be unavailable or visually inconsistent
title	Accurate product/variant title without unsupported claims	Truncation hides variant or title carries stale promotion	Diff product master, feed, and destination	Relevance and claim continuity become harder to audit

Item identity coverage = (sellable variants whose commerce ID joins exactly one catalog ID) ÷ (sellable variants eligible for advertising). Source/window: product master and latest accepted feed snapshot. Limitation: an ID join does not validate price, stock, or claims.

Interpretation boundary

Use the catalog field identity check only for its stated decision. Join variant IDs first, then independently validate availability, price, GTIN, image, and title against one timestamped product snapshot. A successful ID join does not clear stale inventory, wrong price, unsupported title claims, or a mismatched variant image. Reader-supplied thresholds remain inputs, not universal standards.

Can software help?

Bach.ai audits your connected Meta account against 100+ checks, ranks what it finds by estimated impact, and proposes specific fixes. It stays read-only until you approve a change, then executes the approved change on Meta; connected Google Ads data is used for intelligence only. Think of it as an automated audit layer that surfaces issues and proposed fixes for your review — not a replacement for your team’s judgment, and it does not generate your creative.

FAQ

How do you validate identity and product fields in a Meta catalog?

Join variant IDs first, then independently validate availability, price, GTIN, image, and title against one timestamped product snapshot.

Does a correct catalog ID match clear every data-quality issue?

A successful ID join does not clear stale inventory, wrong price, unsupported title claims, or a mismatched variant image.

What does a catalog diagnostic reveal without proving the cause of performance changes?

It isolates competing explanations through the catalog field identity check. The resulting branch is a diagnostic decision, not proof that one candidate caused the observed change.