At a glance
Total advertising cost across all Sponsored Products, Sponsored Brands, Sponsored Display, and DSP campaigns over the window. SUM(cost) in account currency. The denominator under ROAS, the numerator under ACOS, and the budget figure your CFO checks first. Watch for unexpected spend spikes (>2σ above the 30D baseline) which usually mean auto-campaign drift or competitor cost-per-click pressure.
Calculation
Calculated automatically from your Amazon Ads data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A US home-goods seller, same account as the ROAS / ACOS examples. The 30-day window covers 14 Mar 26 to 12 Apr 26.
What’s interesting:
- A 5.5% rise in spend is well within the 2σ window (which on a 5,000 spike). No alert fires; the rise is within normal scaling. Pair with ROAS to confirm: ROAS dropped 8.5% over the same period, so spend up + ROAS down = scaling slightly past the efficient frontier. Watch.
- SP at 76% of spend is normal for a Sponsored-only seller. SB and SD share remained roughly stable. If SD spend were rising disproportionately, it would suggest the merchant is leaning into remarketing without being asked to.
- No DSP commitment yet. DSP requires minimum spend commitments ($35K+ for managed-service, less for self-service). For sellers below that threshold, DSP shows zero, which is correct.
- The 14% rise in SB and SD with only 3% in SP could mean Amazon’s auto-budgeting shifted spend toward the better-converting campaigns last cycle, or that the merchant manually raised SB and SD budgets after a good week. Both are normal; investigate only if ROAS by Campaign shows the rise concentrated in a single drifting campaign.
- What a 2σ spike would look like: A sudden jump to $34,000 in 30D (~33% above baseline). Common causes: a single auto-campaign exploded due to broad-match leakage (open Search Terms immediately); a competitor entered the auction with aggressive bids (CPC Spike Detection); or a budget cap was raised without team awareness.
- Spend up + ROAS up = healthy scaling. Best case.
- Spend up + ROAS flat = clean scaling without efficiency loss. Good.
- Spend up + ROAS down = scaling beyond efficient frontier. Common; watch.
- Spend down + ROAS up = pruned low-quality. Good if intentional.
- Spend up sharply (2σ+) with ROAS flat = budget caps or competitor pressure, not deliberate scaling. Investigate.
- Spend flat + ROAS down = attribution change or external factor. Don’t react before checking ACOS / ROAS reconciliation.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in Amazon Ads Console: Amazon Ads Console > Campaign Manager, sort all campaigns by Cost descending. The total at the foot of the table should match this card to within ~1%. Amazon Ads Console > Reports, choose a 30-day window and the same date range. The Spend column total reconciles directly. Amazon Ads Console > Billing, the invoice view. This is the authoritative source for finance-team reconciliation; this card pulls report-level cost which matches invoiced cost to within ~0.5% (the small drift is invalid-click refunds processed later). Why our number may legitimately differ from Amazon’s invoice:
Cross-connector reconciliation: