Before automating budget changes, define the maximum spend you can accept, the evidence required to make a change, who can approve exceptions and how to stop the automation. A rule that moves money should have limits as clear as the performance target it is trying to reach.
Which spending limits do you need?
- An overall budget for the period, plus limits for each account, campaign, market or client that must stay separate.
- A maximum increase and decrease per action, so one evaluation cannot make an unexpectedly large change.
- A limit on how often changes can happen and a waiting period before the same campaign is evaluated again.
- A reserve or minimum allocation for campaigns whose purpose would otherwise be lost when budget follows short-term results.
Distinguish the budget you enter from the maximum you can be charged. For most Google Ads campaigns, an average daily budget is not a strict daily cap: spend can reach twice that amount on a day, subject to the applicable monthly limit. Check the rules for the campaign type and account before designing a spending control.
When should a rule refuse to act?
- The tracking signal is missing, delayed or materially different from the business's order or lead records.
- There is too little data to support the decision, or the conversion window has not had time to mature.
- A campaign has recently changed budget, creative, audience or objective and the effect is not yet clear.
- A promotion, stock issue or other known event makes the comparison period unsuitable.
- Another rule or operator is already changing the same budget.
How do you choose a useful performance target?
Define the business outcome before choosing a metric. A lead-generation rule should consider lead quality where that information is available. A sales rule should distinguish revenue from margin and new customers from repeat purchases. Optimising an easy-to-count event can otherwise move spend toward outcomes the business does not value.
How should you test a rule?
- Run the logic in observation mode first and record the changes it would have proposed.
- Check those proposals against the agreed budget, reporting delay and known business events.
- Begin with limited scope and a clear owner. Require approval for changes above your chosen threshold.
- Keep a log of the previous value, proposed value, reason, time and outcome of every action.
- Define a stop control and a rollback procedure, then check that both work before expanding the automation.
For an illustrative test, a team might allow only a small increase per review and require human approval above a separate threshold. Choose the actual values from your budget and operating constraints; a fixed percentage recommended for every advertiser would ignore those differences.
Can these checks guarantee better results?
No. They limit operational risk and make decisions easier to review. Performance still depends on the campaign, creative, measurement and market. Review the rule's results periodically, including changes it chose not to make, and retire rules whose assumptions no longer hold.
Put it into practice with Aurora
- Aurora Ads: manage campaigns across your ad accounts
- Aurora Intelligence: review performance before changing budgets
- Aurora Wallet: monitor balances and advertising spend
Sources and further reading
- Google Ads: manage your spend and spending limits
- Google Ads: set and change an average daily budget
- Google Analytics: get started with attribution
Published by Aurora. Platform features and policies can change; check the linked documentation for current details.