AdAce AdsIsolated executor: read before writing, verify after
Between approval and execution, someone may change the campaign in Google Ads or Ads Manager. The executor makes sure AdAce Ads never overwrites such changes blindly.
What it does
The executor is a separate process with its own restricted database role. Right before writing it reads the object from the platform: if the value differs from the approved “before”, it stops with “the account state differs”; if the account already has the “after” value, it records “already applied” without writing.
It writes only the approved fields (for Meta targeting — a patch on the freshly read object), then reads the object back to confirm. Results, codes and timings are visible on Operations.
Why it helps
- No lost changes made by people directly in the ad platforms.
- Proof that each change actually landed.
- Least-privilege design limits damage from any bug.
How to set it up
- Nothing to configure — this is how every write works.
- Open Operations to see each execution with its result.
- If a change was refused because the account differs, review and propose again.
Good to know
- Provider error codes are shown in brackets (for example, a Meta or Google code) without raw provider messages.
- Changes to different ad sets or ads of one campaign are checked independently.
Try it on your own accounts
Create a workspace, connect Google or Meta in a couple of clicks and see your accounts clearly. Changes follow your approvals or the policy you configure.
Create your workspace