Stage campaign changes for human approval

Why use this

1. Advertising changes can look equivalent across platforms while using different budget units, targeting rules or activation states. A review page that shows only proposed copy can conceal the part of the change that commits spend or expands the audience.

2. A campaign-change packet could expose those differences before staging or activation. The account owner could review exact before-and-after settings, confirm the intended spend boundaries and distinguish a paused proposal from an edit that would immediately affect an existing live campaign.

Why an agent / simpler alternative

Useful judgment

Reconcile normalized campaign fields with platform-specific meanings and flag changes that need separate budget or audience review.

Simpler alternative

Use native platform draft tools when the campaign is confined to one account and standard settings.

Unsuitable when

The workflow cannot reliably distinguish drafts, paused campaigns and immediately effective live edits.

Proposed inputs

1. Name

   Campaign baseline

   Owner

   Advertising account owner

   Minimum scope

   Selected campaign IDs, states, budget units and approved audiences

   Quality check

   Mark live campaigns and inherited settings.

2. Name

   Change brief

   Owner

   Campaign manager

   Minimum scope

   Desired edits, permitted spend and approval owners

   Quality check

   Separate creative revisions from targeting and budget changes.

Access and setup — proposed or unknown

Proposed minimum

1. Read-only exported settings and a proposed change diff without ad-account access.

Compatibility unknowns

1. Unknown: current runtime, ad connectors, field normalization and pause-state enforcement.

External actions requiring approval

1. Staging external drafts, live edits, activation, spending changes and expanded data or audience access.

Expected deliverable and review checks

Proposed artifact

Per-platform campaign diff with activation state, budget interpretation and approval checklist.

Critical checks

1. All new-campaign proposals explicitly retain paused status.

2. Existing campaign edits disclose whether effects would be immediate.

Missing output evidence

No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.

Failure signals and proposed responses

1. Signal

   A daily budget is interpreted as a lifetime budget.

   Why it matters

   The proposed commitment can differ materially from the owner's intent.

   Proposed response

   Flag the unit mismatch and require an exact platform-level budget review.

2. Signal

   An edit targets a live campaign instead of its draft.

   Why it matters

   A supposedly reviewable change could affect delivery immediately.

   Proposed response

   Stop the proposal and identify a supported draft or explicit live-edit approval path.

Effort and cost — unknown

Setup work

1. Document field meanings and approval ownership by account.

Ongoing review

1. Inspect staged diffs and reconcile activation status.

Unknowns

1. Unknown: connector charges, platform restrictions and eventual advertising spend.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Two fictional campaign records use different budget units; one change points at a live campaign.

Acceptance checks

1. Flag both budget and state mismatches.

2. Produce no activation-ready action.

Stop conditions

1. Real ad accounts, staging writes or expenditure is required.

Limits

1. The proposed checks and safeguards are editorial recommendations, not evidence of successful execution or permission to act. The linked implementation retains its own observed outcome and approval limits.