Introduction

Amazon Ads performance stalls when teams disagree on definitions. If ACoS, attribution windows, or reporting ranges differ, the same numbers lead to different decisions. This guide outlines a clean, decision-first dashboard design that keeps your team aligned.

---

Table of Contents

1. Align the foundations
2. Essential KPIs and definitions
3. Change log and decision reasons
4. Alerts and anomaly signals
5. Minimum layout that works
6. Implementation checklist

---

Align the foundations

Before building UI, lock these three decisions:

1. Attribution window: click/view attribution rules are fixed
2. Reporting granularity: daily/weekly/monthly cadence is consistent
3. Scope: SP/SB/SD and campaign/ad group boundaries are explicit

---

Essential KPIs and definitions

Keep KPIs tight and decision-oriented.

• ACoS: ad spend / ad sales
• ROAS: ad sales / ad spend
• TACoS: ad spend / total sales
• CVR: orders / clicks
• CTR: clicks / impressions

Define acceptable ranges per KPI from the business objective, not a universal benchmark. Display the observation count and data status beside any alert.

Calculation and missing-data example

In a hypothetical GBP campaign export, spend is £120, attributed sales £600, clicks 200 and orders 12. ACoS is 20%, ROAS 5.0 and order CVR 6%. If matching total business sales are £1,500, TACoS is 8%; do not add the £600 attributed sales to the £1,500 total.

Aggregate numerators and denominators before calculating ratios. If sales are zero, ACoS is undefined; if the report failed, display missing data. Do not turn either into 0% ACoS. Keep currencies separate unless an explicit exchange-rate method and date are recorded.

Store report type, advertiser type, click/view scope, period, time zone and export timestamp. Label recent data provisional and refresh it after the applicable window and delay. Amazon's conversion definitions vary by metric; the dashboard should preserve those definitions rather than force every report into one window.

---

Change log and decision reasons

Every bid, budget, or targeting change should be logged alongside the reason. This creates repeatable decision patterns.

• Change type: bid/budget/targeting
• Reason: ACoS spike, CVR improvement, seasonality
• Observation window: how long you watch before judging

With a consistent log, post-analysis is faster and decisions are more defensible.

---

Alerts and anomaly signals

Daily operations need high-signal alerts only.

• Clicks spike + CVR drop
• Impression share decline
• Search term CTR collapse
• Bids hitting max caps

Too many alerts leads to fatigue, so prioritize the top 3-5 signals.

---

Minimum layout that works

Start with these five decision views:

1. Top KPI cards (ACoS/ROAS/TACoS/CVR/CTR)
2. Trend chart (7-day and 30-day)
3. Search term performance table
4. Change log timeline
5. Alerts list

---

Implementation checklist

• Attribution window is fixed and documented
• KPI definitions are written and shared
• Change log captures reason + outcome
• Alerts are scoped to high-signal events
• KPI thresholds are agreed internally

---

Wrap-up

The goal of a dashboard is not visual polish but decision consistency. Once definitions and logs are aligned, automation and AI recommendations become far more reliable. Start small, expand only what adds clarity.

If the dashboard exposes weak conversion signals, run the Amazon Listing Score before increasing bids. If the issue is KPI target design, use the ACoS calculator, then compare the broader operating model on the Amazon Ads software comparison page.

Related Arctavia resources

Use these supporting pages to compare Amazon PPC operating models and implementation choices.

• Amazon Ad Rejections: Check Claims, Images and Destinations
• Amazon Ads ACoS Suddenly Increased: What to Check First
• Amazon Ads ML Bid Review: Guardrails Before Aggression
• Amazon PPC Automation: Data, Decisions and Operating Controls
• Amazon PPC Automation Migration Checklist
• Amazon PPC Automation vs Agency: Which Operating Model Fits Better?