> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Listings Failing Feedonomics to Target Mirakl Validation, Target Plus > Listings Failing Feedonomics to Target Mirakl Validation for Target Plus stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Card class:** [Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Cross-Channel: Revenue at Risk](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Listings Failing Feedonomics to Target Mirakl Validation** is a Cross-Channel: Revenue at Risk metric. It joins what your Feedonomics feed manager distributed against what Target accepted at its Mirakl import, matching on the shared SKU, and reports the percentage of listings rejected at validation over the last seven days. A rejected listing never goes live, so every rejection is a product you cannot sell on Target Plus until the feed is fixed. A rate above 5% usually points to an attribute-mapping or schema problem in the feed pipeline, and feed-import quality feeds directly into Target's partner-status review. | | | | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The percentage of Feedonomics-distributed listings rejected at Target's Mirakl import over a rolling seven-day window. | | **Sample type** | Backend API data from Target Plus, refreshed on the standard data refresh. | | **Why it matters** | Rejected listings never reach buyers, and a sustained rejection rate signals a feed-pipeline fault that drags down the feed-import quality Target uses to review partner status. | | **Reading the value** | Read it as a rejection rate. Lower is better, and a rate above 5% is the line where a mapping or schema fault is likely. | | **Currency** | `percent` | | **Time window** | `7D` | | **Alert trigger** | `>5% rejection rate` | | **Sentiment key** | `tgt_xc_feed_rejection_vs_listings` | | **Roles** | owner, operations, engineering | ## Calculation Vortex IQ joins the listings Feedonomics distributed to Target against the records Target's Mirakl import accepted or rejected, matching on the shared SKU. For the rolling seven-day window it divides the count of rejected listings by the total listings submitted and expresses the result as a percentage. Because BigCommerce is the catalogue source of truth that feeds into Feedonomics, a rejection almost always traces back to how an attribute was mapped or transformed on its way out, not to the underlying product. Only listings that actually reached Mirakl validation count toward the denominator, so a feed that never ran does not deflate the rate. The worked example below shows how a typical reading breaks down. ## Worked example *A representative reading of **Listings Failing Feedonomics to Target Mirakl Validation** for a typical Target Plus partner.* On 16 Jun 26 an apparel partner added a new size attribute to its BigCommerce catalogue and the Feedonomics feed carried it forward. Across the seven days to 23 Jun 26, Feedonomics submitted 1,180 listings to Target's Mirakl import and 71 were rejected, a rate of 6.0% and over the 5% alert line. The rejections clustered on the new size field, which Mirakl expected in a controlled-value format the feed was sending as free text. Vortex Mind traced the upstream cause to the unmapped size attribute in the Feedonomics transform, and Ask Viq listed the 71 rejected SKUs and their shared error reason in plain English so the team could correct the mapping and re-submit in a single pass. ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | -------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | | [`listings-drifting-from-bc-source-of-truth`](/nerve-centre/kpi-cards/target-plus/listings-drifting-from-bc-source-of-truth) | A feed that rejects on some SKUs often leaves others live but drifted from BigCommerce. | | [`active-target-plus-listings-for-oos-skus-on-bc`](/nerve-centre/kpi-cards/target-plus/active-target-plus-listings-for-oos-skus-on-bc) | The same feed pipeline carries stock state, so validation faults and stock gaps tend to surface together. | | [`mirakl-feed-rejections-24h`](/nerve-centre/kpi-cards/target-plus/mirakl-feed-rejections-24h) | The 24-hour view catches a spike early before it shows up in the seven-day rate. | | [`rejected-listings-mirakl-import-errors`](/nerve-centre/kpi-cards/target-plus/rejected-listings-mirakl-import-errors) | Breaks the rejections down by specific import-error reason for faster fixes. | | [`mirakl-feed-import-success-rate`](/nerve-centre/kpi-cards/target-plus/mirakl-feed-import-success-rate) | The success rate is the inverse view and confirms the pipeline is healthy again after a fix. | ## Reconciling against Target Plus Partners **Where to look in the Target Plus Partners portal:** The Partners portal surfaces Target's own import results, listing which items were accepted or rejected at Mirakl validation, but it shows only Target's side of the handoff. To reconcile the rate you compare it against the other source, opening the Feedonomics feed logs to see what was actually submitted and how each attribute was transformed on the way out. The portal tells you what failed at Target, while the feed logs tell you why it failed upstream. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | ---------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | | A feed run straddles the seven-day boundary, so submissions and their rejections fall in different windows (period boundary / sync lag). | Vortex IQ may show a higher or lower rate than a single feed run suggests. | Align the feed run timestamp to the window before comparing against a one-off Feedonomics batch. | | Feedonomics submission times and the Target Plus refresh use different time zones. | A run near midnight can shift in or out of the seven-day window. | Compare using UTC-aligned timestamps for runs near the window edge. | | The card counts validation rejections only, not listings Feedonomics held back before submission. | Vortex IQ may show fewer failures than the full Feedonomics error log. | Scope your reconciliation to records that reached Mirakl validation to match the card. | **Cross-connector reconciliation:** Reconcile this metric against the Feedonomics feed logs rather than against Target Plus alone, since the Partners portal cannot see what the feed pipeline sent or transformed, and use Vortex Mind for any divergence investigation. ## Known limitations / merchant FAQs **Q: How often does this number update?** It refreshes on the standard data refresh, but because it joins the Feedonomics submission against the Target Mirakl result there is sync lag between a feed run completing and its acceptance or rejection landing, so a very recent run may not be fully reflected yet. **Q: Why is there no equivalent number in the Target Plus Partners portal?** The portal can report what Target rejected, but it has no view of the Feedonomics feed that produced those submissions, so it cannot express the result as a rate against what your pipeline actually sent. The percentage only exists once both sides are joined. **Q: How does this relate to the other cross-channel cards?** This card catches feed rejections as a rolling rate, while the drift card catches presentation mismatches on listings that did go live and the OOS-on-BC card catches stock gaps. They are different symptoms of the same BigCommerce-to-Feedonomics-to-Target pipeline. **Q: Can I change the alert threshold?** Yes. The default alerts above a 5% rejection rate, and you can move that line on the Sensitivity tab to match how tolerant your feed cadence is to short spikes. *** ### Tracked live in Vortex IQ Nerve Centre *Listings Failing Feedonomics to Target Mirakl Validation* is one of hundreds of KPI pulses Vortex IQ tracks across Target Plus 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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.