How to Build an Amazon PPC Reporting Dashboard That Drives Decisions

An Amazon PPC reporting dashboard should answer three questions in under a minute: are ads profitable, is the business growing, and where should I look next. That means a small set of KPIs (spend, ad sales, ACoS, TACoS, total sales, orders, CPC, conversion rate), shown as trends against targets, and broken out by product and campaign type so a problem can be traced to its source.

What a dashboard is for (and what it is not)

The Amazon Ads console already shows every number. A dashboard's job is to remove most of them. It should show the few metrics you act on, compared with a target or a prior period, and make the outliers obvious. If you open your dashboard and still need to export three reports to know what to do, it is too thin. If it has 40 columns, it is too thick.

The core KPIs

If you only add one non-ads number, make it total sales so you can see TACoS. The TACoS calculator shows the math, and what TACoS means explains why it is the best single measure of whether ads are helping the whole business.

Segments that make the dashboard useful

Account-level totals hide almost everything. Break the core KPIs out by:

• Product (parent ASIN or product line). Each has a different margin and target.
• Ad type: Sponsored Products, Sponsored Brands, Sponsored Display. They use different attribution windows, so do not blend them blindly.
• Intent: branded, non-branded, competitor, and auto or research. Branded campaigns usually run a much lower ACoS and can make the account look healthier than it is. See branded vs non-branded keywords.
• Marketplace, if you sell in more than one.

Consistent campaign naming conventions make this segmentation possible. If a campaign name includes the product, ad type and intent, a spreadsheet formula or pivot can group it automatically.

Data sources and how to connect them

1. Amazon Ads console reports: schedule the campaign, targeting, and search term reports weekly by email, or pull them through the Amazon Ads API.
2. Seller Central Business Reports: the Detail Page Sales and Traffic by Child Item report gives total sales and sessions per ASIN.
3. Your cost data: COGS, fees and shipping per SKU, kept in a sheet you update when costs change.
4. A change log: dates and descriptions of major changes, so you can annotate the trend lines.

Spreadsheets work fine for one brand. Paste the weekly exports into raw-data tabs, and build the dashboard tab from formulas. If you want this pulled automatically, the Amazon Ads API guide explains what access involves, or a PPC tool can handle it for you.

Sample weekly dashboard layout

Top row: four headline tiles. Spend (with month-to-date pacing), ad sales, ACoS vs target, TACoS. Each tile shows this week, last week and the change.

Second row: two charts. Ad sales and total sales as lines over 12 weeks; ACoS and TACoS as lines over the same period.

Third row: a product table, one row per product.

Bottom row: the top 10 targets by spend with ACoS, and the top 10 wasted search terms (spend with no orders) for the last 30 days. These are your to-do list.

Choosing date ranges and comparisons

The same data can tell different stories depending on the window. A few conventions keep your dashboard honest.

• Use complete weeks (for example Sunday to Saturday) so each period has the same mix of weekdays and weekends.
• Compare week over week for operational decisions and the same week last year for seasonal products. A drop in January after a strong December is usually normal.
• Show a trailing 4-week average beside weekly numbers. It smooths out noise from a single big order or a short stockout.
• Mark the most recent few days as provisional. Sales attributed to ads keep arriving for days after a click, so the newest week will look slightly worse than it will end up.
• Keep the time zone consistent. The Ads console reports in the marketplace time zone; make sure your Business Reports pulls line up.

Building it in a spreadsheet: a quick recipe

1. Create raw tabs named Ads_Campaign, Ads_Targeting, Ads_SearchTerm and Business_Report. Paste each week's export at the bottom, keeping the header row once.
2. Add a helper column to Ads_Campaign that extracts product and intent from the campaign name, for example with SPLIT or REGEXEXTRACT on your naming pattern.
3. Build a Summary tab with SUMIFS for spend, sales and orders by week, product and intent. Calculate ACoS, TACoS and conversion rate from those sums, never by averaging percentages.
4. Add a Targets tab with break-even and target ACoS per product, and pull those into the Summary with a lookup.
5. Use conditional formatting to color the Flag column based on the rules below.
6. Chart the Summary tab, not the raw tabs, so charts stay fast as data grows.

Rules for flags

• ACoS more than 20% above target with at least $100 spend for the week: flag red.
• ACoS more than 30% below target and campaigns limited by budget or low impression share: flag as room to scale.
• Total sales down more than 10% week over week: flag and check stock, Buy Box and pricing.
• CPC up more than 15% with flat conversion: check for new competitors or bid changes.

Dashboards for agencies and clients

If you report to a client or a boss, lead with business outcomes: total sales, TACoS and profit after ads. Put ACoS and keyword detail lower down. Include a short written summary of what changed and what is next. The client reporting guide covers what clients actually read.

Common dashboard mistakes

• Using the last 1 to 3 days. Attributed sales lag, so recent ACoS looks worse than it will end up.
• Blending ad types with different attribution windows into one ACoS without labeling it.
• No targets. A number without a target or prior period cannot tell you whether to act.
• No total sales. Without it you cannot see TACoS or whether ads are lifting organic sales.
• Too many metrics. If a number never changes a decision, remove it.

FAQ