Correction: Traffic data is not available in the sourcing view query of the Data Kiosk Vendor Analytics dataset
On December 3 2025 Amazon added the lostFeaturedOffer field to the Traffic segment of the Vendor Analytics dataset, but it is only accessible via the manufacturingView query. The earlier claim that it would also appear in sourcingView was retracted, meaning sourcingView now returns no Traffic rows for this field.
Overview
On December 3 2025 Amazon announced that the lostFeaturedOffer field would be added to the Traffic data set within the Vendor Analytics dataset accessible through Data Kiosk. The original release mistakenly claimed that this new field would appear in both the manufacturingView and sourcingView queries. The correction clarifies that Traffic data, including lostFeaturedOffer, is only available through the manufacturingView query, not the sourcingView query. Sellers who rely on sourcing‑focused analytics must adjust their data‑retrieval processes immediately.
Key Points
- Announcement date — The update was communicated on December 3 2025, setting a clear timeline for vendors to expect the new field.
- Field added — lostFeaturedOffer now appears in the Traffic segment of the Vendor Analytics dataset, enabling deeper insight into offers that lost featured status.
- Incorrect initial claim — Early documentation said the field would be present in both manufacturingView and sourcingView queries; this was later retracted.
- Current availability — Traffic data, together with lostFeaturedOffer, can be queried only through manufacturingView; the sourcingView query returns no Traffic rows for this field.
- Impact on reporting — Any dashboards, alerts, or automated extracts that reference sourcingView for Traffic metrics will return empty results for lostFeaturedOffer.
- Action deadline — Vendors should revise their query logic before the next scheduled data refresh cycle to avoid gaps in analytics.
How the Traffic Data Query Works
- Select the manufacturingView query — When a vendor runs a query against manufacturingView, the response includes all Traffic‑related columns, such as impressions, clicks, and the newly added lostFeaturedOffer. Example: A query for ASIN B07XYZ returns a row showing 12,340 impressions, 1,210 clicks, and a lostFeaturedOffer value of 5.
- Attempt to use sourcingView — Executing the same request against sourcingView will return the standard sales and inventory columns but will omit any Traffic fields, including lostFeaturedOffer.
Analysis & Recommendations
Why This Matters
Vendors using the sourcingView to track lost featured offers will see empty results, causing inaccurate performance reporting and potential budgeting errors. Immediate query changes are required before the next data refresh to maintain reliable analytics.
Key Takeaways
- lostFeaturedOffer was added on Dec 3 2025 but is only returned by manufacturingView, not sourcingView.
- SourcingView queries now return zero Traffic rows for lostFeaturedOffer, leading to empty metric values.
- Vendors must run two separate queries—manufacturingView for Traffic and sourcingView for sourcing metrics—and merge them on ASIN or SKU.
- All dashboards, alerts, and ETL jobs referencing sourcingView for Traffic data must be updated before the next scheduled refresh.
Recommended Actions
- →In Seller Central > Data Kiosk > Query Builder, replace any 'FROM sourcingView' references for lostFeaturedOffer with 'FROM manufacturingView' and ...
- →Update ETL pipelines (e.g., AWS Glue jobs) to pull Traffic data from manufacturingView, store it in a staging table, then join with sourcingView da...
- →Run a schema inspection in Data Kiosk to confirm the lostFeaturedOffer column appears and contains non‑null values, then validate the merged report.
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!