Comparing Budget Pacing Across Accounts: A Working Reference
How to put every account on the same pacing yardstick so you can tell underspend from overspend at a glance.
The short version
- Normalize every account to a pace ratio: spend to date / (monthly target x fraction of month elapsed), where 1.0 is on track.
- Ignore day-level spikes; Google paces to the daily budget averaged over the month, so a hot Tuesday is not a problem.
- Act when the ratio stays outside 0.85-1.15 for three straight days between day 7 and 21; damage-control with hard daily caps after day 21.
- Use each account's real budget cycle, not the calendar month, or your yardstick lies right after every reset.
- An account at 1.0 overall can hide a starved brand campaign and a bloated generic one; check pace per campaign when performance slips.
To compare budget pacing across accounts, normalize each account to a single number: spend so far this month divided by the share of the month that has elapsed, expressed against the monthly budget target. An account pacing at 1.0 is exactly on track; above 1.0 is running hot, below 1.0 is underspending. Everything else in this post is about making that number honest across accounts with different budgets, billing cycles, and campaign types.
The one metric that makes accounts comparable
Raw spend tells you nothing across accounts. A $300 day is a crisis in a $5,000/month account and a rounding error in a $150,000/month one. The only way to line accounts up side by side is to convert each to a pace ratio: (spend to date) divided by (monthly budget times fraction of month elapsed).
Work it with real numbers. Suppose it is the 12th of a 30-day month, so 40 percent of the month has passed. An account with a $10,000 monthly target should have spent about $4,000 by now. If it has spent $5,200, its pace ratio is 5200 / 4000 = 1.30, meaning it is 30 percent ahead and will blow the budget by roughly the 23rd if nothing changes. If it has spent $2,800, the ratio is 0.70 and it will finish the month around $7,000, leaving $3,000 on the table.
Build this as a spreadsheet column, one row per account, and you can scan twenty accounts in thirty seconds. Sort by pace ratio descending: the hot accounts float to the top where they belong, the starved ones sink to the bottom, and the quiet middle (0.90 to 1.10) is where you spend no attention at all.
- Pace ratio = spend to date / (monthly target x fraction of month elapsed)
- 1.0 = on track, >1.0 = ahead of budget, <1.0 = behind
- Projected month-end spend = spend to date / fraction of month elapsed
Why the number drifts: how Google actually paces
Google Ads does not spend your daily budget evenly. It spends more on days it predicts higher-value traffic and less on quiet days, and it reconciles over the billing period so that your average daily spend over the month lands at your daily budget. Google retired the old explicit 2x daily overdelivery cap language; today it describes spend as varying day to day, sometimes well above the daily number, averaging out across the month. That means a single hot day is not evidence of a pacing problem. A hot week might be.
This is why you compare at the account or campaign level over a month, not at the day level. A campaign can spend 180 percent of its daily budget on Tuesday and 40 percent on Sunday and still be perfectly paced. If you react to the Tuesday, you will yank budgets on noise and starve the campaign on the days it was trying to capture demand.
The reconciliation also means the back half of a hot month gets throttled automatically only if you are using shared budgets or the campaign hits its own ceiling. Standalone campaign daily budgets do not self-correct toward a monthly target you keep in a spreadsheet. Google is pacing to the daily number; your monthly target is your fiction, so you have to enforce it.
Thresholds: when to touch a budget and when to wait
Do not act on pace ratio alone. Pair it with how much month is left, because the earlier you are, the noisier the projection. Here are the heuristics I use, with the tradeoff stated.
Before day 7 of the month, ignore ratios between 0.7 and 1.4 entirely. The denominator (fraction elapsed) is small, so a couple of heavy or light days swing the ratio hard. Acting now means acting on noise. The exception: a ratio above 2.0 in the first week is real and worth checking for a tracking break or a runaway broad match term.
From day 7 to day 21, act when the ratio sits outside 0.85 to 1.15 for three consecutive days. One day outside the band is normal variance; three days is a trend. For overspenders, the fix is usually trimming daily budgets on the hottest campaigns proportionally so the account projects back to 1.0. For underspenders, first confirm it is a demand or coverage problem (limited by budget status, low impression share) and not a budget you simply set too high.
After day 21, your lever is mostly damage control. An account projecting 1.25 with a week left will overspend by a fixed dollar amount no matter what you do to CPA, so cap daily budgets to the exact remaining dollars divided by remaining days. An account at 0.80 this late rarely recovers full spend without raising bids or widening targeting, both of which change economics, so decide whether hitting the number is worth worse efficiency.
- Days 1-6: ignore 0.7-1.4, investigate only above 2.0
- Days 7-21: act when outside 0.85-1.15 for 3 straight days
- Days 22+: cap daily budget at (remaining budget / remaining days) to control overspend
- Always check "Limited by budget" status before adding budget to an underspender
The failure mode nobody warns you about
The trap is comparing accounts with different billing realities as if they were the same. Google's calendar-month reporting (what you see in the UI date picker set to "This month") is not the same as the billing cycle, and it is definitely not the same as a client's custom monthly budget that runs the 15th to the 14th. If one account's target resets mid-month and your spreadsheet assumes calendar months, its pace ratio will read as a wild overspend right after the reset and a wild underspend right before it. The account is fine; your yardstick is broken.
Second trap: averaging pace across campaigns inside an account hides the real problem. An account can sit at a tidy 1.0 overall while a brand campaign underspends at 0.5 and a generic campaign overspends at 1.5. You are wasting budget on expensive generic clicks and starving your cheapest conversions, and the account-level number tells you everything is fine. When an account looks on-pace but performance is sliding, drop one level and compute pace per campaign.
Third trap: treating "Limited by budget" as a signal to add money. That status only means the campaign could spend more at current bids, not that the extra spend converts. Check the impression share lost to budget and the CPA of recent incremental clicks before you feed it. Sometimes the right move on an underspender is to leave it underspent.
Building the comparison so it survives contact with reality
The durable setup is one sheet, refreshed daily, with these columns per account: monthly target, spend to date, fraction of month elapsed (using that account's real budget cycle, not the calendar), pace ratio, projected month-end spend, and projected dollars over or under. Conditional formatting that turns the ratio red above 1.15 and amber below 0.85 does the triage for you.
Pull spend to date from the Google Ads UI at Campaigns with the date range set to the account's current budget period, or script it against the API if you manage more than a handful of accounts and refuse to copy-paste. The honest limit here: Google does not expose your custom monthly target or a client's off-calendar cycle anywhere in the interface. Those live in your records, and the whole comparison is only as accurate as the target numbers you type in.
One more thing the data cannot tell you: whether an underspending account should be pushed to spend. That is a client and economics question, not a pacing question. Pace comparison tells you which accounts are off track and by how much. It does not tell you whether hitting the number at a worse CPA is a win. Keep those two decisions separate or you will start spending budget just to make a spreadsheet cell turn green.
Questions people also ask
How do I calculate budget pacing for a single account quickly?
Divide spend so far this month by the fraction of the month that has elapsed to get projected month-end spend. Divide that projection by your monthly target to get the pace ratio. A ratio of 1.0 means you will land exactly on budget; 1.2 means you will overspend by 20 percent at the current rate.
Does Google Ads still cap daily spend at 2x the daily budget?
Google no longer describes pacing with an explicit 2x daily cap. Current behavior is that daily spend varies, sometimes well above the daily budget, and averages out to the daily budget over the billing period. That is why you should judge pacing over a month, not a day.
Should I add budget whenever a campaign shows "Limited by budget"?
No. That status only means the campaign could spend more at current bids, not that the extra spend converts profitably. Check impression share lost to budget and the CPA of recent incremental clicks first. Sometimes leaving an account underspent is the correct, more profitable call.
Why does my account look like it is massively overspending right after the month starts?
Early in the month the fraction-elapsed denominator is tiny, so a couple of heavy days swing the pace ratio dramatically. Before day 7, ignore ratios between about 0.7 and 1.4 as noise, and only investigate ratios above 2.0, which usually point to a tracking break or a runaway broad match term.
How do I compare pacing when clients use off-calendar budget cycles?
Use each account's real budget period, not the calendar month, when you compute the fraction elapsed and spend to date. Google's UI does not store your custom cycle or target, so you must track those yourself. Mixing calendar months with a 15th-to-14th cycle produces false overspend right after the reset and false underspend right before it.