The paused-draft workflow is the single best trick in agent-run advertising, and it fits in a sentence: the agent builds the campaign completely - structure, targeting, creatives, budgets, tracking - but every entity lands in a paused state, so the human contribution collapses to reading finished work and pressing go. Nothing can spend until the click; nothing about the build waits for a meeting. This playbook is the workflow end to end: the brief, the assembly, the review protocol that takes minutes, and the graduation path for teams that earn it.
The pattern in one paragraph
A mission receives a campaign objective, gathers its evidence, and then creates real entities in the real ad account - campaigns, ad sets, ads, with naming conventions, UTMs and budgets - every one of them paused. The platform's own state machine is the safety: a paused campaign is unspendable however wrong it might be, which converts "can we trust the agent in the ad account" from a philosophy question into a mechanical one. The pattern is the advertising instance of the approval-gate principle - the parked artifact is the real artifact - implemented with the platform's native pause instead of a queue.
Why it works: review beats production
Campaign production is hours of structured drudgery: naming, duplication, targeting entry, budget arithmetic, UTM discipline, creative uploads. Campaign review is minutes of judgment: is the money right, is the audience right, does the message match the angle. The workflow moves the drudgery to the mission and concentrates the human entirely on judgment - which is both the scarce input and the one that was being shortchanged when the same person did both. Teams running the pattern describe the same shift: throughput stops being limited by who has an afternoon free, and starts being limited by review attention - a much better bottleneck, because it scales with a rota instead of a hiring plan.
Step one: the brief with evidence attached
The mission starts from a brief that names the objective, the constraint envelope (total budget, dates, platforms) and the evidence sources: demand sizing from the AI advertising operating loop's pricing stage, the open angle from the angle map, audience definitions inheriting the executable ideal customer profile. The assembled draft will carry this evidence forward - each ad set annotated with why it exists, each budget with the math behind it - because a reviewable campaign is one whose reasoning rides along.
Step two: assembly, everything paused
The mission builds the full tree: campaign objectives and budgets; ad sets with targeting, placements and bids; ads with creatives rendered to placement specs by the Design agent; naming per your convention; UTMs per your scheme; every entity paused. Two disciplines matter in assembly. Completeness: a draft missing its tracking or its naming is not reviewable, it is homework. And one-variable structure where the campaign is a test - the creative testing cadence depends on drafts that isolate what they claim to measure.
Step three: the review protocol
| Point | Question |
|---|---|
| Money | Budgets, bids and dates match the envelope; daily totals sum right |
| Audience | Targeting matches the ICP; exclusions applied; no overlap traps |
| Message | Creatives carry the intended angle; claims are ones we make |
| Measurement | Tracking, UTMs and conversion events wired; test variable isolated |
| Mechanics | Naming, placements, schedules per convention |
Five points, on finished work, in the platform itself - edits happen directly on the draft, which beats annotating documents and eliminates the translation loss where "make it punchier" becomes something nobody intended. When the five points pass, launch is the un-pause. The protocol is also the training loop: recurring edit patterns feed back into the brief, and drafts converge on launchable-as-built.
Step four: launch, watch, graduate
Post-launch, the standing missions take over - the audits and diffs from the PPC audit anatomy - and the workflow offers a narrow graduation path per the autonomy ladder: campaign types that recur with identical structure (the weekly budget refresh, the monthly creative rotation into proven slots) can earn spot-check review after a clean record. The boundary worth keeping bright: net-new campaigns - new audiences, new angles, new offers - stay fully reviewed regardless of track record, because novelty is precisely where judgment earns its keep.
The working checklist
Frequently asked questions
What is a paused-draft campaign?
A campaign an agent builds completely - structure, targeting, creatives, budgets, tracking - with every entity created in a paused state, so it cannot spend until a human reviews the finished work and un-pauses it.
Why is this safer than approval documents?
The safety is platform state, not process: paused entities are unspendable by construction, and the reviewed artifact is the exact artifact that launches - no translation between a doc and the build.
How long should review take?
Minutes: five points - money, audience, message, measurement, mechanics - read against finished work in the platform, with edits made directly on the draft.
Can any campaigns skip review eventually?
Only structurally recurring types with clean records - budget refreshes, rotations into proven slots - and only to spot-check status. Net-new campaigns stay fully reviewed regardless of history.
What does the agent need to build drafts?
Account access with create-paused permissions, your naming and UTM conventions, the budget envelope, and the evidence inputs: demand pricing, the angle map, and audience definitions from the executable ICP.
Sources
Every playbook on this blog ships as a runnable mission.
Open a workspace and the playbook library is waiting - describe the outcome and the agents carry it end to end, on your plan's monthly credits.