The four stops of every change
Step 1: Draft
Your AI describes the change, for example new negative keywords or a lower budget.
Step 2: Preview
Ads Bridge shows exactly what will be sent, with warnings when something looks risky.
Step 3: Test run
Google checks the change without carrying it out. Errors show up here, not in your account.
Step 4: Apply
Only after you approve it. Then the change is made and logged.
How you approve
In apps that show approval cards, such as Claude, the preview appears as a card with three buttons: Test run, Apply and Discard. Only your click applies the change; the AI cannot press the button for you.
In apps without cards, Ads Bridge asks you in a confirmation dialog before anything changes. Changes that cannot be undone ask you to confirm twice.
You can let the AI apply changes after you say yes in the chat instead, with Allow approval in chat in your safety settings. It is off unless you turn it on.
Limits you set
- Daily budget cap. Your AI cannot propose a daily budget above this amount, in your account's currency.
- Bid increase cap. A bid can be raised by at most this percentage in one change.
- Test run required. When this is on, Ads Bridge only ever does test runs and applies nothing, until you turn it off.
- Tag Manager changes. Off by default. While off, your AI can read your containers but not change or publish them.
Rules that are always on
- Two-step apply. A change can only be applied after a test run of exactly that change has passed. You cannot turn this off.
- New campaigns and ads start paused. They spend nothing until you enable them.
- Broad match needs automated bidding. Ads Bridge refuses broad match keywords on campaigns with manual bids, a common way to waste budget.
- Removals ask twice. Removing something cannot be undone, so it needs a second confirmation. Pausing is always offered first.
- Everything is logged. Every test run and every applied change is recorded in your change log.
Your AI can still be wrong
The safeguards stop surprises, not bad ideas. Read each preview before you approve it, the same way you would check a colleague's change.