At a glance
Mirakl Feed Rejections (24h) counts the product-feed lines Target rejected at the Mirakl import in the last 24 hours. Target Plus catalogues are distributed through the Mirakl platform, often via a feed manager such as Feedonomics, and a rejection means a listing has dropped out of the catalogue or failed to update. Common causes are schema drift, attribute violations, and image-dimension violations. A spike means live or pending listings are silently disappearing, which both costs sales and feeds the feed-quality dimension of Target’s partner-status review.
| What it counts | The number of product-feed lines rejected at Target’s Mirakl import over the last 24 hours. |
| Sample type | Backend API data from Target Plus, refreshed on the standard data refresh. |
| Why it matters | Rejected lines never reach the catalogue, so listings stop selling, and a rising rejection rate is one of the triggers in Target’s partner-status review. |
| Reading the value | Any non-zero count is worth investigating; a sudden spike usually points to a single root cause such as a schema change in the feed. |
| Currency | count |
| Time window | 24H |
| Alert trigger | >0 import rejections |
| Sentiment key | tgt_alert_listing_rejection_spike |
| Roles | owner, operations |
Calculation
Vortex IQ reads the Mirakl feed-import results for your Target Plus partner account and counts the lines marked rejected within a rolling 24-hour window on each refresh. Each rejected line carries an import error reason, which the related listing cards expose so you can group rejections by cause. Because feeds typically flow from a source store through a feed manager into Mirakl, a single upstream change can produce many rejections at once, so the count is a sensitive early signal of a broken feed mapping. The window is fixed at 24 hours to keep the card focused on what is actively breaking rather than historical noise. See the worked example below for a typical spike pattern.Worked example
A representative reading of Mirakl Feed Rejections (24h) for a typical Target Plus partner. On 21 Jun 26 a beauty partner pushes a feed update from BigCommerce through Feedonomics. A category-mapping change drops the primary category attribute on 140 SKUs, and Target’s Mirakl import rejects all 140 lines for a missing required attribute. By the next refresh this card jumps from 0 to 140 and fires its alert. The operations lead opensrejected-listings-mirakl-import-errors, sees the common reason, fixes the mapping in Feedonomics, and re-submits the feed. By 22 Jun 26 the rolling count falls back toward zero. Use Vortex Mind to trace the rejection reason and the feed run that introduced it, and ask Ask Viq “what caused yesterday’s feed rejections and which SKUs were affected?”.
Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
rejected-listings-mirakl-import-errors | The listing-level detail behind the count, grouped by import error reason. |
mirakl-feed-import-success-rate | The companion success rate; watch it fall as rejections rise. |
listings-failing-feedonomics-target-mirakl-validation | Catches validation failures upstream in Feedonomics before Mirakl rejects them. |
brand-presentation-compliance-flags | Image and content violations often appear here as well as in feed rejections. |
partner-health-composite-crossed-threshold | The roll-up alert that can flip when the feed-rejection dimension breaches. |
Reconciling against Target Plus Partners
Where to look in the Target Plus Partners portal: Open the Mirakl feed import logs, which list each import run with its accepted and rejected line counts and the rejection reasons. The portal is the authority on which lines failed and why; this card surfaces the rolling 24-hour total so you notice a spike without opening every import log. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary | Vortex IQ uses a rolling 24-hour window; the portal groups by import run | Compare against the sum of import runs inside the same 24 hours, not a single run. |
| Time zone | The window boundary may differ from the portal’s reporting day | Confirm the import timestamps fall inside the same local window. |
| Filter scope | Vortex IQ counts rejected lines; the portal may also list warnings or skipped lines | Filter the portal log to rejections only before comparing. |
Known limitations / merchant FAQs
Q: How often does this card update? It refreshes on the standard data refresh over a rolling 24-hour window, so a new batch of rejections appears within a refresh cycle of the import that produced them. Q: Why does the Target Plus Partners number differ from this card? The portal reports per import run while this card sums rejections across the rolling 24 hours, and the portal may also count warnings or skipped lines that this card excludes. Filter the portal to rejections within the same window to reconcile. Q: How does this relate to the sibling metrics? This count is the headline;rejected-listings-mirakl-import-errors gives the line detail, and mirakl-feed-import-success-rate shows the same event as a rate.
Q: Can I change the alert threshold?
The default fires on any rejection. If your feeds routinely carry a small expected reject rate, raise the threshold in the Sensitivity tab so only meaningful spikes alert.