At a glance
Mirakl Feed Import Success Rate is the share of product-feed import lines accepted by Target over the last 7 days, expressed as a percentage. Target Plus distributes catalogue data through the Mirakl platform, often via a feed manager such as Feedonomics, so this rate is the heartbeat of your listing pipeline. A rate below 95% usually signals an attribute-schema regression worth investigating before it cascades into rejected or suspended listings. It is the positive counterpart to feed rejections: when this falls, expect rejection cards to climb.
| What it counts | The percentage of Mirakl product-feed import lines accepted by Target over the last 7 days. |
| Sample type | Backend API data from Target Plus, refreshed on the standard data refresh. |
| Why it matters | A falling success rate means listings are not landing, which throttles catalogue health and feeds Target’s partner review. |
| Reading the value | Higher is better. Keep it at or above 95%; a dip below points to an attribute or schema problem. |
| Currency | percent |
| Time window | 7D |
| Alert trigger | <95% |
| Sentiment key | tgt_mirakl_feed_success_rate |
| Roles | owner, operations, engineering |
Calculation
Vortex IQ takes the count of Mirakl feed import lines Target accepted over the last 7 days and divides it by the total lines submitted in that window, then expresses the result as a percentage. Rejected lines, whether from missing attributes, format mismatches, or validation failures, drag the rate down. The alert fires when the rolling 7-day success rate falls below 95%, the level at which a schema or mapping regression usually becomes the likely cause. Because it is the inverse view of feed rejections, this card and the rejection cards should always tell a consistent story. The worked example below shows how a single mapping change dents the rate.Worked example
A representative reading of Mirakl Feed Import Success Rate for a typical Target Plus partner. For the 7 days to 16 Jun 26 a beauty partner’s feed ran at 99.2% acceptance, with only a handful of lines bouncing. On 20 Jun 26 their feed manager rolled out a colour-attribute mapping change that did not match Target’s expected values, and by 23 Jun 26 the rolling rate had slipped to 93%, tripping the alert. Roughly 70 product lines were now bouncing each run, meaning new and updated listings were not landing and the catalogue was quietly going stale. Vortex Mind traced the drop to the colour-attribute mapping change rather than a Target-side issue, and Ask Viq answered “why did my feed success rate fall below 95% this week” in plain English so the engineering team could revert the mapping the same afternoon.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
mirakl-feed-rejections-24h | The short-window rejection count that this rate inverts. |
rejected-listings-mirakl-import-errors | Names the listings failing import so you can fix the worst offenders. |
listings-failing-feedonomics-target-mirakl-validation | Pinpoints validation failures in the Feedonomics-to-Mirakl path. |
brand-presentation-compliance-flags | Presentation issues often surface alongside feed-quality problems. |
total-listings | Confirms whether a low success rate is suppressing your catalogue size. |
Reconciling against Target Plus Partners
Where to look in the Target Plus Partners portal: Open the Mirakl feed import logs, which list accepted and rejected lines per import run along with the rejection reasons. Sum accepted against total over a matching 7-day span to reconcile against this card. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary (rolling 7D vs per-run logs) | Either | Aggregate the per-run logs across the same 7-day window before comparing. |
| Time zone of import run timestamps | Either | Confirm whether the logs are timestamped in your zone or Target’s when bucketing by day. |
| Filter scope (lines vs distinct SKUs) | Vortex IQ may differ | Check whether the portal counts feed lines or distinct products; align the unit to the card. |
Known limitations / merchant FAQs
Q: How often does this number update? It refreshes on the standard Vortex IQ data refresh and is calculated over a rolling 7-day window. Q: Why does the Partners portal show a different rate? The portal logs are per import run and may count feed lines rather than distinct SKUs. Aggregate across the same 7-day window and align the unit before reconciling. Q: How does this relate to the sibling cards? It is the inverse ofmirakl-feed-rejections-24h and moves opposite to rejected-listings-mirakl-import-errors and listings-failing-feedonomics-target-mirakl-validation.
Q: Can I change the alert threshold?
Yes. The default fires below 95%, but you can adjust the floor for this card on the Sensitivity tab to match your feed’s normal baseline.