Google Ads budget pacing: keep the monthly budget under control

Control needs a plan, a projection, a change rule and a separate internal stop limit. Whether a monthly agency review sees the deviation only after month end depends on its reporting cut-off; a daily pacing run shows it while days remain to correct course. An audit reads only and needs a connected or supplied plan with supporting records.

Which four figures must you never confuse?

Four figures are called “budget” – with different decision-makers, supporting records and effects.

What does “average daily budget” mean?

Google describes it as the amount you want to spend on average per day and campaign. On strong days more can be delivered; Google calls this “overdelivery”. Google documents two named limits for this; according to the English Help they apply to most campaigns:

• Daily spending limit = average daily budget × 2;
• Monthly spending limit = average daily budget × 30.4; it applies while the average daily budget is unchanged.

30.4 is Google’s calculated value for the average number of days per month. The monthly limit applies while the average daily budget is unchanged; any change shifts the calculation to the remaining days. If delivery exceeds the monthly limit, the billed amount stays at the limit; Google carries the difference as an overdelivery credit. Delivered costs and the charged amount are therefore not the same figure – which figure belongs in which record is covered by the guide to media budget and agency fees.

With the pay-per-conversion billing model, daily spending can, according to Google, even exceed twice the daily budget; the monthly spending limit still applies there as well. Both limits apply per budget resource, not per account.

Purely illustrative, freely chosen, with no account observation and no forecast, account currency CHF: with a daily budget of CHF 1,000, the daily limit is CHF 2,000 and the monthly limit CHF 30,400. None of these figures is an approval.

Which budget type suits your period?

Google documents three budget types at campaign level. The shared budget is not a separate billing model but a single average daily budget for several campaigns. The choice changes pacing behaviour fundamentally and belongs at the start.

According to Google, only the total budget has a fixed upper limit, but it is not a general pacing answer: it depends on campaign type, bidding strategy, run time and time of creation, and late changes can make spending uneven. Check availability in the account.

What is the right starting point?

The starting point is the approved business plan, not the account history. Record the source, amount, currency, validity period and approving person. For the monthly value, this order applies:

• monthly plan: the amount directly;
• annual plan: amount ÷ 12, only with genuinely even distribution;
• limited period: amount ÷ included days × 30.4;
• explicit zero: a valid plan with a value of zero, not “no plan”.

Before falling back on account history, the configured plan applies. A workflow override precedes the account plan; when both are absent, the complete account-local cost of the last 90 days divided by three serves as a visibly labelled comparison target – that is not literally three previous calendar months, and it carries no authority. If the data basis is incomplete, no proposal is created: the run records the missing evidence and counts the budget resources that were not assessed instead of inventing a target figure.

How do you calculate the current pace?

Projection = costs to date ÷ completed calendar days × calendar days in the period

Use only completed days in the account time zone; a day in progress distorts the denominator. Expected share and expected spend are the linear plan to that day, not predicted auction delivery.

Illustrative scenario, freely chosen, with no account observation and no forecast – plan period 1–30 June 2026, account time zone Europe/Zurich, account currency CHF, data as at the fully completed 10 June, source: hypothetical sample source “campaign costs”, not an observed account:

• approved period target CHF 40,000, costs to date CHF 13,000 after 10 completed days;
• projection: CHF 13,000 ÷ 10 × 30 = CHF 39,000;
• plan deviation: CHF 39,000 − CHF 40,000 = −CHF 1,000;
• remaining plan CHF 27,000 over 20 days, that is CHF 1,350 per remaining day.

This is a pace indicator, not a forecast of auctions, demand or performance. Days of the week, season, budget changes and learning phases change the trajectory. The embedded calculator at the end of this article calls “deviation” the difference between the observed spend and the linear planned spend to the selected day. The plan deviation shown here instead compares the month-end projection with the full plan. The two figures differ and are labelled separately.

What does the full manual evidence worksheet look like?

Derived values, each with a visible formula and unit:

• Projection = costs to date ÷ completed days × days in the period
• Plan deviation = projection − plan amount
• Remaining daily requirement = (plan amount − spend to date) ÷ remaining days; at period end no days remain, so the value is “N/A”; a negative remainder means the plan is already exceeded, not a negative spending recommendation.
• Sum of unique daily budgets = Σ daily amount per unique budget resource
• possible daily delivery ≈ 2 × the highest daily budget configured for each independent budget resource on that day after edits. This is an applicable planning reference for billed cost, not an upper bound on served cost; switching shared budget resources can restart delivery and must be accounted for separately.
• Monthly spending limit: compute each budget resource from its own history and change dates – unchanged: daily budget × 30.4; after a change: cost incurred to date for that resource + current daily budget × remaining calendar days; then sum comparable resources. A change to one resource does not reset the others. Applies only with a known budget history, otherwise not verifiable. A billing limit, not a delivery or spending cap.

In the manual template, a missing value leaves the affected statement open – you mark it instead of inventing a figure. The embedded form knows only its four fields; if one is missing or out of range, it shows “N/A”.

• An empty mandatory field means unknown: note “not verifiable” and the missing item, never a plausible figure. An explicit zero remains distinguishable. At period end no days remain; the remaining-day requirement is then “N/A”, not the entire sheet “undefined”.
• Different currencies are neither summed nor converted.
• The possible daily delivery comes from Google’s daily limit. It is a planning reference for billed cost – neither an approval nor a guaranteed upper bound on served cost – and is never deducted from the remaining plan.
• Campaigns without a documented daily limit – for example with pay-per-conversion – are marked and excluded instead of being silently multiplied by 2. The monthly spending limit still applies there as well.

How maitiq handles pacing every day

This is how the Budget Pacer workflow works: it does not compute this sheet; it uses the account data available at run time – month-to-date cost divided by today’s day (today.day) against the resolved monthly plan, which differs from this article’s conservative completed-day scenario. At account level the default selects exactly one eligible best or worst campaign; distribution at campaign level is a separate mode. A missing plan alone does not suppress a proposal: a configured workflow override precedes the account plan; when both are absent, the complete account-local cost of the last 90 days divided by three serves as a labelled comparison target – not literally three previous calendar months and with no authority derived from it. The workflow is scheduled daily by default, and the schedule is configurable. You decide; a configured bounded Autopilot rule can also approve and execute, with every execution logged and bounded by guardrails (guarded apply). If the evidence for plan, currency or coverage is missing, the run records the missing evidence instead of inventing a proposal.

How do you count shared budgets correctly?

According to Google, a shared budget is a single average daily budget for several campaigns; budgets that are not fully used are automatically reallocated to campaigns limited by budget. This gives rise to four rules:

1. Count the budget resource once and list the member campaigns alongside it.
2. Calculate limits on the resource, not on each member campaign.
3. Do not treat any member as independently controllable; maitiq’s account ranking excludes members of shared budgets from an individual correction and counts them in. That is maitiq account-ranking behaviour, not a universal prohibition on an operator restructuring budgets.
4. Expect side effects when reassigning: Google adds the budget of a newly added campaign to the shared amount, and a change in the middle of the day then delivers as if the campaign had spent nothing up to the switch.

An account with Performance Max or app campaigns therefore cannot control its period fully through shared budgets.

What to do about underspending?

Do not increase immediately: a higher budget fixes neither missing demand nor a wrong conversion signal. First check a tight bid target, limited or disapproved ads, restrictive location, language or ad schedule settings, unreliable measurement, a planned pause, a shared budget resource and an outdated plan.

Only with reliable measurement does an increase go to a suitable campaign. “Suitable” depends on the mode: CPA for conversion goals, ROAS for value goals, CPC with CTR as a tiebreak only when the account is click-focused (click or hybrid mode). A campaign without positive spend and a robust denominator is excluded rather than ranked.

What to do about overspending?

A projection above target can come from a short surge in demand. Check the change history, the maturity of the measurement window, conversion delay, the campaign role and shared budgets. For any intervention, Google's change logic applies:

• The change does not apply retroactively: for the rest of the month, new daily budget × remaining calendar days applies, plus the costs already incurred.
• For the daily limit, the highest daily budget set on that day counts. Anyone who increases in the morning and lowers in the afternoon keeps the higher limit.
• For a resource’s monthly limit, only the last valid daily budget counts.

Because a day can bill up to twice the amount, a buffer is defensible in the closing days. The maitiq workflows work with configured limits – maximum change per step and daily limits; such a buffer is a planned operating setting, not a universally valid threshold.

Every change is logged: old and new daily value, budget resource, expected effect on the period, reason, approval, verification and rollback point. The approval path is described in the guide to governance and approvals.

What does the Google budget report show – and what does it not?

The budget report shows the monthly spending limit, the forecast and the spend to date. It does not know your internal business plan; you compare its figures with the plan you supplied. Its documented limits are part of the assessment:

• Performance Max is currently not compatible with the budget report.
• It requires a campaign whose period includes the current month.
• Ad schedules are not taken into account in the forecast.
• The report follows Google's billing view, not your period plan.

If the report is missing for part of the account, that is not a balanced pace but missing coverage: flag it and continue working there with the cost history.

How does an internal exposure framework differ?

A period plan says what you want to spend; an internal exposure framework – the internal spending and stop boundary – says when you stop. A controlled start – for example a paid search pilot – includes:

• daily budget per campaign and the sum of unique budget resources;
• a separate authorisation for the entire run time;
• an explicit assumption of possible intraday exposure: for planning purposes around 2 × the highest daily budget configured for each independent budget resource on that day after edits, with the exceptions named above. This is an applicable planning reference for billed cost, not an upper bound on served cost; switching shared budget resources can restart delivery and must be accounted for separately;
• a pessimistic reserve for costs not yet booked up to the next control point;
• a monitoring rhythm with a named person, tested pause access, a written stop rule and a rollback point.

This limit is an authorisation and stop limit, not a provider-side cap. A pause does not apply retroactively; costs already incurred remain owed. If you need a technically hard cap, you must use a Google feature that achieves this and evidence its availability.

Which controls does a large account need?

1. record costs account-locally and in the account currency;
2. version the plan source, approval and budget changes;
3. calculate the projection and the remaining daily requirement with a visible formula;
4. classify the deviation by cause rather than by sign;
5. count budget resources, shared ones once;
6. define the maximum single change and the change frequency in advance;
7. create an evidenced proposal for each decision and have it approved;
8. log the implementation and verify it after an appropriate maturity period;
9. stop rather than keep calculating in the event of a measurement, coverage or exposure error.

A proposing maitiq run chains plan, costs, projection, campaign and the old to new daily budget without changing the account; the process is shown by the read-only Google Ads audit.

Frequently asked questions

Sources and how to read them

All sources are Google Ads Help pages documenting platform features, billing limits and report limits. The CHF figures in this article are freely chosen illustrations, not Google figures; the June cost source is a hypothetical sample source, not an observed account. Information about how maitiq works is available at maitiq.com.

Have maitiq review your specific case.