At a glance
The highest-stakes catalogue-health card on Pinterest. Your Verified Merchant status depends on a healthy product feed; when the rejection rate climbs past Pinterest’s quality threshold, that status is at risk, and losing it removes your Shopping Pin distribution and the trust badges that drive conversion. This card watches the rejection rate on the Pinterest product feed (often managed through a feed tool such as Feedonomics) and flags when rejections threaten Verified Merchant status, before Pinterest pulls your Shopping distribution. It joins feed health to the spend riding on those Shopping Pins so you can see exactly what revenue is exposed.
| What it watches | The share of products in your Pinterest catalogue feed that Pinterest rejects, weighted against the spend and revenue flowing through Shopping Pins that depend on a healthy feed and Verified Merchant status. |
| Why it is cross-channel | Feed health lives in your feed-management layer (Feedonomics or equivalent) and your commerce platform; the Shopping distribution and Verified Merchant status live on Pinterest. The card joins the two so a feed problem is read in terms of the Pinterest revenue it endangers. |
| Why Verified Merchant matters | Verified Merchant status grants Shopping Pin distribution, product tagging, and trust signals that materially lift conversion. Losing it is not a soft penalty: it removes the surface your Shopping campaigns depend on. The threshold for keeping it is a low rejection rate, so feed quality is not optional. |
| Why rejections happen | Missing required attributes, broken image or destination URLs, price or availability mismatches between the feed and the landing page, disallowed product categories, or formatting errors introduced by a feed-rule change. A single bad feed rule can reject thousands of products at once. |
| Why Pinterest is high-stakes | On Pinterest Shopping the feed IS the catalogue of shoppable Pins. A feed problem does not just lower quality scores as it might elsewhere; it can revoke the merchant standing that lets you run Shopping at all. |
| The feed-tool angle | Most merchants pipe products to Pinterest through Feedonomics or a similar tool. A transformation rule that works for Google Shopping can violate Pinterest’s stricter requirements, so the same source catalogue can pass on Google and fail on Pinterest. This card is the Pinterest-specific safety net. |
| Unit | Currency for the exposed revenue and spend, alongside the rejection-rate percentage that drives the trigger. |
| Time window | 30D (30-day window to capture feed-quality trend, not just a single sync). |
| Alert trigger | Pinterest feed rejection rate exceeding roughly 5%, the level at which Verified Merchant status is at risk. |
| Sentiment key | pin_xc_feed_rejection_vs_spend |
| Roles | owner, marketing, operations |
Calculation
Calculated automatically from your Pinterest catalogue feed health joined to the Pinterest Ads spend and revenue riding on Shopping Pins. 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 home decor brand piping a Shopify catalogue to Pinterest via Feedonomics. Account currency: GBP. The 30-day window covers 02 May 26 to 31 May 26.| Feed metric | Value | Status |
|---|---|---|
| Products submitted | 3,400 | - |
| Products rejected | 244 | - |
| Rejection rate | 7.2% | Above threshold, VMP at risk |
| Shopping spend riding on feed (30D) | £14,800 | Exposed |
| Shopping revenue riding on feed (30D) | £92,000 | Exposed |
| Top rejection reason | Image URL returns 404 | Fixable |
- The rejection rate is 7.2%, above the threshold. Verified Merchant status is now at risk. If Pinterest revokes it, the £14,800 of Shopping spend stops producing distribution and the £92,000 of Shopping revenue is in jeopardy. That exposure is why this is the highest-stakes feed card on Pinterest.
- The cause is concrete and fixable. 244 products were rejected because their image URLs return 404. That points to a feed-rule or hosting change, likely a Feedonomics transformation that built a broken image path or a CDN change on the store side.
- One bad rule rejects thousands. Feed rejections are rarely random; they cluster around a single cause. Fix the rule and the rejection rate usually drops back under threshold at the next sync.
- Act before Pinterest acts. The window between crossing the threshold and Pinterest pulling Verified Merchant status is your grace period. This card exists to make sure you use it. Fix the feed rule, force a re-sync, and confirm the rejection rate falls back below the threshold.
- The same feed may pass on Google. Google Shopping’s requirements differ from Pinterest’s, so a feed that is clean on Google can fail here. Do not assume a healthy Google feed means a healthy Pinterest feed.
- Rejection rate above threshold + single dominant reason = fix that feed rule now, re-sync.
- Rejection rate above threshold + many scattered reasons = a broader feed or source-data problem; audit the feed configuration.
- Rate rising but below threshold = early warning; fix before it crosses.
- High exposed spend/revenue = prioritise this above almost any other feed task.
Sibling cards merchants should reference together
| Card | Why pair it with this alert |
|---|---|
| Pinterest Active Shopping Pins on Out-of-Stock SKUs | The other catalogue-health card; both protect Shopping Pin distribution and feed integrity. |
| Pinterest Revenue by Campaign | Shows how much revenue runs through Shopping campaigns that depend on Verified Merchant status. |
| Pinterest Spend by Campaign | Quantifies the Shopping spend exposed if distribution is revoked. |
| Pinterest ROAS by Campaign | Shopping ROAS collapses if Verified Merchant status is lost; this card prevents that. |
| Pinterest Wasted-Spend Burst (3-day spike) | Rejected products that still draw spend before being pulled can show up as a burst. |
| Shopify Total Revenue | The commerce source whose catalogue feeds Pinterest; feed errors often originate in source data here. |
Reconciling against Pinterest Ads Manager
Where to look in Pinterest Ads Manager: Pinterest Ads Manager > Catalogs > the feed and product status view shows submitted, approved, and rejected counts plus rejection reasons. Pinterest’s business hub also surfaces Verified Merchant status and any warnings about it. Cross-reference your feed tool (Feedonomics or equivalent) for the transformation rules that produced the rejected attributes. This card combines Pinterest’s rejection data with the spend and revenue exposure that Pinterest’s catalogue view does not show alongside it. Why our number may legitimately differ from Pinterest’s UI:| Reason | Direction | Why |
|---|---|---|
| Rejection rate plus exposure vs raw counts | Different framing | Pinterest’s UI shows rejection counts and reasons. This card frames them against the spend and revenue at risk, which is what makes the rate actionable. |
| Feed sync timing | Snapshot differences | The rejection rate is measured at sync points. Between syncs, a fix applied in the feed tool will not yet show in Pinterest’s counts; the card reflects the latest available sync. |
| 30-day trend vs latest sync | Smoothing | The card uses a 30-day view to show whether feed health is trending toward or away from the threshold, not just the single latest snapshot. |
| Feed-tool vs Pinterest reasons | Mapping | Rejection reasons may be phrased differently in Feedonomics and Pinterest; the card maps them to the common cause where possible. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
shopify product catalogue / feed source | Rejected attributes should trace to missing or malformed source data or a feed transformation rule | A feed-tool rule built for Google can violate Pinterest’s stricter rules even when the source data is fine; the divergence is in the transformation, not the catalogue. |
google_ads Shopping feed health | Not a reconciliation, a comparison | A feed clean on Google can fail on Pinterest because requirements differ; do not assume parity. |