Google Ads changes that are validated before they are written

Most AI tools connect with read only access and tell you what to do. Campanior applies changes to the account, after first putting them through a dry run.

Applies changes, not just advice
Dry run before every write
Per account limits and audit trail

The problem

Letting a tool touch a client account is a trust decision. A wrong bid or a wrong budget costs real money within hours, and there is no undo button.

That is why every change here goes through a dry run first. Google checks it without applying it and returns exactly what would break. Only if it comes back clean is it written to the account.

How it works

  1. Change plan

    Proposed actions are collected into a plan you read before approving anything.

  2. Dry run

    The plan is sent to Google to be checked without being applied. No change touches the account at this stage.

  3. Isolate problems

    Rejected operations are removed and the rest are retried, so one bad operation does not block the whole plan.

  4. Write

    The clean set is written to the account. The result is logged with everything that changed.

The guarantees before every write

These are not interface messages. They are behaviour that runs on every change, before it touches the account.

Dry runEvery change is first checked by Google without being applied. If something is wrong, we learn it before it is written
All or nothingThe account is never left half changed
Error isolationOne bad action does not block the whole plan. It is removed and the rest proceeds
Per account limitsBudget changes pass through limits you define
Audit trailEvery write is recorded with time, user and outcome
If a change fails the check it is not written, and you are told which one and why. There is no silent downgrade.

What it includes

Safe subset

When part of a plan is rejected, the remainder still runs instead of everything being cancelled.

Change log

Every write is recorded with time, user and outcome.

Budget controls

Budget changes pass through limits you set per account.

MCC support

Work through a manager account with correct per client isolation.

Frequently asked questions

What does the dry run mean in practice?
We send the change to Google and ask it to check without applying it. If something is wrong we learn it before your client’s account is touched. It is the same safety net a developer uses before shipping to production.
Can the AI change budgets on its own?
Not without approval. The plan is presented, you approve, and only then does validation and writing begin.
What happens when Google changes API version?
The version is configured in one place and updated centrally, with nothing to change on your side.

See a change plan without applying it

Connect an account, let Campanior propose, and stop at the dry run step.