Campaign Staging

Draft first.
GAM next.

Create a CampaignDocument in draft status, preview the planned mutations and deploy to GAM only after explicit validation.

draft TTL

writes to the draft

Plan

before deploy

Token

confirmation

Features

What you can do

The draft holds the brief, the targeting and the creative groups before any mutation on Google Ad Manager.

Every draft has a validity window, which avoids deploying an old intent onto inventory that has changed.

The dry-run returns the planned Orders, Line Items and LICAs, with credit cost and irreversible risks before execution.

Deployment consumes a token tied to the validated plan. An expired or already consumed token is refused.

The same CampaignPipeline runs staging drafts and display creations, which reduces gaps between preview and execution.

Preview and confirmed execution are logged so the operator can review who validated what.

Real execution

campaign-staging.log

$ campaign(action='create_draft', name='Q3 Acme')

→ CampaignDocument draft created — expires in 7 days

$ campaign(action='deploy', dryRun=true, jobId='job_8b2a')

ExecutionPlan: 1 Order + 3 LineItems + 3 LICAs

estimatedCost: 5 credits | confirmationToken: tok_9c3f

$ campaign(action='deploy', confirmationToken='tok_9c3f')

✓ Campaign deployed — Order #789012

Campaign Staging

5 free credits. No credit card required.