Snapchat Catalog Errors: Feed, media & diagnostics fixes

Snapchat's catalog diagnostics use a severity model, explicit media error codes, and a downloadable report. A separate troubleshooting layer matters too: delivery gates can stop Dynamic Ads without turning a feed-diagnostics row red.

This guide covers both layers: every documented error class with its fix, and the invisible gates to check when diagnostics look clean. It's the Snapchat spoke of the product feed errors pillar; the feed spec itself is in Snapchat product feed.

The severity model: errors, warnings, information

Snapchat's Catalog Diagnostics sorts problems into three tiers, and triage follows the tiers:

1. Errors - a required field is missing or invalid; the product doesn't upload. These block revenue; fix them first.

2. Warnings - an optional field is missing or malformed; the product serves anyway, with reduced matching or features. Schedule these; don't firefight them.

3. Information flags - eligibility notes, mostly for app advertisers: products missing app fields (store IDs, deeplink URLs) are flagged ineligible for App Install and Deep Link ad units without being broken for web campaigns.

The downloadable Error Report lists feed errors by product ID - useful for spreadsheet triage, with one crucial caveat covered below.

Required-field errors

Snapchat requires seven fields plus one identifier: id, title, description, link, image_link, availability, price - and at least one of brand, GTIN, or MPN.

The failure patterns:

• Missing required field - the row blocks. Note the identifier rule is one-of-three: an identifier error means all three are absent, or the GTIN you sent is invalid. An empty brand with a valid gtin is fine.

• Price format - 199 USD style; a null price blocks the product.

• ID rules - unique, max 128 characters, and stable: the id is also the retargeting join key, so regenerating IDs between exports silently breaks your audiences even when diagnostics stay green.

• Availability values - five supported (In stock, Out of stock, Preorder, Discontinued, Available for order); out-of-stock products are excluded from ads automatically, which is behavior, not breakage.

Media errors: the codes and the blind spot

First, the blind spot: image failures are not included in the downloadable feed Error Report. A catalog can report zero feed errors while some images fail - the product still builds, and only successfully fetched images serve. Check the media diagnostics surface separately as part of each catalog review.

The documented codes and their fixes:

• AUTH_ERROR - your server or CDN is rejecting Snap's fetcher. Whitelist Snapchat's user agent/IPs; bot-protection rules are the usual culprit.

• REQUEST_TIMED_OUT - the image host is too slow or rate-limiting. Serve catalog images from a real CDN.

• NOT_FOUND - broken URL; the image moved or the URL was mistyped in the feed.

• UNSUPPORTED_MEDIA - outside WebP, JPEG, or PNG. Convert to a supported format.

• CONTENT_TOO_LARGE - over 5 MB. Compress; a 1000-1500px JPEG lands far under the cap.

• SERVER_ERROR - your host errored; if it recurs, it's a hosting problem, not a Snapchat one.

Baseline requirements are gentle - 200 x 200 minimum - but ship the same 1000px+ renders you use everywhere; the creative bar is set by the feed you're competing in, not the floor the platform accepts.

The delivery gates that look like errors

When diagnostics are clean and Dynamic Ads still don't deliver, check these three documented gates early:

1. The 1,000-Snapchatter threshold - Dynamic Ads require your Snap Pixel events to match at least 1,000 Snapchatters. New pixels and low-traffic stores sit below the line; no feed fix changes that - traffic and correct pixel implementation do.

2. item_ids mismatch - pixel events (Page View, View Content, Add to Cart, Purchase) must pass item_ids that exactly match catalog id values. When they don't, retargeting quietly starves. Verify the values, not the events: firing without matching IDs looks healthy everywhere except results.

3. Out-of-stock exclusion - products marked out of stock don't serve; a stale feed that never flips them back keeps them invisible. Sync discipline is the fix - Snapchat supports hourly scheduled fetches.

The Snapchat prevention checklist

1. Validate the seven required fields plus one identifier before upload

2. Keep IDs stable across exports - they're audience keys, not just row keys

3. Serve images as WebP, JPEG, or PNG under 5 MB from a CDN that doesn't block Snap's fetcher

4. Check media diagnostics separately every week - the error report won't warn you

5. Verify pixel item_ids against catalog IDs after any site or app change

6. Use hourly scheduled sync during sales; daily as the floor

7. Gzip large feeds (.zip isn't supported); CSV/TSV/TXT/XML over HTTPS or SFTP

8. For app campaigns, fill the app field set or expect eligibility flags

Separating Snapchat feed checks from delivery gates

Snapchat troubleshooting has the same split as this guide: mechanical catalog checks upstream, delivery gates inside the platform. Flow can validate feed data before export, while its Snapchat workflow supports reusable templates and product variations for the creative side.

Validate the exported files against Snapchat's current field and media limits, then switch tools. Media diagnostics, pixel item_ids, the 1,000-Snapchatter threshold, stock status, account state, and campaign configuration can only be confirmed on Snapchat's side.

FAQ

Final thoughts

Snapchat splits catalog health into two honest halves: a diagnostics system that tells you exactly what's wrong with the data, and a set of delivery gates that tell you nothing at all. Automate the first half, memorize the second - threshold, item_ids, stock status - and "why aren't our Snap ads running" becomes a sixty-second check instead of an afternoon.