Skip to main content
Metrics type: Key Metrics • Category: Cross-Platform: Revenue at Risk

​
At a glance

A cross-platform revenue-at-risk card that sums the LinkedIn spend running on any campaign whose linked product feed currently has live rejections. When a feed-management layer such as Feedonomics pushes a product catalogue into a paid channel and some items are rejected (missing attributes, policy issues, bad image URLs, currency or pricing mismatches), the campaigns promoting those rejected products keep spending while the products themselves are degraded or undeliverable. The card joins LinkedIn campaign spend to the feed-rejection status from the connected feed source, and surfaces the total money exposed to active rejections. It needs both a LinkedIn campaign with a linked product feed and a connected feed-management source; it stays quiet when there are no live rejections to worry about.

​
Calculation

Calculated automatically from your LinkedIn Ads data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

A B2B equipment manufacturer that sells through a product catalogue and runs LinkedIn product campaigns to procurement and engineering audiences. Account currency GBP. Its catalogue flows through Feedonomics into multiple channels including LinkedIn. A supplier data update strips the GTIN and a required spec attribute from a range of products, and Feedonomics starts rejecting them. The card evaluates a 30-day window. Two campaigns are linked to feeds with active rejections. The card reports roughly £6,300 of 30-day LinkedIn spend exposed to feed rejections. It fires, escalating because the exposed spend is material.
  1. The spend is buying a half-broken catalogue. On the valves campaign, 34 of 90 products are rejected, so a large slice of what the campaign promotes is degraded or undeliverable. The £4,200 is paying to promote a catalogue with a hole in it; clicks land on missing or downgraded products.
  2. The fix is upstream in the feed, not in LinkedIn. Re-add the stripped GTIN and spec attributes at source, let Feedonomics reprocess, and the rejected items return to delivery. Pausing the LinkedIn campaign is a stopgap; fixing the feed restores the full catalogue the campaign already paid to advertise.
  3. Rejections often cascade from one upstream change. A single supplier data update stripped attributes across a whole range, which is why two campaigns lit up at once. When several campaigns trip together, look for one common upstream cause rather than fixing each item by hand.
  4. This is a cross-connector card and stays quiet when healthy. It needs both a LinkedIn campaign with a linked product feed and a connected feed-management source. With no active rejections, there is nothing to flag and the card sits at zero. Seeing a non-zero reading means real money is exposed right now.
Quick triage when this card fires:
  • Rejections concentrated in one range = a single upstream data change; fix at source and reprocess.
  • Rejections scattered across many feeds = a broader feed-config or sync problem; check the feed-management layer’s health.
  • High exposed spend + many rejected items = pause the worst campaigns as a stopgap while the feed is repaired.
  • Card fires but rejections are stale = confirm the feed has actually resynced; a fixed feed may not have pushed yet.

​
Sibling cards merchants should reference together

This card sits at the join of LinkedIn spend and feed health, so pair it across both:

​
Reconciling against LinkedIn Campaign Manager

Where to look in LinkedIn Campaign Manager: LinkedIn Campaign Manager → Campaigns shows campaign spend, but it does not show your feed-management rejections, which live in the feed layer. To reconcile, confirm the spend side in Campaign Manager for the flagged campaigns over the same 30-day window, then check the rejection counts in your feed-management dashboard (for example Feedonomics) or your commerce platform’s feed-health view. The card multiplies the two: spend on campaigns whose linked feed has live rejections. Neither system shows the joined figure alone. Things to confirm during reconciliation:
  • Feed-to-campaign linkage. Verify which feed each campaign is linked to, so the spend attributes to the right rejection status.
  • Rejection recency. Feed dashboards can show historical rejections that are already resolved; the card reads the current sync, so confirm the rejections are still live.
  • Whole-campaign exposure. The card counts the campaign’s full spend, not just spend on the rejected items, because a degraded feed undermines the whole campaign. That is intentional, and may read higher than an item-level count.
Why our number may legitimately differ from LinkedIn: Cross-connector reconciliation: This card is a join by design, so reconciliation spans LinkedIn and the feed layer:

​
Known limitations / merchant FAQs

Why count the whole campaign’s spend, not just the rejected items? Because a feed with rejections degrades the whole campaign, not only the rejected lines. Delivery optimisation, budget pacing, and the prospect’s experience all suffer when part of the promoted catalogue is broken. Counting whole-campaign spend reflects the true money at risk, even if it reads higher than an item-by-item tally. The feed dashboard shows rejections but the card is quiet. Why? Most likely the rejections are historical and already resolved, while the card reads the current feed sync. Confirm the rejections are live in the latest sync. The reverse can also happen: a fix you just made may not have resynced yet, so the card still shows the old rejections briefly. Should I pause the campaign or fix the feed? Fix the feed. Pausing is a stopgap that stops the bleeding but throws away the campaign’s momentum. The rejections are almost always an upstream data problem (missing attributes, broken URLs, policy issues) that, once fixed at source and reprocessed, restores the full catalogue the campaign already paid to promote. Many campaigns lit up at once. Is that normal? It usually means one upstream change cascaded: a supplier data update, a catalogue migration, or a feed-config change that stripped a required attribute across a whole range. Look for the single common cause rather than fixing items one at a time. The card is not showing for my account. Why? It needs both a LinkedIn campaign with a linked product feed and a connected feed-management source. Pure lead-gen LinkedIn accounts with no product feed will not see it. If you run product campaigns and expect the card, confirm the feed source is connected and the campaign is feed-linked. Does this overlap with the out-of-stock card? They are complementary. The out-of-stock card flags products that are unbuyable due to inventory; this card flags products that are rejected due to feed data quality. A product can be in stock but rejected, or rejected but in stock. Read both for full catalogue-integrity coverage.

​
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 LinkedIn 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.