Amazon Expands Data Kiosk API With Customer Feedback Metrics and Vendor Code Segmentation
Amazon added two new feedback metrics—customerReviewsTopics and customerReturnTopics—to the Data Kiosk API and introduced a vendorCode group‑by attribute. Queries must now include asin in groupBy for these metrics, and the metrics are non‑additive, requiring snapshotDate instead of date ranges.
Overview
Amazon has upgraded the Data Kiosk API’s Vendor Analytics dataset, adding two customer‑feedback metrics and a vendor‑code grouping field. The new metrics deliver structured sentiment and return‑reason data at both product and category levels, while the grouping attribute lets multi‑account vendors slice performance by operational unit. All changes are live across every Amazon marketplace, giving sellers immediate access to richer insights.
Key Points
- customerReviewsTopics metric — Returns the most frequent positive and negative review themes together with the star‑rating impact for each ASIN and for entire browse nodes.
- customerReturnTopics metric — Supplies aggregated return‑reason statistics at the browse‑node level, highlighting category‑wide patterns that individual ASIN reports often miss.
- vendorCode group‑by attribute — Enables API queries to segment results by vendor code, allowing direct comparison of separate business units or regional accounts.
- Global rollout — The new fields are available on every Amazon marketplace, from the United States to Japan, without the need for regional enablement.
- Mandatory ASIN grouping — Queries that request the feedback metrics must include
asinin thegroupByclause, otherwise the API returns an error. - Non‑additive time windows — Feedback metrics do not sum across date ranges, so standard period filters behave differently than for sales or traffic data.
How the New Metrics Work
-
Requesting review topics — Include
customerReviewsTopicsin themetricsarray and setgroupBytoasin(or bothasinandbrowseNode). The response lists top positive and negative themes, each paired with a “rating impact” score that quantifies how much the theme shifts the average star rating.
Example: A query for ASIN B07XYZ returns “packaging damage” as a negative theme with a –0.42 impact, indicating that this complaint drags the product’s rating down by roughly four‑tenths of a star.
Analysis & Recommendations
Why This Matters
The new metrics give sellers instant, pre‑processed sentiment scores (e.g., a –0.42 rating impact for “packaging damage”) and return‑reason percentages, eliminating manual text mining. VendorCode grouping lets regional units pull separate results in a single call, speeding up dashboards and reducing errors. Because the metrics are non‑additive, using snapshotDate enables accurate before‑after c...
Key Takeaways
- customerReviewsTopics metric returns top positive/negative review themes with a rating‑impact score per ASIN or browse node.
- customerReturnTopics metric aggregates return‑reason percentages at the browse‑node level.
- vendorCode can be added to the groupBy array to segment results by business unit or region.
- Feedback metrics require asin in groupBy and ignore startDate/endDate; use snapshotDate for point‑in‑time snapshots.
Recommended Actions
- →Update your SP‑API Data Kiosk requests to include customerReviewsTopics or customerReturnTopics in the metrics array and ensure asin is listed in g...
- →Add vendorCode to the groupBy array in your API calls to generate separate rows for each vendor unit.
- →Create a nightly job that queries the API with a snapshotDate, flags any ASIN where a negative theme impact ≤ -0.30, and auto‑creates a task in you...
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!