Skip to main content
Metrics type: Cross-Platform Metrics • Category: Ad Platform

​
At a glance

The spend running on a Snapchat Dynamic Ads campaign whose linked product catalogue has live rejections. When products are rejected at the feed layer (by a feed-management tool, or by Snapchat’s own catalogue review in Business Manager), the catalogue Snapchat bids on is incomplete or stale. The bid signal degrades, the affected products stop serving in the Dynamic Ads carousel, and ROAS bleeds until the catalogue clears. This card names the spend that is exposed to that degraded feed so you can fix the rejection rather than keep paying for a campaign that cannot show its best products. Caveat: a rejection does not always zero out a campaign; partial rejections quietly shrink the eligible product set, so the damage is often a slow ROAS erosion rather than a hard stop, and on Snapchat that erosion is easy to miss because the swipe-up rate can look healthy even as conversions slide.

​
Calculation

Calculated automatically from your Snapchat Ads data joined to your product-catalogue health. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

A UK streetwear brand, Dune & Drift, running Snapchat Dynamic Ads to a Gen-Z audience with the catalogue synced from its Shopify store feed. Reading taken on 14 Apr 26 over the trailing 30 days. All figures are illustrative.
  1. The card reads GBP 29,300 of spend exposed to a catalogue with active rejections across the two campaigns linked to main-catalogue.
  2. Only 6% of items are rejected, but the damage is larger than 6%. Dynamic Ads optimisation reallocates budget across the eligible set, so removing 318 items, especially if they include high-velocity products, distorts bidding for the whole campaign, not just the rejected lines. On Snapchat the carousel simply skips the missing SKUs, so swipe-up rate can stay flat while conversions quietly fall.
  3. The new-drop Collection campaign is clean. It is fed by a separate, smaller catalogue with no rejections, which is why its ROAS held while the main-catalogue campaigns drifted down over the month.
  4. The fix is upstream, not in Ads Manager. Open the catalogue source (the feed-management tool, or the Shopify catalogue sync), read the rejection reasons (commonly a missing required attribute, a prohibited-category flag, or a price mismatch against the landing page), correct the source data, and re-sync. Confirm the catalogue clears in Business Manager catalogue review.
  5. Expect a recovery lag. Once the catalogue clears and the items re-enter the active set, Snapchat needs time to relearn and redistribute budget. ROAS does not snap back instantly; budget the following week for recovery, not the same day.
Quick reads:
  • Rejections rising + ROAS drifting down on the same campaign = catalogue degradation. Fix upstream.
  • Rejections on high-velocity SKUs = disproportionate ROAS damage. Prioritise those.
  • Clean catalogue, separate campaign holding ROAS = isolate the broken catalogue and fix it without touching the healthy one.
  • Swipe-up rate steady but conversions falling = classic signature of a catalogue that is serving fewer products than it should.

​
Sibling cards merchants should reference together

​
Reconciling against Snapchat Ads Manager

Where to look in Snapchat Ads Manager: This is a two-surface reconciliation, because Ads Manager shows the spend and the catalogue view shows the rejections:
  • Snapchat Business Manager (business.snapchat.com) > Catalogues > your catalogue > Products lists rejected items and their rejection reasons. This is Snapchat’s downstream review.
  • The feed-management platform’s own dashboard, or the Shopify catalogue sync log, shows upstream rejections caught before the export reaches Snapchat. Many rejections never appear in the Snapchat catalogue because they were filtered at the source.
  • Snapchat Ads Manager (ads.snapchat.com) > Campaigns shows the spend per Dynamic Ads campaign but does not link it to catalogue health.
You would have to read rejections from the catalogue view and the feed tool, then match them to the spending campaigns by hand. This card joins the two automatically. Why our number may legitimately differ from Snapchat: Cross-connector reconciliation:

​
Known limitations / merchant FAQs

My feed tool shows rejections but Snapchat’s catalogue looks clean. Why? Because many rejections are caught upstream in the feed-management platform (or the Shopify catalogue sync) and never reach Snapchat. Those items are simply excluded from the export, so the catalogue has nothing to flag, yet the campaign is still serving a reduced product set. Checking Snapchat alone undercounts; this card considers the upstream layer where the feed connector is linked. A small percentage of items is rejected. Is it really worth fixing? Usually yes. Dynamic Ads optimisation spreads budget across the eligible set, so removing even a few high-velocity products skews bidding for the whole campaign. A low rejection count can cause an outsized ROAS drop, which is why the card is loud on any active rejection rather than waiting for a large count. It is especially worth checking on Snapchat, where swipe-up rate can stay healthy and hide the loss. What are the most common rejection causes on Snapchat? Missing or invalid required product attributes, broken or low-resolution image URLs, prohibited or restricted categories (Snapchat is strict on alcohol, weight loss, regulated and age-gated goods), price or availability mismatches between the feed and the landing page, and product-level policy flags. The catalogue review or feed tool’s rejection reason usually names the exact field to fix. I fixed the feed. Why is ROAS still down? Recovery lags the fix. Once the items re-enter the catalogue, Snapchat has to relearn and redistribute budget across the restored set. Expect a recovery window of days, not an instant rebound, and read ROAS Dropped Below Threshold and the conversions trend over the following week rather than the same day. Does this apply to non-catalogue campaigns (Single Image, Story, Spotlight, AR Lens)? No. The card is specific to catalogue-driven campaigns (Dynamic Ads and catalogue-fed Collection Ads) that depend on the product feed. A Single Image, Story, Spotlight or AR Lens campaign with no catalogue link is not exposed to feed rejections and will not appear here. My swipe-up rate is fine, so why does the card say my catalogue is degraded? Swipe-up rate measures interest in the creative, not the completeness of the catalogue behind it. A campaign can keep earning swipe-ups while quietly serving fewer products, so buyers land on a thinner selection and convert less. That is exactly the pattern this card is built to catch: steady swipe-up rate, falling conversions, live rejections on the linked catalogue. Whose rejection list is authoritative? Both matter. The feed-management platform (or Shopify sync) catches issues before export; Snapchat’s catalogue review in Business Manager catches issues at Snapchat’s end. A complete picture needs both, which is why this card joins the feed connector and the Snapchat connector rather than relying on one.

​
Tracked live in Vortex IQ Nerve Centre

Spend on Campaigns with Active Feed Rejections is one of hundreds of KPI pulses Vortex IQ tracks across Snapchat Ads and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.