Drafts and approvals
A change requested by an AI is written down as a draft first. You see what would change, Adflitz runs safety checks, and a person decides. Only then is anything sent to the ad platform.
The life of a draft
- 1. Filed. Your assistant (or an Autopilot rule) describes the change: a new campaign, a budget move, a pause. It is stored as a draft in Adflitz. Nothing has been sent to the platform yet.
- 2. Checked. Adflitz compares the draft with the synced account and shows the before and after of every field. It also runs guardrail checks.
- 3. Reviewed. An owner or admin opens it under Approvals, reads the diff, then approves or rejects it. Connections with publish permission can approve through the API, if the project allows it.
- 4. Published. Adflitz re-checks the draft against the latest synced data, then sends the change through the platform's official API and records the result in Activity.
What the guardrails look at
These are the default limits.
| Check | Default |
|---|---|
| Largest budget increase in one change | 50 percent |
| Highest daily budget in a draft | 1,000 in the account currency |
| Operations in one draft | 25 |
| New items start paused | Asked for by default |
| Draft expires if nobody decides | After 7 days |
Each check ends in one of three results. A note is only informational. A warning is shown prominently to the reviewer, for example when a budget drops sharply or a new campaign would go live as soon as it is published. A block stops publishing until the draft is fixed or an owner overrides it. Rules of the platform itself, such as a policy the platform would reject, cannot be overridden.
About paused and live
Most platforms create new campaigns in a paused state unless told otherwise, and Adflitz keeps to that by default: a new campaign is drafted as paused, so approving it does not start spending by itself. You then turn it on, as a separate approved change. That is a default, not a promise the system makes for every draft. If a draft asks for something to go live, the reviewer gets a warning. The real safeguard is the approval step: nothing reaches your ad account without a person, or a rule you set up yourself, signing it off.
Reviewing well
- Read the summary first, then the before and after table. The summary is written by the assistant, the table is computed by Adflitz.
- Look at warnings before approving, even when the status is green.
- Reject with a reason. The reason is added to the draft and your assistant can read it when it tries again.
- One draft changes one platform. If an assistant mixes several, ask it to split the work into one draft per platform.
Next
Questions about connecting your AI or your ad accounts? Write to contact@adflitz.com or open the support page.