What this template is for
Fill a build sheet whenever a DV360 campaign is built or rebuilt, a new insertion order is added for a new budget line, or a structural change splits or merges line items. Routine optimisation inside a live campaign, such as a bid change or a new exclusion, belongs in the campaign's change log instead.
The sheet sits between documents that already exist. Above it, the media plan sets the audience, budget by period, flighting and the reach and frequency the campaign is meant to deliver; the sheet copies those rather than deciding them. The DV360 hub gives a first campaign in order, and the account structure guide explains what each level decides; the sheet follows the same order. Beside it, the insertion order sign-off checklist checks the media order with a publisher or seller, and after the build the DV360 campaign launch checklist verifies budgets, dates, deals, brand safety, audiences, caps and tracking against the signed plan. Once live, the programmatic campaign management playbook runs the daily and weekly routines. The search campaign build sheet and the paid social campaign build sheet do the same job for search and paid social. None of them is the row-by-row record a trader fills before anything exists in DV360.
The sheet earns its place on review. Most programmatic build errors are invisible from the campaign overview: a deal line item starved by an open-auction sibling in the same insertion order, an unlabelled-content exclusion that blocks the publisher the deal was bought for, a line item missing the creative sizes its inventory sends, a strategy optimising to a Floodlight activity that counts page views. On a sheet they are a row a reviewer can read.
The template
Copy the table into a spreadsheet. The cover tab carries the campaign-level fields; insertion orders and line items become their own tabs, one row per insertion order and one row per line item, with the inventory, audience, bidding, brand-safety and creative columns repeated on every line item row.
| Field | What to write |
|---|---|
| Campaign and goal | The campaign, its goal and planned flight, and the media plan line it descends from |
| Insertion orders | Each insertion order with its budget, flight dates, pacing and the plan line it carries |
| Line items | Each line item with its type, the targeting it holds and why it is separate from its neighbours |
| Inventory and deals | Open auction, private deals or guaranteed buys per line item, with each deal's identifier and status |
| Audiences and exclusions | First-party, Google and third-party audiences per line item, their sources and fees, and the exclusions |
| Bidding and frequency | Fixed or automated bidding, the goal and any constraint, and the frequency caps at each level |
| Brand safety and verification | Exclusions, suitability settings and the verification used, with who reads it |
| Creatives | Each creative, its format, whether hosted or a third-party tag, and the line items it is assigned to |
| Conversion tags | The Floodlight activities the campaign optimises to and reports on, and where each fires |
| Trafficking | Placements, ads and tags trafficked through the ad server, and who checks them before launch |
| Naming and reporting | Names from the convention at every level, and the reports and reconciliation the build must support |
Add a sign-off line at the foot of the cover tab: the trader who built the sheet, the reviewer, the review date and the launch date. Keep the platform IDs in a column beside each name once objects exist, because names change and IDs do not.
How to fill each section
Campaign and goal
Write the campaign name, the goal and KPIA metric tied directly to an objective. with its target, the planned spend and the planned dates, and the line of the media plan the campaign comes from. The account structure guide treats the campaign as a folder with a label: one objective, one period, one planning owner. Its goal and KPI are references for the people running it and do not bid, so write what the plan promised, not what a strategy will optimise. Note the advertiser-level settings the build assumes, such as currency, time zone, the Campaign Manager 360 link and the brand-safety defaults, because a wrong one cannot be fixed at campaign level.
Insertion orders
One row per insertion order, each carrying one budget line of the plan: budget and any budget segments, flight dates, pacing mode and rate, performance goal and any insertion-order-level frequency cap or optimisation. The bidding and pacing guide explains how an insertion order's pacing throttles its line items and why a deal can be starved by an open-auction sibling; if a deal needs protecting, the sheet is where it gets its own insertion order or an explicit budget share. Every insertion order should be a line on the plan that somebody has agreed to spend, because that is what pacing reports and invoices are reconciled against.
Line items
One row per line item: its type, its budget share, the targeting it holds and, in a short phrase, why it is separate from its neighbours. The account structure guide gives the test: one line item per combination that needs its own budget, bid or report line. Prospecting and remarketing are separate; a deal and the open auction are separate; two creative sizes are not. If the reason column reads "to see it in reports" for every row, check whether the plan really needs that many, because thin line items give automated strategies little to learn from.
Inventory and deals
For each line item, record the inventory source: open auction with the exchanges in scope, a private auction or preferred dealA programmatic deal giving one buyer a first look at eligible impressions at a fixed, agreed price before the auction, with no volume guarantee., a programmatic guaranteed deal, or a package. For each deal, record the publisher, the deal type, the deal ID, the agreed price basis and dates, and its status as seen in DV360. The inventory and deals guide explains that acceptance makes a deal available but only assignment makes it spend, that a guaranteed deal needs a dedicated line item, and that one line item per deal keeps each publisher's delivery readable. A PMPAn invitation-only programmatic auction a publisher runs for selected buyers through a deal ID. deal belongs on its own row even when the platform would allow it beside other sources.
Audiences and exclusions
List the audiences on each line item by source: first-party lists built from Floodlight or uploads, Google audiences and third-party segments, with any data fee per segment. Then list the exclusions, starting with the advertiser's own converters on every prospecting line item. The DV360 audiences guide explains combined audiences, data fees shown separately from media, and the consent and identity limits that shrink every list. Put inclusions and exclusions side by side on the row, so a reviewer reads both together.
Bidding and frequency
For each line item, write fixed or automated bidding; for automated, the goal and any constraint or target; for fixed, the bid basis. Then write the FrequencyAverage times a person saw an ad. caps at every level where one is set: campaign, insertion order and line item. The bidding and pacing guide explains that caps at each level are enforced together, that fixed bids suit deals and new inventory, and that each strategy change restarts learning. Take the cap values and the bid basis from the plan, not from habit: the reach and frequency calculator helps check that the caps and budget are consistent with the reach the plan expects, and the CPM calculator turns a budget and bid into the impression volume the targeting must supply.
Brand safety and verification
Record the brand-safety layer per line item: content label exclusions, sensitive category exclusions, keyword exclusions, inclusion or exclusion lists, authorised-seller settings, any ViewabilityShare of measured ad impressions that had a real chance to be seen. targeting and any pre-bid segments from a verification vendor. Then record the post-bid verification used and the person who reads it. The brand safety and viewability guide sets out the controls and their trade-offs, and notes that the Media Rating Council defines a viewable impression, with the thresholds in the MRC's guidelines. Check every deal line item's layer against the publisher's actual inventory rather than copying the prospecting defaults; Brand SafetyControls that keep ads away from content that would harm the advertiser's reputation. exclusions apply to deals too. Each setting in this section should trace to a line of the brand's written policy, which the guide to writing a brand suitability policy shows how to draft.
Creatives
One row per creative: name, format and size, hosted or third-party tag, landing page, dates and the line items it is assigned to. The DV360 creatives guide explains hosted creatives against CM360Ad server and measurement platform. tags, the sync between linked advertisers, rotation settings and review. Cross-check each line item against the sizes its inventory sends, since a line item does not bid where it has nothing to show, and note the rotation setting where a creative test is planned.
Conversion tags
List the Floodlight activities the campaign optimises to and those it only reports on, each with its group, counter or sales type, counting method and the page or event where it fires. The Floodlight tags guide explains activity groups, counting methods and how sales tags deduplicate repeat loads. An automated strategy is only as good as the activity it is told to chase, so name the activity on each line item row that uses it, and confirm it is receiving test firings before the build starts.
Trafficking
Where Campaign Manager 360 serves the ads, record the campaign, the placements and the ads in the ad server, the default ad for each placement, the trackers added and who checks them before launch. The trafficking workflow tutorial gives the sequence and notes that placements for a linked DV360Google's enterprise DSP. advertiser arrive by sync, so no tags are sent for them. The sheet records which route each creative takes and who owns the launch-day check from both ends.
Naming and reporting
Write the name of every object from the convention: the campaign for objective and period, the insertion order for channel and budget line, the line item for tactic, inventory, audience and format. The UTM and naming conventions template holds the house rules. Then list the reports the build must support, such as delivery by insertion order against plan, deal delivery and reach and frequency, and how spend is reconciled with Campaign Manager 360 and the invoice. The DV360 reporting guide explains which report types expose which levels. A structure that mirrors the plan can be reported without a lookup table.
Filled example
Below, the sheet is completed for an invented business. The names, figures and dates are illustrative.
Lomqvaret Motors builds a launch-weekend campaign in DV360
Lomqvaret Motors is an invented group of car dealerships with showrooms in two regions. Its agency's trader filled this sheet for a new model's launch weekend, from a media plan of £48,000 over three weeks, before anything was created in DV360. The plan asked for reach among in-market car buyers in each region and for test-drive bookings.
| Field | Lomqvaret's build sheet |
|---|---|
| Campaign and goal | "LQM_ModelLaunch_Spring": goal raise awareness and drive bookings; KPI cost per test-drive booking, target £60; planned £48,000, 3 to 23 March; from media plan lines 4 and 5. Advertiser checks: currency and time zone as set, CM360 link live, brand-safety defaults set |
| Insertion orders | IO1 "North_Display": £26,000, flight pacing, even; plan line 4. IO2 "South_Display": £22,000, flight pacing, even; plan line 5. The regional news deal sits in IO1 with an explicit budget share so the open-auction line items cannot starve it |
| Line items | Per IO: LI-a prospecting, in-market audience, open auction, display; LI-b remarketing, site visitors in 30 days, open auction, display. IO1 also LI-c, the news publisher deal. LI-a and LI-b separate because they need different bids and caps; LI-c separate to read the deal on its own |
| Inventory and deals | LI-a and LI-b: open auction on the exchanges enabled at partner level, authorised sellers only. LI-c: private auction with a regional news publisher, deal ID recorded, floor £7 CPM, 3 to 23 March, status "active" checked in DV360 on 27 February |
| Audiences and exclusions | LI-a: Google in-market audience for new cars; no third-party segments, so no data fees. LI-b: Floodlight list of model-page visitors. Excluded on LI-a and LI-c: test-drive bookers and current finance customers (Customer Match upload) |
| Bidding and frequency | LI-a: automated, maximise conversions on the booking activity, average CPM ceiling £6. LI-b: automated, same goal, no ceiling. LI-c: fixed bid £7.50 CPM. Caps: campaign 10 per person per week; LI-b 3 per person per day |
| Brand safety and verification | Advertiser defaults: content labels up to general audiences, sensitive categories excluded. LI-c: unlabelled content allowed, because much of the publisher's inventory is unlabelled; checked with the publisher. Post-bid monitoring through the verification vendor's tag; read weekly by the agency's ad operations lead |
| Creatives | 6 display sizes of the launch creative and 2 sizes of a booking reminder, all as CM360 tags synced to DV360. Launch creative on LI-a and LI-c; reminder on LI-b. Optimised rotation |
| Conversion tags | Optimise to "TestDrive_Booked" (counter, standard counting, fires on the booking confirmation page). Report only on "Brochure_Download" and "Finance_Quote" |
| Trafficking | CM360 campaign with placements by sync from DV360; default ad on each placement is the launch creative. Verification wrapper on every creative; unwrapped copies kept. Checked by the ad operations lead on 1 March |
| Naming and reporting | Names follow the agency convention: Advertiser_Campaign_IO_Tactic_Inventory_Audience. Weekly offline report by IO and LI against plan; deal delivery report for LI-c; reach and frequency by region; spend reconciled with CM360 and the invoice at month end |
The launch checklist found one gap: LI-c had been built without the exclusion of test-drive bookers that the sheet required, and it was added before the flight. In the first week the deal line item delivered close to plan while LI-a ran slightly ahead; the trader left the structure as built and recorded the pacing in the campaign log.
Common mistakes
- Building before the plan is signed. A sheet filled from a draft plan produces insertion orders that do not match what finance will reconcile. Fill it from the signed plan and point each insertion order at its line.
- A deal sharing a line item or an insertion order with the open auction. The deal's delivery cannot be read on its own and can be starved by its sibling. Give each deal its own line item and protect its budget.
- Prospecting defaults on deal line items. Exclusions copied from prospecting can block most of a chosen publisher's inventory. Set each deal's brand-safety layer against that publisher.
- Missing exclusions. Prospecting line items without the converter exclusion spend on people who have already acted. Write exclusions beside inclusions on every row.
- Caps and bids from habit. Values copied from the last campaign rarely match this plan's reach and budget. Take them from the plan and record where each came from.
- Optimising to the wrong Floodlight activity. A strategy pointed at a page-view counter optimises for page views. Name the activity per line item and confirm it fires.
- Names invented at build time. Names typed in the platform without a convention become report dimensions nobody can sort. Write every name on the sheet first.
The media plan the sheet copies from, and the build sheets for search and paid social, are in the templates library.
