Analytics
Cross-integration analytics combining SP-API sales and Ads-API spend.
Cross-channel Analytics
The Analytics view fuses SP-API sales data with Ads API spend data so you can see metrics that neither source alone can produce — TACOS, organic vs paid contribution, ad-driven AOV, and category-level efficiency.
What it shows
(Numbers above are placeholders — your dashboard shows live values.)
How to read it
Top KPI band
Six metrics computed from the joined dataset. Period defaults to last 30 days; pick any range up to your historical sync window.
Trend chart
Daily ad spend vs. total sales over the chosen period. Look for divergence — rising spend with flat sales = inefficient growth.
Breakdown table
Per-ASIN or per-portfolio rows showing all six KPIs. Sortable and exportable.
Filter strip
Marketplace, ad product (SP / SB / SD / DSP), and date range. Apply once and the whole view re-renders.
Use cases
You suspect ads are cannibalising organic sales — TACOS keeps climbing but ROAS looks fine. The cross-channel view shows the truth: maybe ads are just stealing clicks from your own organic listing.
A client asks “what's the real impact of doubling our ad budget?” The breakdown by ASIN shows you which products responded with incremental total sales vs. which just spent more for the same total revenue.
You need a single number to put in front of the CFO. Analytics gives you TACOS in one click — and the trend tells you whether marketing efficiency is improving quarter over quarter.
Best practices
- ✓Compare TACOS across marketplaces — wildly different TACOS often points at competitive intensity, not your strategy.
- ✓Export the breakdown table to feed your weekly internal review.
- ✓Run the historical sync first so the trend chart has a meaningful baseline.
- ✗Use ACOS alone to evaluate ad health on this view — TACOS is the more honest measure when sales channels mix.
- ✗Compare ad-attributed sales week-to-week with raw click data — attribution windows differ across ad products.