What this playbook covers and when to run it
The playbook covers the operating life of programmatic flights bought through Display & Video 360 (DV360Google's enterprise DSP.) and served or measured through Campaign Manager 360 (CM360Ad server and measurement platform.): setting up the flight to match the signed plan, trafficking and launch checks, the daily read of pacing, the weekly review of inventory, deals, safety, audiences, frequency and creative, the monthly reconciliation with the ad server and verification, and the close of each flight. It does not teach bidding, deal types, audiences, trafficking, Floodlight or verification. The programmatic pillar explains how the channel works, the DV360 hub sets out the account hierarchy and the order of a first campaign, and each phase below hands off to the guide or checklist that owns the method.
It is the programmatic counterpart of the paid search account management playbook and the paid social account management playbook, which run the self-serve platforms. Where programmatic is one line in a wider plan, the tutorial on managing a media plan while it runs manages the plan across media; this playbook is the routine inside the programmatic line.
Run it when any of these is true: programmatic spend is checked only when the monthly report arrives; deals are accepted but nobody checks whether they spend; nobody can say how often the same person sees the ads across line items; verification reports are filed rather than read; or each flight starts from a rate card rather than from what the last one cost. Like every playbook in the playbooks library, it is a starting shape. A single advertiser with one always-on campaign may run it in a few hours a week; an agency trading desk with many advertisers will split it across traders, ad operations and analysts.
Roles and responsibilities
- Programmatic trader. Owns the DV360 set-up below the plan: insertion orders, line items, bids, pacing, targeting, inventory sources and caps. Reads pacing daily and makes in-flight changes inside the agreed limits, logging each one.
- Ad operations lead. Owns trafficking in Campaign Manager 360, Floodlight activities, creative assignment and approval status, and the tags sent to each buying platform. Signs off the launch checks before money moves.
- Media planner. Owns the signed plan, the insertion order terms and the change log against the plan. Decides budget moves between line items within the agreed limit and chases make-goods with sellers.
- Analyst. Owns reporting from the DSP and the ad server, the monthly reconciliation with verification, and the post-campaign analysis and cost history.
- Account lead. The advertiser-side or client-side owner of the budget. Approves anything that changes the plan's total, its media mix or a contractual commitment, and reads the post-campaign analysis.
In an agency, the trader, ad operations lead and analyst usually sit on the trading desk, the planner in the media team and the account lead with the client. In a small in-house team one person may hold the trader and ad operations roles; the planner and account lead decisions still need to be separate and written down, because the commonest failure is a trader moving money nobody else agreed to move.
Cadence, inputs and outputs
The rhythm below is a suggested starting point. Adjust it to the size and length of each flight, how much of the budget sits in guaranteed or private deals and how quickly the platform's automated strategies react, not to a calendar that looks tidy.
| Cadence | Owner | Inputs | Outputs |
|---|---|---|---|
| Per flight | Trader, ad operations lead, planner | The signed plan, the insertion order, creatives, Floodlight activities | A structure that mirrors the plan, trafficked placements and a passed launch checklist |
| Daily | Trader | Spend and delivery by insertion order and line item against the flight | Pacing corrections inside the limits, each logged; issues raised to the planner |
| Weekly | Trader, planner | Placement and site reports, deal delivery, verification data, frequency and creative reports | Exclusions or inclusions changed, deals chased, caps and rotation adjusted, a weekly note |
| Monthly | Analyst, planner | DSP reports, ad server counts, verification reports, invoices, the insertion order | A reconciliation with gaps explained and make-goods or credits claimed |
| After each flight | Analyst, planner, account lead | The reconciled delivery, reach and frequency, costs, the change log | A post-campaign analysis and new rows in the cost history |
The daily read stops small drifts from becoming lost flights; the weekly review catches what pacing alone cannot see, such as where the ads ran and how often people saw them; the monthly reconciliation turns the platforms' numbers into ones the business can pay against; and the post-campaign analysis feeds the next plan. Results go to the business through the reporting cadence playbook rather than through a separate programmatic report. The academy capstone on a programmatic operating plan for an adult education college asks you to write this daily, weekly and monthly rhythm, with decision rights, for a team taking buying back from an agency.
The playbook in phases
Set up the flight
Build the structure from the signed plan, not from habit. The DV360 account structure guide explains what the partner, advertiser, campaign, insertion order and line item each decide, and how to lay the tree out so reports read like the media plan. The insertion order's terms come from the deal with the seller: the negotiation and insertion orders guide covers what the order should say about volume, rate, make-goods and cancellation, and the insertion order sign-off checklist is the gate before it is signed. The media planning framework lists the planning decisions behind each line, and the CPM calculator turns a budget into the impression volume it implies.
Traffic and launch
Nothing spends until ad serving is in place and checked. The CM360 trafficking tutorial builds the campaign, sites and placements, creatives and ads, rotation and tags in the order Campaign Manager 360 Help documents, and the Floodlight guide decides which actions become activities, how they count and how long their windows run. The DV360 creatives guide covers hosted and third-party creatives, review by Google and each exchange, and rotation. The DV360 campaign launch checklist is the gate: insertion orders and pacing, deals, brand safety, audiences, frequency and tracking confirmed against the plan before the flight begins. The ad operations lead signs it off.
Watch pacing and delivery daily
Each day, as a starting rhythm, the trader reads spend and delivery by insertion order and line item against the flight. The bidding and pacing guide explains, from Display & Video 360 Help, how pacing modes and rates work at both levels, how an insertion order's pacing can starve a deal line item that shares it, and how to read the troubleshooting view to locate under-delivery. PacingHow fast a campaign spends its budget across the flight compared with the plan. changes are made for a reason and logged. Anything outside the trader's limit, or any line drifting beyond the tolerance the plan set, goes to the planner, following the decision split in the tutorial on managing a media plan while it runs.
Review inventory, deals and safety weekly
Once a week, read where the ads actually ran. The DV360 inventory and deals guide covers inventory sources, accepting and assigning deals, controls on the line item and why an accepted deal so often fails to spend; the deal types guide explains how open auction, private auction (PMPAn invitation-only programmatic auction a publisher runs for selected buyers through a deal ID.), preferred and guaranteed deals differ in access, price and priority. The brand safety and viewability guide covers inclusion and exclusion lists, suitability, pre-bid segmentsVerification applied before the bid: a vendor's segments, checked by the DSP, decline impressions classed as unsafe, unsuitable, unviewable or invalid., post-bid blocking and made-for-advertising inventory, and suggests monitoring first and applying controls once the data shows where inventory fails. The trader changes lists and assignments; the planner chases deals that do not deliver.
Manage audiences, frequency and creative
In the same weekly sitting, read who the ads reached and how often. The DV360 audiences guide explains where each list comes from and why list size is the first thing to read and the last to trust. The guide to reach and frequency across platforms explains how caps stack across campaign, insertion order and line item, and why a DV360 cap does not bound what the same person sees elsewhere; the reach and frequency calculator gives a rough check of FrequencyAverage times a person saw an ad. against reach. Where the right cap is genuinely uncertain, the ad frequency cap test answers it with capped and uncapped cells. Creative rotation and approval status are read per creative, as the creatives guide describes.
Reconcile and verify monthly
Once a month, as a starting rhythm, compare three views of the same delivery. The DV360 reporting guide separates media cost from fees and served from viewable impressions, the CM360 reporting guide gives the ad server's independent count and its verification area, and the media auditing and verification guide reconciles the insertion order, the delivery evidence and the invoice line by line. That guide notes that the Media Rating Council in the United States accredits measurement and verification services against published standards, and that contracts should name accredited sources as the counting basis where they exist. The viewability and attention guide explains what a ViewabilityShare of measured ad impressions that had a real chance to be seen. figure does and does not say, and verification vendors classify invalid trafficAd impressions and clicks not caused by genuine human interest: bots, fraud and accidents. that the contract may exclude. Gaps are explained, and make-goods or credits claimed under the order's terms.
Close the flight and carry the learning
When a flight ends, the analyst writes the post-campaign analysis: delivery against plan line by line, reach and frequency achieved, cost efficiency on verified delivery, and what was learned about creative, placement and timing. Every line then goes into the media cost history on a common basis, so the next plan and the next negotiation start from what this advertiser actually paid and got rather than from a rate card. The account lead reads the analysis before the next flight is planned.
Decisions in flight and who takes them
Most programmatic arguments are about who was allowed to change what. Agree the split before launch, write the limits into the plan and log every change with its reason. The table follows the pattern the in-flight media plan tutorial describes; each team sets its own limits.
| Decision | Who takes it | Evidence needed | Recorded in |
|---|---|---|---|
| Adjust bids, pacing or targeting inside a line item | Trader | Line stays within its budget and role | Change log |
| Block or add placements, sites or apps | Trader, with the planner told in the weekly note | Placement and verification reports | Change log and inclusion or exclusion list version |
| Change a frequency cap | Trader for line items; planner for insertion order or campaign caps | Frequency reports, the plan's reach goal | Change log |
| Move budget between line items with the same role, within the limit | Planner | Pacing and delivery evidence | Change log |
| Chase a deal that does not spend, or claim a make-good | Planner, with the trader's diagnosis | Deal delivery figures, the insertion order's terms | Change log and weekly note |
| Move money between campaigns or objectives, or change the total | Account lead and budget holder | A written case and reforecast | Reallocation note and change log |
Two rules keep the table honest. A change not in the log did not happen, which matters when a reconciliation or a post-campaign analysis tries to explain a step in the numbers. And a decision that needs a higher owner is escalated the day it is found, not held until the weekly review, because programmatic budgets keep spending while people wait. A complaint about where an ad appeared is one such decision, and the tutorial on responding to a brand safety incident takes it from the screenshot to the incident record.
A car subscription service runs its spring flight
Rastevold Car Subscriptions, an invented car subscription service, runs a six-week spring awareness flight of £120,000 through an agency trading desk, split between an open auction insertion order and a private deal with a motoring publisher. On day 5 the daily pacing read shows the open auction line item at 140% of its even schedule while the private deal has spent 12% of its share; the insertion order's even pacing is letting the open auction line take the shared allowance. Under the agreed rule the trader moves the deal into its own insertion order and the planner moves £6,000 within the same role. The week 2 inventory review finds 37 sites with low viewable rates and made-for-advertising signals, which the trader adds to the exclusion list. The monthly reconciliation finds the ad server counting 4% fewer impressions than the DSP; the contract names the ad server, so the invoice follows its count. The post-campaign analysis records the deal's verified cost per thousand, and that figure becomes the cost assumption in the autumn plan.
Measuring the playbook
The playbook works when programmatic spend has no surprises at the end of the month. Operating signals show whether the rhythm holds: whether pacing is read every trading day, whether the weekly review and note happen, whether every change has a log entry, whether each flight passes the launch checklist before money moves, and whether the monthly reconciliation finishes before invoices are approved.
Outcome signals show whether the campaigns are getting better run: how many flights end on budget and on time, how long under-delivering deals go before someone acts, how much spend runs on placements later excluded, how far delivered frequency sits from the plan's intention, the size of the gaps between DSP, ad server and verification counts and how many are resolved, and how many plans start from the cost history rather than a rate card. Report them in the team's existing monthly and quarterly packs, beside the campaign results they support.
Common mistakes
- Reading the dashboard only when the report is due. Pacing problems compound daily. Read spend against the flight every trading day and log what you change.
- Assuming an accepted deal is spending. Deals fail quietly. Check deal delivery each week and diagnose with the troubleshooting figures in order.
- Applying every safety segment on day one. It removes inventory nobody saw and makes a reach shortfall impossible to explain. Monitor first, then apply the controls the data supports.
- Caps set once and forgotten. Caps stack across levels and do not reach other platforms. Read frequency weekly against the plan's reach goal.
- Paying on the seller's count. Name the counting source in the insertion order and reconcile against it every month, with make-goods claimed while they can still run.
- Moving money without a rule. In-flight moves without agreed limits erode trust between trader, planner and client. Agree the split before launch and escalate the same day.
- Closing a flight without a cost history. A finished flight that leaves no record makes the next plan guess. Write the analysis and add every line to the cost history.
