Amazon Ecommerce Analytics Setup Guide: From Seller Central to Real Dashboards
by Trivas.ai
|
8 min read
Sep 24, 2026
Most Amazon sellers don't have an analytics problem. They have a plumbing problem. The data exists, but it's scattered across Seller Central reports, an Ads dashboard, and a spreadsheet someone updates every Monday if they remember. This Amazon ecommerce analytics setup guide walks through what an actual working setup looks like, from connecting your accounts to the metrics worth checking every week.
Why Most Amazon Sellers Get Analytics Setup Wrong
Seller Central's native reports feel like analytics. They're not. They lag 24 to 48 hours behind reality, and they live in total isolation from your ad spend, let alone your Shopify numbers if you sell direct too. You can't calculate true TACOS from Seller Central alone. You can't even see same-day Buy Box trends reliably.
So sellers build spreadsheets. Export from Seller Central, export from Amazon Ads, paste into a master sheet, pray the SKU formatting matches this week. It works, sort of, until it doesn't.
Past roughly $1M a month in Amazon revenue, this breaks. Not gradually. It breaks hard, usually the week someone's on vacation and the export doesn't happen. Too many SKUs, too many campaigns, too many manual steps for one person to own reliably.
Here's the part that surprises people: fixing this properly takes hours, not weeks. Connecting SP-API and the Ads API, landing the data in a warehouse, and standing up real dashboards is an afternoon of work with the right setup, not a quarter-long project.
What You Need Before You Start
Before touching any tool, get four things sorted.
First, Seller Central admin access with API permissions enabled. Not a viewer account, actual admin rights, since the Selling Partner API authorization flow requires it.
Second, access to your Amazon Ads account covering Sponsored Products, Sponsored Brands, and Sponsored Display. Ad spend data lives on a completely separate API from your sales data, and you'll need both.
Third, decide upfront whether you need single-marketplace reporting or multi-marketplace (US plus EU, for instance). This matters because currency conversion, VAT handling, and even fee structures differ by marketplace, and retrofitting multi-marketplace support after building single-market dashboards means redoing a chunk of the work.
Fourth, write down the KPIs your team currently tracks by hand. Every seller has some version of this list already, whether it's a weekly ACOS number pulled manually or a margin calculation someone keeps in their head. If you skip this step, you'll migrate to a shiny new dashboard setup and quietly lose track of the two or three numbers that actually run the business.
Step 1: Connect Your Amazon Seller Central and Ads Data
Use the Selling Partner API (SP-API), not the legacy MWS. Amazon has been sunsetting MWS access for years now, and building on it in 2024 or later is building on borrowed time.
SP-API isn't one clean feed. Order data, inventory and FBA data, returns, and settlement reports each come from different endpoints, with different refresh rates and different quirks. Treat them as separate connections, not one unified pull, or your setup will break the moment one endpoint changes its schema.
Amazon Ads data needs its own connection through the Ads API entirely. This is where spend, ACOS, and TACOS live at the campaign and keyword level. A lot of sellers assume Seller Central and Ads share a backend. They don't.
For sync frequency, hourly works well for ad spend, since campaign decisions often need same-day visibility. Settlement and financial data can run daily since Amazon itself doesn't finalize those numbers faster than that anyway. If you're doing this connection work yourself, Trivas's guide to data integration covers the practical side of keeping these connections stable as Amazon updates its APIs.
Step 2: Centralize the Data in a Warehouse
Once you're pulling from SP-API and the Ads API, that data needs somewhere to live besides the Seller Central UI. Trivas routes it into Amazon Redshift, which keeps everything queryable in one place instead of siloed across five different login screens.
This is the step that actually changes what's possible. With Amazon data sitting next to Shopify, Meta, Google Ads, and GA4 data in the same warehouse, you can finally calculate blended ROAS across your whole business, not just an Amazon-only version that ignores half your ad spend.
It's also the difference between a setup that survives and one that quietly rots. Screen-scraping tools that read Seller Central's UI break every time Amazon tweaks a report layout, and Amazon tweaks report layouts often. A warehouse-based pull through official APIs handles schema changes far more gracefully, because you're working with structured data contracts instead of scraping pixels off a page.
Step 3: Build the Core Dashboards
With data centralized, four dashboards cover most of what a seller actually needs day to day.
Sales dashboard. Units sold, revenue, refunds, and net proceeds, broken out by SKU and marketplace. Net proceeds matters more than gross revenue here since it already accounts for Amazon's cut.
Ad performance dashboard. ACOS, TACOS, CPC, and spend split by campaign type, Sponsored Products versus Sponsored Brands versus Sponsored Display. These three campaign types behave differently enough that blending them into one number hides more than it reveals.
Inventory dashboard. Sell-through rate, days of cover, and FBA storage fee exposure. Storage fees creep up quietly on slow-moving SKUs, and this is usually the dashboard that pays for itself fastest.
Profitability view. Landed cost, referral fees, FBA fees, and true margin per SKU. Revenue is not profit, and Amazon's fee structure eats more of a SKU's margin than most sellers realize until they see it laid out per unit.
A handful of metrics deserve weekly attention. The rest is noise most weeks.
TACOS should be your north star for ad efficiency, since it measures ad spend against total sales, not just ad-attributed sales. ACOS alone can look great while your organic sales quietly shrink underneath it.
Buy Box win rate matters more than most sellers give it credit for. Lose the Buy Box and your conversion rate collapses almost immediately, even if your listing itself hasn't changed at all.
Contribution margin after Amazon fees is the number leadership should watch weekly, not gross revenue. Revenue can grow while margin shrinks if referral fees or FBA fees creep up, and gross numbers hide that completely.
Session-to-order conversion rate by ASIN catches listing problems early, before Amazon's algorithm notices and starts suppressing your rank. A dropping conversion rate on one ASIN is usually the first sign something's wrong, weeks before revenue actually drops.
Common Setup Mistakes to Avoid
Three mistakes show up over and over.
The biggest one: treating Amazon Ads spend and Seller Central sales as two separate reports instead of joining them. Without that join, you can't calculate real TACOS, and TACOS is the metric that tells you whether your ad spend is actually healthy relative to overall sales.
Second, ignoring FBA reimbursements and returns data. These aren't rounding errors. Unreconciled reimbursements and returns can quietly erode 3 to 5% of net revenue, and most sellers never notice because that data sits in a different report than the one they check.
Third, setting up dashboards once and never touching the metric definitions again. Amazon changes fee structures. Referral fee percentages shift, FBA fee tiers get restructured, and a margin calculation built on last year's fee schedule will quietly drift wrong. Revisit the definitions at least quarterly.
Where AI and Forecasting Fit Into Your Setup
Once your data is actually centralized, an AI layer becomes genuinely useful rather than a gimmick bolted onto a dashboard. It can flag a sudden ACOS spike or a Buy Box loss the moment it happens instead of waiting for someone to spot it during Friday's weekly review.
Forecasting is the other piece. Models built on historical Amazon sales plus ad spend trends can project inventory needs well enough to catch an FBA stockout before it happens, which matters since a stockout doesn't just lose sales, it can tank your listing's rank for weeks after you restock.
This is roughly where manual setups hit a ceiling. Spreadsheets and even basic dashboards can show you what happened. Catching what's about to happen, and doing it without someone manually cross-referencing five reports, is where a platform-based approach starts earning its cost.
Get Your Amazon Analytics Running Without the Manual Work
The core setup doesn't change: connect SP-API and the Ads API, centralize everything in a warehouse, build the four core dashboards, and track TACOS, Buy Box rate, contribution margin, and conversion by ASIN as your weekly numbers.
If you'd rather not hand-roll each piece, Trivas's Amazon solution and Amazon-specific pricing are built around exactly this setup, pre-connected and ready to run against your own account data.
If you're still deciding how deep to go on your own, subscribe to keep learning as we cover more of this, or start a trial and see the dashboards running against your actual Amazon numbers.
Content author and contributor at Trivas.ai, sharing insights on e-commerce analytics, business intelligence, and data-driven strategies to help businesses grow.
Continue Reading
explore more insights
What Is AI-Powered Attribution for Shopify? A Straight Answer for DTC Teams
3 min read
What Is a Data Silo in Ecommerce (and Why It's Costing You Sales)
3 min read
The Ecommerce Analytics Platform That Catches Bad Data Before You Report On It
.d53b12e5.png&w=3840&q=75 "Trivas.ai")
by Trivas.ai
