At a glance
A cross-channel 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.
| What it tracks | Total LinkedIn spend, over the window, on campaigns whose linked product feed currently shows one or more active item rejections. |
| Reporting source | LinkedIn Marketing Reporting API for campaign spend, joined to the feed-rejection status from the connected feed-management source (for example Feedonomics) or the commerce catalogue’s feed health. |
| What “feed rejection” means | A product in the feed that the destination has refused or downgraded: missing required attributes, disapproved on policy, broken image or landing URL, price or currency mismatch, or other data-quality failures reported by the feed layer. |
| What “spend on the campaign” means | The media cost accrued by a campaign linked to a feed that has active rejections, regardless of whether the spend went to rejected or still-approved items, because a degraded feed undermines the whole campaign’s delivery. |
| Why it matters | LinkedIn spend is premium. Money flowing through a campaign whose products are being rejected is buying degraded delivery at best and undeliverable products at worst. Fixing the feed restores the full catalogue the campaign paid to promote. |
| Currency | Account currency for the spend-at-risk total. |
| Time window | 30-day window for the spend total, with rejection status read against the latest feed sync. |
| Alert trigger | Fires when any spend lands on a campaign whose linked feed has active rejections. The card escalates with the size of the exposed spend. |
| Roles | owner, marketing, operations |
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.| Campaign | Linked feed | Items rejected | Spend (30D) | Exposed |
|---|---|---|---|---|
| Industrial pumps, engineering audience | Pumps feed | 0 | £6,800 | OK |
| Valves range, procurement audience | Valves feed | 34 of 90 | £4,200 | At risk |
| Sensors range, ops audience | Sensors feed | 12 of 60 | £2,100 | At risk |
- 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.
- 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.
- 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.
- 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.
- 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:| Card | Why pair it with this card | What the combination tells you |
|---|---|---|
| Active Campaigns on Out-of-Stock SKUs | The other catalogue-integrity revenue-at-risk card. | Together they cover both ways a product campaign can spend on something unsellable: out of stock, or feed-rejected. |
| Spend by Campaign | Allocates the exposed spend to specific campaigns. | Prioritise which feed to fix by how much spend sits behind it. |
| Wasted Spend | Feed-rejection spend is avoidable degraded spend. | Sizes the recoverable portion of the wasted-spend baseline. |
| Conversion Rate by Campaign | A campaign with rejected products converts worse. | Confirms the rejections are hurting outcomes, not just delivery cosmetics. |
| Landing Pages with Poor Web Vitals | Another destination-quality check for paid clicks. | A rejected product and a slow page are two ways the click lands badly. |
| Shopify / BigCommerce / Adobe Total Revenue | The commerce side, where the lost product sales would land. | Connects feed health to the storefront revenue the campaign should drive. |
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.
| Reason | Direction | Why |
|---|---|---|
| Whole-campaign attribution | Card reads higher than item-level | The card counts the full campaign spend, not only the rejected items’ share, because rejections degrade overall delivery. |
| Feed sync timing | Card may lag a fix | A just-repaired feed may still show rejections until the next sync; the flag clears on resync. |
| Stale dashboard rejections | Feed dashboard may overstate | Feed tools can list resolved historical rejections; the card uses current status. |
| Time zone | Boundary days off | Spend windows and feed snapshots align, but raw exports can look offset. |
| No feed connector | Card hidden or zero | Without a connected feed source and a feed-linked campaign, there is nothing to flag. |
| Source | Expected relationship | What causes legitimate divergence |
|---|---|---|
| Feed-management dashboard (Feedonomics or similar) | The rejection counts that drive the flag | Historical versus live rejections, and per-channel rejection rules, change what counts. |
| Commerce catalogue feed health (Shopify / BigCommerce / Adobe) | The upstream source of feed data | Attribute requirements differ per destination channel. |
| Spend by Campaign | The spend behind each flagged campaign | Account spend includes non-feed campaigns this card ignores. |