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.
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.
How to read it:
- 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
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:
Cross-connector reconciliation:
The fix usually lives in the feed tool or the source catalogue, not in Pinterest. Reconcile the rejected attributes back to their source.