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

​
At a glance

The spend running on a catalog campaign whose linked product feed has live rejections. When products are rejected at the feed layer (by a feed-management tool such as Feedonomics, or by Meta’s own catalog review), the catalog Meta bids on is incomplete or stale. The bid signal degrades, the affected products stop serving, and ROAS bleeds until the feed 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.

​
Calculation

Calculated automatically from your Meta Ads (Facebook) data joined to your product-feed 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 US outdoor-gear brand running Advantage+ Catalog campaigns with the catalog fed by a feed-management export. Reading taken on 14 Mar 26 over the trailing 30 days. All figures are illustrative.
  1. The card reads $47,000 of spend exposed to a feed with active rejections across the two campaigns linked to main-export.
  2. Only 6% of items are rejected, but the damage is larger than 6%. Catalog optimisation reallocates budget across the eligible set, so removing 412 items, especially if they include high-velocity products, distorts bidding for the whole campaign, not just the rejected lines.
  3. The bestsellers campaign is clean. It is fed by a separate, smaller export with no rejections, which is why its ROAS held while the main-export campaigns drifted down over the month.
  4. The fix is upstream, not in Ads Manager. Open the feed-management platform, read the rejection reasons (commonly a missing required attribute or a price mismatch against the landing page), correct the source data, and re-export. Confirm the catalog clears in Commerce Manager.
  5. Expect a recovery lag. Once the feed clears and the items re-enter the catalog, Meta 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 = feed degradation. Fix upstream.
  • Rejections on high-velocity SKUs = disproportionate ROAS damage. Prioritise those.
  • Clean feed, separate campaign holding ROAS = isolate the broken feed and fix it without touching the healthy one.

​
Sibling cards merchants should reference together

​
Reconciling against Meta Ads Manager

Where to look in Meta Ads Manager: This is a two-surface reconciliation, because Ads Manager shows the spend and Commerce Manager shows the rejections:
  • Meta Commerce Manager → Catalog → Diagnostics / Items lists rejected items and their rejection reasons. This is Meta’s downstream review.
  • The feed-management platform’s own dashboard (for example Feedonomics) shows upstream rejections caught before the export reaches Meta. Many rejections never appear in Commerce Manager because they were filtered at the source.
  • Meta Ads Manager → Campaigns shows the spend per catalog campaign but does not link it to feed health.
You would have to read rejections from the feed tool and Commerce Manager, then match them to the spending campaigns by hand. This card joins the two automatically. Why the Vortex IQ value may legitimately differ: Cross-connector reconciliation:

​
Known limitations / merchant FAQs

My feed tool shows rejections but Commerce Manager looks clean. Why? Because many rejections are caught upstream in the feed-management platform and never reach Meta. Those items are simply excluded from the export, so Commerce Manager has nothing to flag, yet the campaign is still serving a reduced product set. Checking Meta 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. Catalog 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. What are the most common rejection causes? Missing or invalid required product attributes, price or availability mismatches between the feed and the landing page, disallowed or restricted content, and product-level policy flags. The 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 catalog, Meta has to relearn and redistribute budget across the restored set. Expect a recovery window of days, not an instant rebound, and read ROAS Trend over the following week rather than the same day. Does this apply to manual (non-catalog) campaigns? No. The card is specific to catalog-driven campaigns (Advantage+ Catalog and DPA) that depend on the product feed. A manual broad-audience campaign with no catalog link is not exposed to feed rejections and will not appear here. Whose rejection list is authoritative? Both matter. The feed-management platform catches issues before export; Commerce Manager catches issues at Meta’s review. A complete picture needs both, which is why this card joins the feed connector and the Meta 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 Meta Ads (Facebook) 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.