Amazon Ecommerce Analytics Setup Guide: From Seller Central to a Working Dashboard
by Trivas.ai
|
8 min read
Sep 08, 2026
Why Amazon Analytics Setup Trips Up Most Sellers
Most sellers don't have an analytics problem. They have a data-scattered-across-three-systems problem.
Seller Central splits everything into Business Reports, Brand Analytics, and the Advertising Console. None of these talk to each other. Business Reports gives you organic sales by SKU. Brand Analytics gives you search terms, but only weekly. Advertising Console gives you ad spend and ACOS, but it's blind to your actual margin. If you want one number that tells you whether a product is profitable, you're stitching it together yourself.
That's where the manual CSV routine comes in, and it works fine until it doesn't. Pull reports, drop them in a spreadsheet, build some VLOOKUPs. Then your SKU count crosses a few hundred, or you add a second marketplace, and the whole thing collapses under its own weight. Formulas break. Someone forgets to update a tab. Now finance is arguing with marketing over whose number is right.
The real cost isn't the spreadsheet crash. It's the hours. Teams doing this manually routinely burn 3+ hours a week just reconciling ad spend against sales, before anyone actually looks at what the numbers mean. That's a part-time job spent on data plumbing instead of decisions.
This guide walks through an actual Amazon ecommerce analytics setup guide you can follow: which data sources to connect, in what order, what to check before you trust a single dashboard number. No fluff, no "it depends" hand-waving. Just the sequence that works.
The Data Sources You Need Before You Start
Before touching a dashboard tool, get clear on what you're actually pulling from. There are three core sources.
Seller Central Reports API covers your orders, returns, and FBA inventory data. This is your ground truth for what actually sold and what came back. It's also where settlement data lives, which matters more than most people realize (more on that below).
Amazon Advertising API covers Sponsored Products, Sponsored Brands, and Sponsored Display: spend, clicks, and attributed sales. This is a separate system from Seller Central entirely, with its own authentication and its own data structure.
Amazon Brand Analytics gives you search term data and market basket info, but only if you're brand-registered. If you're not, skip this one. If you are, know that it updates weekly, not daily. Treat it that way from day one.
Each of these needs its own permissions. You'll need SP-API (the successor to MWS) developer credentials for Seller Central data, and separate ad account access levels for the Advertising API, typically at the admin or ad account owner tier. Getting these credentials approved can take a few days if you've never registered as a developer with Amazon, so don't leave this until the day before you need the dashboard live.
Step-by-Step: Connecting Amazon Data to a Central Warehouse
Step 1: Authorize API access and confirm scopes. Don't just request "access." Confirm your SP-API scopes explicitly cover Orders, Finances, and Reports endpoints. Missing the Finances scope is the single most common reason people can't reconcile fees later.
Step 2: Set a sync cadence around settlement timing. Amazon settlement data typically lags 24 to 48 hours behind what shows up in your order reports. If you sync everything hourly and expect same-day accuracy on fees and payouts, you'll chase numbers that keep moving. Set expectations with your team now: yesterday's numbers are provisional, day-before-yesterday's are closer to final.
Step 3: Land raw data in a warehouse layer, not straight into a dashboard tool. This is where a lot of DIY setups go wrong. Pulling API data directly into a BI tool skips the step where you can clean, dedupe, and reconcile before anything gets visualized. Trivas runs this layer on Amazon Redshift specifically so raw Amazon data lands somewhere queryable and auditable before it hits a chart. If a number looks wrong, you can trace it back.
Step 4: Map SKUs and ASINs consistently across Seller Central and Advertising data. Ad campaigns target ASINs. Your sales and inventory data is often organized by SKU, and sellers frequently have multiple SKUs mapping to one ASIN (different pack sizes, bundles, etc). If this mapping isn't consistent, your ad spend won't join cleanly to sales, and your ACOS numbers will quietly lie to you.
Common blockers worth flagging up front: throttled API calls once you're pulling data across multiple report types, mismatched currency and timezone settings across marketplaces, and settlement reports that arrive later than expected around holidays. None of these are exotic problems, but they all show up eventually. If you want more detail on how integration timing and syncing generally work, our data integration help docs cover the broader mechanics.
Building Your Core Amazon Dashboards
Once data's landing reliably, you need three dashboards, not one giant one trying to do everything.
Sales and profitability view. This should show net revenue after Amazon referral fees, FBA storage and fulfillment costs, and returns, not gross sales. Gross sales makes everything look healthier than it is. Net is the number that should drive decisions.
Ad performance view. Track ACOS and TACOS separately, broken out by campaign type. ACOS tells you campaign efficiency. TACOS tells you what ad spend is doing to the business as a whole. Confusing the two is how teams end up scaling a campaign that looks great in isolation but is actually cannibalizing organic sales.
Inventory health view. Sell-through rate, days of cover, and restock alerts, all tied directly to FBA data. A profitability dashboard means nothing if you're out of stock on your best seller for two weeks.
Here's the thing most setups get wrong: they build an ad performance view and a sales view as two completely separate dashboards, then never blend them. That's backwards. If you can't see organic and paid sales for the same SKU side by side, you can't tell whether a product is actually profitable or just profitable-looking because ad spend is propping up rankings that would otherwise slip. True product profitability requires both numbers on one screen, not two tabs open at once.
Connecting Amazon Ads Data for Full-Funnel Attribution
Sponsored Products and Sponsored Brands data isn't structured the same way as your organic Business Reports data. Business Reports rolls up by SKU and date. Ad data rolls up by campaign, ad group, keyword, or target, and it reports "attributed sales," which is Amazon's estimate of what an ad caused, not a settled financial number.
This is where attribution windows trip people up. Amazon defaults to a 7-day attribution window for Sponsored Products and Sponsored Display, and 14 days for Sponsored Brands. If you're comparing "yesterday's ad spend" against "yesterday's attributed sales," you're comparing numbers on different clocks. Sales attributed to yesterday's clicks can keep showing up in the report for a week or two after the fact, which makes daily ACOS look noisier than it actually is.
The fix is to line up ad spend against actual settlement data rather than Amazon's estimated daily spend figures. Estimated spend can shift after the fact too, and if your dashboard locks in the estimate as final, you'll see numbers change later without understanding why.
If your team needs attribution and campaign-level reporting beyond what a general setup covers, that's a deeper build than what fits in a getting-started guide. Trivas's Amazon Ads integration is built specifically for that layer of detail.
Common Setup Mistakes to Avoid
A few mistakes show up over and over in DIY setups, and they're all avoidable.
Blending FBA and FBM fee structures into one cost line. These have genuinely different fee mechanics, and merging them hides which fulfillment method is actually more profitable for a given SKU. Keep them separate.
Ignoring currency conversion on international marketplaces. If you sell on Amazon.ca or Amazon.de alongside .com, and you're not converting to a consistent base currency before rolling numbers up, your "total revenue" figure is just wrong, not approximately wrong, actually wrong.
Refreshing dashboards before settlement data finalizes. We mentioned the 24 to 48 hour lag earlier. If your dashboard refresh runs before that window closes, you'll see fee and payout numbers shift days later, and someone on your team will spend an afternoon trying to figure out why "the dashboard changed."
Treating Brand Analytics data as real-time. It updates weekly. If you're checking search term rank daily and reacting to noise, you're chasing a number that hasn't actually moved.
Getting This Running Without Building It Yourself
Everything above is doable manually. It's also a real engineering project: API authorization, a warehouse layer, SKU mapping logic, settlement timing rules, and ongoing maintenance every time Amazon changes a report format. Most teams underestimate how much of this is upkeep, not setup.
The alternative is connecting to a platform that's already built the pipes. Trivas handles the Seller Central and Amazon Ads API connections, SKU-to-ASIN mapping, and settlement timing automatically on top of Redshift, so you're not reconciling reports by hand every week. For the platform-specific details on what's included, our Amazon integration page covers the setup.
Either path gets you to a working dashboard. One just takes a lot longer to build. If you want more on this kind of setup work as it evolves, it's worth subscribing to our resources for updates, or if you're ready to see it running on your own data, you can start a trial and skip the manual build entirely.
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 Marketing Attribution? A Plain-English Breakdown for DTC Brands
3 min read
Ecommerce Analytics for Toronto and Vancouver Brands: One Dashboard for Shopify, Amazon.ca, and Ad Spend
3 min read
Ecommerce Analytics With Concierge Support: What You're Actually Paying For
.d53b12e5.png&w=3840&q=75 "Trivas.ai")
