At a glance
Rejected Listings (Mirakl import errors) counts the feed lines Target’s Mirakl import refused over the last 7 days. Because Target Plus distributes product feeds through the Mirakl platform, often via a feed manager such as Feedonomics, any line that fails validation never reaches the curated storefront. Common causes are a missing required attribute, a GTIN check-digit failure, or an image-dimension violation, and every rejected line is a SKU that cannot sell until it is fixed.
| What it counts | Feed lines that Target’s Mirakl import rejected over the last 7 days. |
| Sample type | Backend API data from Target Plus, refreshed on the standard data refresh. |
| Why it matters | Rejected lines are SKUs missing from the catalogue, and a rising count drags down feed-import quality, one of the inputs Target weighs when reviewing partner status. |
| Reading the value | Any value above zero is actionable; treat each rejected line as a SKU to diagnose and resubmit. |
| Currency | count |
| Time window | 7D |
| Alert trigger | >0 |
| Sentiment key | tgt_rejected_listings |
| Roles | owner, operations |
Calculation
Vortex IQ reads the Mirakl import results for your Target Plus feed and counts every line marked as rejected across the trailing 7 days. The count groups errors regardless of cause, so a single SKU rejected for a missing attribute and another rejected for a bad image both add one to the total. Because the alert fires on any value above zero, the card is designed to surface import failures the moment they appear rather than waiting for a backlog. See the worked example for how this reads on a typical partner.Worked example
A representative reading of Rejected Listings (Mirakl import errors) for a typical Target Plus partner. On 14 Jun 26 a beauty partner pushes a 600-line feed update through Feedonomics into Target’s Mirakl import. The next refresh shows Rejected Listings at 23, up from its usual zero. Drilling in, 18 of the rejections share a single cause: a new product range shipped without the required country-of-origin attribute, and 5 more failed a GTIN check-digit test after a spreadsheet truncated leading zeros. Those 23 SKUs are invisible to Target guests until corrected, so the partner patches the missing attribute in the feed source and re-runs the import. Vortex Mind groups the rejections by error type so the team fixes one root cause instead of 23 line items, and Ask Viq answers “what is blocking my new range from going live” in plain English.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
mirakl-feed-rejections-24h | The 24-hour view that catches a bad feed push within a day. |
mirakl-feed-import-success-rate | Frames rejections as a share of total feed lines processed. |
listings-failing-feedonomics-target-mirakl-validation | Pinpoints lines failing validation before they reach Target. |
brand-presentation-compliance-flags | Image and content rejections often overlap with brand-presentation flags. |
inactive-suspended-listings | Persistent rejections can leave SKUs inactive or suspended. |
Reconciling against Target Plus Partners
Where to look in the Target Plus Partners portal: Open the Mirakl feed import logs and review the most recent import reports, which list each rejected line with its error reason. Cross-check against listing status to confirm which SKUs never went live. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary | Either | The card sums a rolling 7-day window; a portal report for a single import run covers a narrower slice, so totals will not match line-for-line. |
| Time zone | Either | Import timestamps use Target’s reference time zone; align your 7-day window before comparing counts. |
| Filter scope | Vortex IQ may show more | The card counts all rejected lines, while a portal view may already exclude lines you have since corrected and resubmitted successfully. |