An approval workflow for changes to live ad accounts

Most expensive mistakes in ad accounts are small edits applied to the wrong thing. A short, boring workflow prevents most of them.

The steps

Propose: one person writes the change and the reason.
Preview: show exactly what will change, on which object, from what to what.
Approve: a second person, or the account owner, says yes.
Apply: send the change with an idempotency key so a retry cannot repeat it.
Read back: fetch the object from the platform and compare it with the intent.
Record: log who did what, when, and what the read-back showed.

Why each step exists

The preview catches wrong targets. Approval catches wrong decisions. The idempotency key catches retries after a timeout. The read-back catches changes a platform quietly modified or rejected.

Where it applies

Budgets, bids, statuses, targeting and anything that spends money. Start new ads paused, and let a person turn them on.

Keep it fast

The workflow should take less effort than the mistake it prevents. Batch related changes into one proposal and approve them together.

6 min read. Last updated 2026-10-07. Examples use made-up numbers.

This guide in numbers

6minutes to read

3terms explained

4sections

16related guides

Use it as a checklist

Tick items as you go. Your ticks stay in this browser only.

Propose: one person writes the change and the reason.
Preview: show exactly what will change, on which object, from what to what.
Approve: a second person, or the account owner, says yes.
Apply: send the change with an idempotency key so a retry cannot repeat it.
Read back: fetch the object from the platform and compare it with the intent.
Record: log who did what, when, and what the read-back showed.

Terms in this guide

Idempotency key Read-back Audit trail

Where this shows up in the product

Ad launcher

Bulk matrices of product, variant, copy, format and audience uploaded paused, then read back.

Approvals and calendar

Clients approve the exact image, copy, placement and date, with revisions and comments in one place.

Change log

Every change with before and after, author, reason, time, API response and what happened next.

MCP for AI assistants

Assistants such as Claude or Codex get the same tools, roles, approvals and log as people.

Keep reading

AI and automation

A safety checklist before an AI assistant touches ad accounts

An assistant that can read your accounts is a convenience. One that can write to them is a decision. This checklist separates the two.

6 min read Creative

How to review a creative test by creative ID

A creative test is only readable if every copy of the same asset can be added up. A creative ID makes that possible.

7 min read Creative

An ad naming convention that survives a team of ten

Good names are a free analytics layer. Bad names mean exporting to a spreadsheet every month to work out what an ad was.

6 min read AI and automation

AI assistants and ad accounts: read, propose, apply

Connecting an assistant to an ad account is easy. Deciding what it may do without asking is the part that needs a rule.

7 min read Operations

A client approval checklist for ad launches

Client approval goes wrong in the same ways: the wrong version is approved, the answer lives in a chat, and nobody can say later what was agreed.

6 min read Operations

How to read back a change to an ad account

A success message from an API only says the request was accepted. A read-back says what the account looks like now.

5 min read Operations

A client offboarding checklist for agencies

A clean exit protects both sides. It also leaves the door open for the client to return.

5 min read Measurement

Budget pacing for ecommerce ad accounts

A budget can fail in two directions: it runs out on the 20th, or a third of it is left on the 30th. Pacing is how you notice early.

6 min read Operations

An SOP library for an ecommerce ad agency

Agencies lose time and client trust when the same task is done three different ways by three people. A small library of written procedures fixes that.

6 min read Operations

Responding to an ad account incident, step by step

An incident is any event that spends money wrongly, stops sales or hides data. The first hour decides how much it costs, so the steps are written before anything goes wrong.

6 min read Operations

Naming QA before launch: check every name before the first spend

Names are how a report finds a row. One misspelled campaign name can split its spend into a second line that nobody reads, so the check runs before launch, not after.

5 min read Operations

Ad launch checklist for ecommerce campaigns, from draft to first day

Launches go wrong in small places: a wrong budget, a missing exclusion, a broken link. One checklist with an owner on each line catches most of them before money is spent.

6 min read Operations

Budget caps and guardrails: stop overspend before the client sees it

A budget cap is a number agreed before launch. A guardrail is the rule that acts when that number is about to break. Both need a named person behind them.

5 min read Operations

A scope change process for agency retainers

A retainer covers an agreed scope. Extra work done without a written change turns into an argument about money, usually at the worst moment.

5 min read Operations

Change requests for client ad accounts: a simple process

Clients ask for changes all the time, often in a quick message. A change request turns each one into a written record with an owner, a reason and a date.