At a glance
Listings Failing Feedonomics Validation is a cross-channel metric tracked from your feed pipeline into Vinted. It is the share of listings that fail validation in the Feedonomics feed layer before they reach Vinted, typically for missing required attributes, malformed values, or category mapping errors. A failing listing never makes it live, so this card catches lost reach at the source, upstream of anything visible on Vinted itself.
| What it counts | The percentage of listings failing Feedonomics validation in the feed pipeline over the selected period. |
| Sample type | Feed-pipeline validation data ahead of the Vinted integration, refreshed on the standard data refresh. |
| Why it matters | Validation failures are silent: the listing simply never appears on Vinted. A rising failure rate means reach is leaking before it ever reaches buyers, and the cause is usually a fixable data or mapping issue. |
| Reading the value | Lower is better. A rate above the safe band means a meaningful slice of listings is being rejected upstream and needs attribute or mapping fixes to get live. |
| Currency | percent |
| Time window | 7D |
| Alert trigger | Fires when the validation failure rate rises above the configured ceiling. |
| Sentiment key | vin_xc_feed_rejection_vs_listings |
| Roles | owner, operations, engineering |
Calculation
Calculated automatically from your feed pipeline. Vortex IQ divides the count of listings failing Feedonomics validation by the total submitted for validation over the selected period. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A representative reading of Listings Failing Feedonomics Validation for a typical Pro seller on Vinted. The failure rate normally sits near 1%. Over a 7-day window it climbs to 6%, past the ceiling. The pattern points to a recent catalogue change: a new product line uses a size format Vinted does not accept, and the mapping rule was not updated, so every item in that line fails validation and never reaches Vinted. The action is for the operations or engineering owner to fix the size mapping in the feed configuration, after which the line revalidates and goes live. The lesson is to test mapping when introducing a new attribute format. For deeper investigation, use Vortex Mind to group failures by error type; for natural-language exploration, ask Ask Viq.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
vin_xc_catalogue_drift_vs_bc | Cross-channel sibling: catalogue drift that validation failures can cause. |
vin_attribute_completeness | Listing-health sibling: the attributes validation checks for. |
vin_alert_listing_rejection_spike | Alert sibling: listings removed once live, the downstream symptom. |
vin_total_listings | Listing-health sibling: the catalogue these listings should join. |
vin_revenue_at_risk | Executive sibling: revenue lost while listings cannot go live. |
Reconciling against Vinted
Where to look in Vinted’s own dashboard: Vinted never sees these listings, since they fail before reaching it, so there is nothing in the Vinted dashboard to reconcile against directly. The authoritative source is the Feedonomics feed dashboard, where validation errors and reasons are logged. Reconcile by comparing this card’s failure rate against the Feedonomics error report for the same window. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Window boundary. Vortex IQ uses a 7-day window; the feed dashboard may report per-run or per-day. | Variable | Match the window to the feed report. |
| Denominator. Vortex IQ measures failures as a share of submitted listings; a raw error count is not a rate. | Variable | Compare rate-to-rate, not count-to-rate. |
| Error classification. Some warnings may not count as hard failures. | Variable | Confirm which severities count as a failure. |