Google Ads budget pacing: formulas, thresholds and automation

Why pacing goes wrong in the first place

Google Ads budgets are daily, but clients think in months. Google can spend up to twice your average daily budget on a given day when it sees more opportunity, and balances it out so that, across a calendar month, you are not charged more than your average daily budget times 30.4 (Google's monthly charging limit). So a campaign can be perfectly within Google's rules and still land far from the monthly number your client signed off.

Other causes: budget changes mid-month, campaigns paused and re-enabled, seasonality, bid strategy changes, a new competitor, conversion tracking breaking (Smart Bidding then bids blind), and shared budgets across campaigns. Pacing is how you catch these before the month is gone.

The pacing formulas

All of these use complete days: the 1st of the month through yesterday, in the account's time zone. Today's spend is partial and reported with a delay, so including it makes every account look under-paced in the morning.

A worked example

A client has a $3,000 monthly budget in a 30-day month. It is the morning of the 11th, so 10 complete days have elapsed and 20 days remain, today included. Month-to-date spend is $1,240.

• Expected spend to date: $3,000 × 10 ÷ 30 = $1,000.
• Pacing: $1,240 ÷ $1,000 = 124%, over-pacing.
• Run rate: $1,240 ÷ 10 = $124 a day. Projected month-end: $1,240 + $124 × 20 = $3,720, $720 over.
• Required daily budget to land on $3,000: ($3,000 − $1,240) ÷ 20 = $88 a day across the client's campaigns.

Because Google can overspend a daily budget on individual days, set daily budgets slightly under the required figure late in the month if landing exactly matters.

Which thresholds to alert on

A common band is ±15%: flag over-pacing above 115% and under-pacing below 85%. Those are the thresholds MegaMCP's pacing tools use. Tighten the band as the month goes on, since a 20% miss on day 3 is noise and a 20% miss on day 25 is a real overspend.

Pacing across clients and platforms

Native tools pace one platform's campaigns at a time. Agencies budget per client, across Google, Meta, Microsoft and more. That means the useful number is the client's total month-to-date spend across every platform against the client's monthly budget.

MegaMCP's Agency mode does exactly this. On the Portfolio page you set each client's monthly budget, and megamcp_portfolio_pacing sums month-to-date spend across the client's Google Ads, Meta Ads, Microsoft Ads, TikTok, Reddit and Pinterest accounts, then ranks clients worst first with pacing %, projected month-end, the over or under amount and the daily spend needed to land on budget. Different currencies are never added together.

When a client is off, megamcp_propose_client_rebalance drafts one change plan that resets daily campaign budgets across Google Ads, Meta Ads and Microsoft Ads so the month lands on budget, scaling each budget in proportion to today's. You can edit the numbers first; the whole rebalance is approved, rejected or undone as a unit, and spend caps apply. Budgets it can't change (TikTok, Reddit and Pinterest spend, Meta ad-set budgets, shared Microsoft budgets) are held at their current pace in the math.

Automating the morning check

1. Set the monthly budget per client or account.

   Pacing is meaningless without the number you're aiming at. In MegaMCP, set it per client on the Portfolio page.

2. Read pacing on complete days every morning.

   google_ads_budget_pacing, meta_ads_budget_pacing and microsoft_ads_budget_pacing compute month-to-date pacing per campaign in each account's time zone.

3. Alert only when something is off.

   The Morning Pacing and Anomaly Alert workflow checks pacing and yesterday's numbers against a 28-day baseline for every Google Ads, Meta Ads and Microsoft Ads account, and emails only when something is outside the band.

4. Propose the fix, approve it yourself.

   Ask the AI for the required daily budgets and a plan. Budget bumpers stop any change above your caps.

5. Re-check after the change.

   Pacing responds over days, not hours. Look again two or three days later before adjusting further.

If you'd rather start with a spreadsheet, the formulas above are all you need. The value of automating it is that it happens every single morning for every account, including the ones you weren't worried about.

Example prompts

Copy these into Claude, ChatGPT or Cursor with MegaMCP connected. Each lists the tools it typically calls; more are in the prompt library.

• Reads data

  Which clients are furthest from their monthly budget this month? Show pacing %, projected month-end and the daily spend needed to land on budget.

  Tools it calls: megamcp_portfolio_pacing

• Reads data

  Show month-to-date pacing for every enabled campaign in this Google Ads account, worst first.

  Tools it calls: google_ads_budget_pacing

• Proposes a change

  Rebalance Acme's budgets across Google, Meta and Microsoft so the month lands on budget. Show me the plan.

  Tools it calls: megamcp_propose_client_rebalance

  Any change becomes a plan you review and approve. Nothing moves until you do.

• Reads data

  Did any Google Ads campaign spend unusually yesterday compared with its usual day?

  Tools it calls: google_ads_anomalies

• Reads data

  Is Meta over-pacing this month for this account?

  Tools it calls: meta_ads_budget_pacing