Batch approval of ad changes: all or nothing for Google Ads

What it does

Think of changes that depend on each other: pause the old ad and enable the new one; cut the budget of one campaign and raise another by the same amount; add new keywords together with the negatives that keep them clean; switch a landing page and update the ad that promises it. Approve them one by one and sooner or later something fails, such as a removed ad group or a text over the limit, and you are left with half a plan: both ads off, both budgets up, keywords live without their negatives. A partial result is often worse than no change at all.

Engineers know this pattern from databases: a set of operations either all succeed or all roll back. The Google Ads API itself treats several operations in one request as atomic by default and accepts partial success only when asked explicitly. In everyday management, separate edits rarely get that guarantee, so a practical substitute is to check every change first and go ahead only when all of them pass. Group changes by intent, keep each batch small enough to read carefully, and write reasons that make it clear to the approver why the pieces belong together.

Platforms differ here. Google offers a validate-only mode, so a change can be checked in full without being written. For Meta, the reliable check in this workflow is the execution itself: problems appear when the change runs. In a mixed batch the all-or-nothing rule can therefore cover only the Google part. If a coordinated plan spans both platforms, put the Google changes through the strict gate, approve the Meta changes knowing they are checked at run time, and watch the results until each change is confirmed.

AdAce Ads offers batch approval with the option “approve only if all Google changes pass”. Before approval, every Google change in the batch is checked with Google's validate-only mode. If any of them would be rejected, or the account no longer matches what a proposal expects, none of the batch is approved. Stale proposals can be rebuilt with “Create the same again”. Approval needs your password and second factor; each approved change then runs separately with read-before-write and is visible on “Operations”, while Meta changes are checked when they run.

Why it helps

• Coordinated changes do not land half-applied because of a Google error.
• One approval with password and second factor covers the whole batch.
• Stale proposals stop the batch instead of overwriting newer edits.
• The rules are explicit: Google is checked up front, Meta when it runs.

How to set it up

1. Prepare the related proposals, each with a clear reason.
2. Open “Approvals” and select the proposals for batch approval.
3. Turn on “approve only if all Google changes pass”.
4. Confirm with your password and second factor.
5. If the batch is not approved, fix the failing proposal or rebuild it with “Create the same again”, then try again.
6. Follow the execution on “Operations”.

Good to know