Change a budget or bid safely
How a budget or bid edit is staged, reviewed and applied — the magnitude chips, the frozen money guards, and why nothing reaches Google until you press Apply.
Zyan treats paid spend as the one thing it will not touch on its own. You stage a change, you read it back in a review sheet, and you press Apply. Between those steps sit frozen safety ceilings that refuse a change large enough to look like a mistake — and they refuse it twice, once in the sheet and once at the server.
Before you start
Staging and applying ad changes is owner work, on a connected provider account. Google budgets can be staged inline from the Ad Manager list.
Stage the edit
Inline on a campaign row
Staged-changes bar
Collects the whole set
Review sheet
Before and after, row by row
Money guards
A failing row starts excluded
Apply
One campaign at a time
Stage a change
Edit a daily budget inline on a Google campaign row
In the GrowthAd ManagerGoogle Ads list. It must be a positive dollar amount, and the edit is staged, not applied.
Watch the staged-changes bar appear
It sits at the bottom of the list and says what it is: Nothing applied until you review it.
Stage as many changes as you need
They collect in the same set.
Open the review sheet
Titled Review and apply staged changes.
Read every row
Each row shows the action type, the value before, the value after, and a magnitude chip if the change is large. The sheet's subtitle is the whole policy in one sentence: You are approving this list yourself. No rule decides anything here, and nothing reaches Google until you press Apply.
Untick anything you do not want in this batch. Rows that fail a money guard start excluded — you can force one in, but it will not help.
The money guards
These ceilings are frozen. They are the same numbers in the review sheet and in the server-side preflight, so a chip can never disagree with what the server will decide.
| Change | Verdict | Threshold |
|---|---|---|
| Daily budget above $10,000/day | Fail | Absolute ceiling, regardless of the current budget |
| Daily budget more than 10× the current budget and above $200/day | Fail | The floor exists so a small campaign can still step up |
| Daily budget more than 3× the current budget | Warn | The chip shows the multiple, for example 4.2× current daily budget |
| Daily budget of zero or a non-number | Fail | Daily budget must be a positive dollar amount |
| CPC bid above $100 | Fail | Almost certainly a units error |
| CPC bid above $50 | Warn | Allowed, but flagged |
Forcing in a failed row does not work
The server-side preflight applies the same thresholds. Ticking an excluded row back in gets you a rejection a second later instead of a refusal a second earlier. If the change is genuinely intended, step it up over several smaller edits instead — each one re-bases the multiplier against the new current budget.
A 10× jump is usually a units mistake
The absolute $10,000/day ceiling exists to catch amounts entered in the wrong units. Before you split a large increase into steps, check you have not typed cents as dollars.
Apply
Click Apply N changes. Changes are sent one campaign at a time, in sequence, so two campaigns sharing a budget cannot collide.
Leaving the sheet does not cancel what was already sent
Apply is not a single atomic transaction across the batch. Once a row has gone to the provider, closing the sheet does not recall it. If you need to stop mid-batch, deal with what has already landed at the provider.
Discard staged changes throws away the entire set without sending anything.
Meta is approve-or-reject only
Meta ad changes follow a stricter path than Google's staged edits.
| Rule | What it means for you |
|---|---|
| Approve or reject | There is no auto-execute path for a Meta ad mutation |
| Dispatched exactly once | The money request is never retried automatically |
| Approvals expire after 24 hours | An approval you leave sitting overnight goes stale |
The Meta auto-approve rules card is dormant
The card lets you create and store rules so your preferences survive, but nothing evaluates them. Every Meta agent action still requires a manual approval. Do not build a process that assumes a rule will act while you are away.
What the AI agents may and may not do
The Ads Agent and Portfolio Agent propose changes. A proposal is not a change. Every campaign action needs an owner approval — in chat, or through this review sheet. There is no scheduled optimisation loop running against your spend by default.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| A row is excluded and says it exceeds a money guard | The change is above $10,000/day, more than 10× current and above the $200/day floor, or a CPC above $100 | Lower it, or step it up over several smaller edits |
| You forced a failed row in and Apply reported an error | The server applies the same guards | Not a bug. Use smaller steps |
| A change shows a warn chip but applies fine | Warn is informational — above 3× budget, or a CPC above $50 | Confirm the number is right, then apply |
| You closed the sheet mid-apply and some changes landed | Rows are sent sequentially, not atomically | Check the provider for what was applied |
| Daily budget must be a positive dollar amount | Zero, blank or a non-numeric value | Enter a positive amount |
| Staged edits vanished | Discard staged changes was used | Stage them again; discard sends nothing |
| A Meta approval no longer works | Meta approvals expire after 24 hours | Have the agent re-propose it |