Budget pacing alerts: which thresholds catch overspend early without alert fatigue
The pacing alert that catches overspend early without flooding the inbox combines two conditions: pace outside a tolerance band and a dollar gap large enough to matter. Start with a 10% band for large, stable campaigns and 20% for new or small ones, a materiality floor such as the larger of US$250 or 2% of the monthly budget, and a projected month-end over 105% of plan. Add three alerts that do not depend on pace at all: a day spending more than twice the even daily rate, any spend on a campaign with no budget, and a platform that has stopped sending data.
Key takeaways
Why do most pacing alerts fail?
Pacing alerts fail in two directions. Percent-only alerts fire on day 2, when a US$1,000 difference is a 50% swing, and teams learn to ignore them. Dollar-only alerts miss small campaigns that are 40% over plan and stay quiet until month end. Real-time alerts on daily spend trip on Google’s normal behavior: a campaign can spend up to 2 times its average daily budget on a day within its monthly limit, so a high day is not, on its own, a problem.
Which pacing alerts should you set?
These are the starting thresholds we use. Tune them after a month of alerts, and check any single campaign with our PPC budget pacing calculator.
| Alert | Condition | Starting threshold | Why |
|---|---|---|---|
| Off pace | Pace outside the band AND dollar gap above the floor | Band 10% (large, stable) or 20% (new, small, weekday-only); floor = larger of US$250 or 2% of monthly budget | Catches drift that matters, ignores noise |
| Projected overspend | Month-end forecast above plan | 105% of plan, from day 5 onward | The number finance will ask about |
| Projected underspend | Month-end forecast below plan | 90% of plan, from day 7 onward | Unspent budget is pipeline not created |
| Daily spike | One day’s spend above the even daily rate | 2x the even daily rate of the plan | Catches budget changes and broken bid caps the same day |
| Spend with no budget | Campaign spending without a plan | Any amount | New or reactivated campaigns outside the plan |
| Stale data | No new spend data from a platform | More than 24 hours, or 2 missed hourly runs for scripts | Pace judged on old numbers is wrong |
| Budget exhausted early | Spend to date reaches the monthly plan before month end | 95% of plan with more than 3 days left | Time to decide: stop, extend or reallocate |
Bring your funnel numbers to a 30-minute pipeline plan session. We show where spend is leaking against your CRM data and what to fix first.
A worked example with example inputs
Two campaigns on the morning of day 3 of a 30-day month, 2.25 days elapsed. Campaign A has a US$3,000 monthly plan and has spent US$360 against US$225 expected: pace 160%, gap US$135. The floor is the larger of US$250 or 2% of US$3,000, so US$250. No alert: the percent is high but the money is not, and day 3 data is noisy.
Campaign B has a US$90,000 plan and has spent US$7,650 against US$6,750 expected: pace 113%, gap US$900. Its floor is 2% of US$90,000, or US$1,800, so there is still no alert on day 3. On the morning of day 10, with 9.25 days elapsed, if it holds 113% the gap is about US$3,600, above the floor, and the month-end forecast is about US$101,700, above 105% of plan. Both alerts fire, with the daily budget to hit attached. That is the right moment: early enough to fix, late enough to be real.
How often should alerts arrive?
Once a day, at an hour someone acts, listing only campaigns that breach a rule, sorted by dollar impact, with the daily budget that fixes each one. The exceptions are the daily spike and stale data, which are worth a same-day notice in Slack or Teams for large accounts. Real-time alerts on every threshold create noise that teams mute within weeks.
When are Google’s own alerts enough?
Google Ads automated rules can run on a schedule, check a condition and send an email or change a budget; Google suggests minimum and maximum limits in every rule. The budget report shows cost to date and a monthly forecast for campaigns on average daily budgets. For one account, a rule that emails campaigns whose month-to-date cost exceeds a share of plan is a reasonable start. Rules need a plan per campaign written into them, they do not span Microsoft Ads and LinkedIn Ads, and keeping thresholds consistent across many accounts is manual work.
Where Pacing Console fits
Pacing Console pulls Google Ads and Microsoft Ads spend every hour through a script that runs in your own account, or daily when you connect by sign-in; LinkedIn Ads connects with LinkedIn sign-in and syncs daily, with Sync now any time. Each morning, at the hour you choose in your time zone, it emails the campaigns that are over budget, overpacing or underpacing, with the daily budget that fixes each one, and warns when a platform stops sending data. No email is sent when everything is on pace. The tolerance band is yours to set (10% by default), and pace is judged at the hour the data was pulled.
On Pro, the same alerts go to Slack or Microsoft Teams. On Enterprise, guardrails are checked every day, alert owners by email, Slack or Teams, and can queue a budget cap for approval.
Frequently asked questions
What is a good budget pacing tolerance?
Start with 10% either side of expected spend for large, stable campaigns and 20% for new, small or weekday-only campaigns, then tighten after a month of results.
Should pacing alerts use percent or dollars?
Both. Alert when pace is outside the band and the dollar gap is above a floor, such as the larger of US$250 or 2% of the monthly budget. Percent alone fires too early; dollars alone miss small campaigns.
How early in the month should pacing alerts start?
Daily spike, spend with no budget and stale data alerts can run from day 1. Pace and projected month-end alerts work better from about day 5, when a few days of spend make the run rate meaningful.
Can Google Ads send budget alerts?
Yes, through automated rules that check conditions on a schedule and send an email or change a budget. They work inside one Google Ads account and need the plan written into each rule.
Sources
Related service: Paid media. See also pricing and client results.
We run enterprise B2B demand generation for teams in Montreal, Toronto, Ottawa and the United States.
