At a glance
Pacing check, actual_spend ÷ budget for the current month, with an alert when >90% of the budget is consumed before 80% of the period has elapsed (front-loaded burn). Amazon Advertising budgets sit at three levels: account-level (rare), campaign-level (most common), and portfolio-level (the optional grouping). This card aggregates campaign-level budgets to a synthetic account total and tracks burn rate against month-elapsed.
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, mid-month read on 12 Apr 26 (day 12 of a 30-day month, 40% of period elapsed).
What’s interesting:
- Account-level pacing is healthy at 43% consumed vs 40% elapsed, slightly hot but well within the alert threshold. The non-branded SP campaign is the hot one (50% consumed at 40% elapsed) and would, on its own, exhaust budget around day 24 if the burn rate continued. Worth watching.
- The 90%/80% alert hasn’t fired because total consumption (43%) is below the 90% trigger. The alert would fire if total spend hit ~$31,000 before day 24, suggesting front-loaded waste rather than steady scale.
- Pair with ROAS: if ROAS is holding while non-branded burns hot, the team is intentionally scaling into a high-converting period. If ROAS is dropping, the burn is unintentional and likely auto-campaign drift.
- Theoretical max vs intended spend: the 28,000. At current pacing (37,000 projected for the month), they will exceed intended spend by 30%.
- Front-loaded burn is the danger pattern. >90% consumed at <80% elapsed = the team will run out of budget mid-month and lose impressions. The fix is usually to lower daily caps, not raise total budget, the burn rate is the symptom of auto-campaign drift.
- 40% elapsed + 35-50% consumed = on pace. Healthy.
- 40% elapsed + 50-70% consumed = hot. Watch Total Spend and CPC Trend.
- 40% elapsed + >70% consumed = alert. Likely cause: a daily-budget cap got raised, or auto-campaign is matching new traffic.
- 80% elapsed + <60% consumed = cold. Either the team set caps too high or there isn’t enough demand for the bid.
- Pace flat + ROAS falling = scaling beyond efficient frontier despite normal pacing.
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, the Daily Budget column shows each campaign’s cap; the Spend column shows MTD usage. Sum manually for the account total. Amazon Ads Console > Portfolios, if portfolios are configured, the portfolio-level monthly cap is the more authoritative budget figure. This card uses portfolio caps where set, falling back to daily-cap × days-in-month otherwise. Amazon Ads Console > Recommendations. Amazon often suggests “out-of-budget” warnings on campaigns hitting their daily cap consistently. Why our number may legitimately differ from a manual sum in Amazon Ads Console:
Cross-connector reconciliation:
Known limitations / merchant FAQs
What does “budget” mean in this card? Theoretical-max budget = sum of campaign daily caps × days-in-month, or portfolio-level monthly caps where configured. It is NOT the same as “what the merchant intends to spend”, daily caps are usually set above intended spend to avoid impression loss on high-demand days. Most accounts spend 70-85% of theoretical max. My pacing alert fires every month, but I always end the month at 85% of budget. Should I worry? The alert is structured around front-loading: 90% consumed before 80% elapsed. If you’re consistently hitting 90% by day 24 (80% of 30) but ending the month at 85%, that means days 25-30 are slow. Two diagnoses: (a) Lightning Deal or Prime Day in the first half of the month creates artificial early burn; this is normal and not actionable. (b) A specific high-spending campaign exhausts mid-month; check Overspending Campaigns to confirm. Why doesn’t DSP show in pacing? DSP uses fixed committed-spend agreements with Amazon ($35K+ minimums for managed-service), not daily budget caps. Pacing for DSP is governed by the contract and the campaign flight dates, not by daily budget consumption. This card excludes DSP; manage DSP pacing separately. The 90%/80% alert seems too sensitive, every month I get flagged. Tune the alert in your Vortex IQ settings. The default 90/80 is a strict pacing rule for accounts that need tight cost discipline; for scaling accounts, 95/85 or 100/90 may be more appropriate. The alert structure isconsumption% > X AND elapsed% < Y.
My team raises daily caps mid-month and the card looks healthy again. Is this gaming?
A bit. Raising the cap increases the denominator of ”% consumed”, which makes the pace look slower. It does not actually slow the burn. Pair with Total Spend: if the absolute spend has continued to rise, you’re scaling, not pacing. If absolute spend has plateaued because you hit the new cap too, you’ve solved nothing.
Why does my pacing differ from what Amazon Ads Console shows?
The Console shows per-campaign daily-cap consumption (not month-level pacing). To see month-level pacing in the Console, you’d manually compute MTD-spend ÷ (daily-cap × days-elapsed). This card does that aggregation for you across the account.
Multi-marketplace, can I see global pacing?
Not in a single card. Each Amazon Advertising account is single-currency single-marketplace; pacing is per-account.
What’s the right action when pacing alerts?
Three options in order of preference: (1) Lower daily caps on the offending campaigns (find them via Overspending Campaigns). This is usually the right answer. (2) Pause the offending campaigns and redeploy budget to higher-ROAS lines. (3) Raise the total budget if the burn is on profitable inventory and you can fund it. Most accounts default to (3) and shouldn’t.
My calendar month is a strange one (28 / 31 days), how does the alert handle that?
The “elapsed%” is calendar-aware: day 14 of February is 50% elapsed; day 14 of March is ~45% elapsed. The card adjusts automatically.