At a glance
Listings Drifting from BC Source-of-Truth is a Cross-Channel: Revenue at Risk metric. It joins your live Target Plus catalogue against the BigCommerce record you treat as the source of truth, matching on the shared SKU, and counts the SKUs whose Target Plus content has drifted away from BigCommerce. Because Target curates the Target Plus catalogue by hand, drifted titles, specs, or images get read as brand-presentation drift and can pull a listing into manual review. Any sustained drift chips away at the curated brand positioning that lets Target Plus command its premium, so revenue sits at risk well before a listing is pulled.
| What it counts | The number of SKUs whose Target Plus catalogue content (title, specs, images) differs from the matching BigCommerce source-of-truth record. |
| Sample type | Backend API data from Target Plus, refreshed on the standard data refresh. |
| Why it matters | Drift between your premium Target Plus listing and your authoritative BigCommerce record reads as brand-presentation drift to Target’s curators and risks listings being pulled into review. |
| Reading the value | Read it as a count of drifting SKUs. Zero is the target, and any non-zero value is worth a look before it grows. |
| Currency | number |
| Time window | 30D |
| Alert trigger | >10 SKUs drifting |
| Sentiment key | tgt_xc_catalogue_drift_vs_bc |
| Roles | owner, marketing, operations |
Calculation
Vortex IQ takes every active Target Plus listing and matches it to its BigCommerce product by the shared SKU identifier, since BigCommerce is the catalogue source of truth for these merchants. For each matched pair it compares the presentation fields that Target curates against - product title, key specifications, and images - and marks the SKU as drifting when the Target Plus content no longer agrees with the BigCommerce record. Each drifted SKU counts once toward the value regardless of how many individual fields differ, so the number reflects affected products rather than a raw diff count. SKUs that exist on only one side are excluded from drift and surface through the catalogue and feed-validation siblings instead. The worked example below shows how a typical reading breaks down.Worked example
A representative reading of Listings Drifting from BC Source-of-Truth for a typical Target Plus partner. On 18 Jun 26 a homeware partner pushed a seasonal copy refresh to BigCommerce, updating product titles and hero images for 240 SKUs. By the 30-day reading on 23 Jun 26 the card showed 14 SKUs drifting, above the alert line of 10. Tracing it back, the refreshed titles and images had landed in BigCommerce but had not yet propagated to the Target Plus listings, so the two records disagreed on those 14 SKUs. Vortex Mind traced the upstream cause to a partial feed run that skipped the image-and-title attribute group during the refresh window, and Ask Viq returned the exact list of 14 drifting SKUs in plain English so the team could re-push them before any landed in Target’s curation review.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
listings-failing-feedonomics-target-mirakl-validation | Drift often starts as a feed that was sent but rejected at import, so check the validation rate alongside it. |
active-target-plus-listings-for-oos-skus-on-bc | The same BigCommerce-to-Target sync gap that drifts content also leaves stock state out of step. |
skus-priced-differently-vs-walmart-amazon | Price is another field that drifts across channels and erodes the curated premium. |
listing-quality-score | Drifted titles, specs, and images drag down the curated quality score Target measures. |
brand-presentation-compliance-flags | Drift is the most common upstream trigger for brand-presentation flags. |
Reconciling against Target Plus Partners
Where to look in the Target Plus Partners portal: The Partners portal shows the listing content as Target currently holds it, item by item, but it shows only Target’s own side of each record. To reconcile drift you compare that against the other source, opening the matching product in the BigCommerce admin (your source of truth) and checking title, specs, and images field by field. The portal cannot tell you that a value is stale, only what it currently is. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| A BigCommerce edit lands before the next feed sync, so the two sides disagree until propagation completes (period boundary / sync lag). | Vortex IQ may show drift the portal has not yet caught up to. | Wait for the next feed run, then re-check the SKU before treating it as a true drift. |
| BigCommerce edit timestamps and the Target Plus refresh use different time zones. | A same-day change can appear inside or outside the 30-day window depending on zone. | Compare using UTC-aligned timestamps when a SKU sits near the window edge. |
| The card compares only the curated presentation fields, not every BigCommerce attribute. | Vortex IQ may count fewer drifts than a full field-by-field diff would. | Limit your manual reconciliation to title, specs, and images to match the card’s scope. |