What sits above the first DV360 line item and why the business must own it
The DV360 account structure guide sets out the tree that every buy hangs from: a partner created by Google or a reseller when the contract is signed, holding users and roles, the exchanges the partner may buy from, billing profiles and partner costs; an advertiser under it holding currency and time zone, the link to a Campaign Manager 360 advertiser that brings the Floodlight configuration across, the creative library, first-party audiences and brand-safety defaults; and campaigns, insertion orders and line items below. The Campaign Manager 360 hub describes the ad server's side: an account with users, roles and permissions, and an advertiser holding creatives, landing pages, the Floodlight configuration and audience lists, with Floodlight belonging to the advertiser rather than to any campaign. The comparison of CM360 and DV360 explains why the two are usually linked and why the ad server, not the buying platform, is the count to report.
| Asset | What it holds | Who usually creates it | Where this site explains it |
|---|---|---|---|
| DV360Google's enterprise DSP. partner | Exchanges, users and roles, billing profiles, partner costs | Google or a reseller, for the agency or the business | Account structure |
| DV360 advertiser | Currency, time zone, the CM360 link, creatives, audiences, safety defaults | Whoever holds the partner | Account structure |
| CM360Ad server and measurement platform. advertiser | Creatives, landing pages, the Floodlight configuration, audience lists | The account holder, agency or in-house | CM360 hub |
| Floodlight configuration | Activity groups, activities, counting methods, custom variables | The analyst or ad operations lead | Floodlight tags guide |
| Audience lists | Floodlight and other first-party lists | The trader, from the advertiser's data | Audiences in DV360 |
| People and partners | Who may do what with each asset | The accountable person | This tutorial, the access step |
Ownership matters most at a moment nobody plans for. The guide to setting up a media agency agreement says the advertiser should own its ad server and verification accounts and its demand-side platform seat, or at least its data and reporting within it, and the partner level often belongs to the agency because that is how access to the platform is contracted. That makes the advertiser level, and above all the ad server and its Floodlight history, the part the business has to secure. The Display & Video 360 and Campaign Manager 360 help centres, listed in the sources, are the reference for the screens, the role names, provisioning and any setting that cannot be changed after creation; screens are renamed from time to time, so the steps below say what to decide and why rather than which button to press. The academy ownership and migration checkpoint tests why the business should own the advertiser layer and which settings to decide before an advertiser is created.
Before you start
- A named owner inside the business: the person accountable for the programmatic assets, who will still be there when the agency or the trader has moved on.
- A second person employed by the business who can hold full access to the ad server and the buying platform.
- The agency agreement or statement of work, open at the clauses on ownership, data and exit.
- Finance's reporting currency and time zone, and the name the business wants to see on every report.
- The measurement plan: the outcomes worth counting, which need revenue, and what extra detail reports need.
- The site's consent platform and its owner, because every tag will be gated behind it.
- A list of the people, agencies and vendors who will need access, with the job each one has to do.
- A shared document for the setup recordA one-page document, kept in the business's own storage, recording an account's owner and admins, assets, links and setup decisions for whoever inherits it., kept somewhere the business controls.
The steps
Decide who owns the platform seats and who is accountable for each asset
Write down, before anyone creates anything, who holds the partner seat, who owns the ad server account, and who in the business is accountable for the advertiser, the Floodlight configuration and the lists. A RACI matrix does it in a few lines: the business accountable, the agency or ad operations lead responsible for the build, the analyst and whoever owns the website consulted, and finance informed for billing. If the agency holds the partner, record what the agreement says the business can export and keep when the relationship ends, and add the missing clause now if there is none. The agency onboarding checklist treats an account the business cannot reach as a failed line rather than a convenience, and so should this step.
Create the CM360 advertiser under an account the business can reach
Create the advertiser in Campaign Manager 360 under the business's own account where it has one, or under the agency's account with named access for two people from the business where it does not. The advertiser is the level that keeps creatives, landing pages, Floodlight and lists across every campaign the brand will ever run, so it should outlive any one flight and any one supplier. Name it for the brand rather than for a campaign or an agency, and record who holds the top role on it. Everything trafficked later, as the CM360 trafficking tutorial describes, sits underneath this one object.
Design the Floodlight configuration before any tag ships
Settle the activity groups and activities from the measurement plan before a single tag is published. The Floodlight tags guide is clear about what cannot be undone: a group's type, counter or sales, is fixed when it is created, and the group and activity tag strings appear in every deployed tag, so changing them later breaks every tag at once. Name groups for the questions reports will ask, give each activity one action, decide which outcomes carry revenue and quantity, and write down each custom variable with its type and source before it is used. Deploy the tags behind the trigger the consent platform raises; Google documents that Floodlight tags deployed through the Google tag respect Consent ModeA Google tag feature that adjusts what tags collect according to the visitor's consent choices., and the privacy and consent guide explains how consent reaches Google tags in the first place. Test both branches, consent granted and refused, before anything depends on the counts.
Create the DV360 advertiser with a deliberate currency and time zone
Create the advertiser under the partner with the currency finance reports in and the time zone the business reconciles its days in, and agree both with finance before anyone clicks. The account structure guide notes that the Help Centre lists which advertiser settings cannot be changed after creation, and these two govern every budget, pacing view and report beneath the advertiser. Use the same brand name as the CM360 advertiser so that anyone reading either platform knows they are looking at the same business. A wrong choice here is cheap to fix today and expensive in a month, when it means a second advertiser and a reporting history split in two.
Link the DV360 advertiser to the CM360 advertiser
Link the two advertisers so the Floodlight configuration comes across to DV360. From then on line items can count and bid towards the same activities the ad server records, audiences can be built from them, and creatives trafficked in the ad server can be synced rather than pasted as tags. The CM360 trafficking tutorial adds that a DV360 advertiser set to serve through CM360 creates and keeps in sync the placements, ads and creatives for its line items, which is how one record of every impression is kept across every buy. Check the link from both sides, and fire a test conversion that shows up as an activity before any campaign relies on it.
Set brand-safety defaults at advertiser level
Set the defaults a new line item starts with at the advertiser rather than on each line item: the digital content labels to exclude, the sensitive categories, and whether unlabelled content is bought. The brand safety and viewability guide separates the safety floor, which should be on for every advertiser, from suitability, which is the brand's own judgement written down with the people who own the brand. Defaults at this level mean the next line item somebody builds in a hurry starts safe without anyone remembering to tick a box; deals and individual line items can still be adjusted where the written suitability decision allows.
Create first-party audience lists as soon as the tags fire
Create the Floodlight lists the first plan will need in the week the tags go live, not on the day the campaign launches. The guide to audiences in DV360 explains why: a list only begins collecting members when it is created, so a remarketing line item launched beside a new list has nobody to reach, and every list is shrunk by consent and browser limits. Build the lists from the advertiser's own First-Party DataData a business collects directly from its own customers, visitors and users.: product viewers, people who started a sign-up or a basket, and a converter list kept for exclusion from prospecting. Decide now who may upload customer files, and on what basis, because that is a decision for the business rather than for whoever builds the campaign.
Grant access by job for staff, agency and vendors
Give each person the access their work needs and nothing more, using the roles the two help centres describe. A trader needs the buying platform and the advertiser, not the partner's billing; a trafficker needs the ad server; an analyst needs reports and Floodlight; a verification vendor needs only the tags it supplies. Agencies work through named people the business can see, never through a shared login, and at least two people employed by the business keep full access to the ad server advertiser at all times. Record who was given what, when and why, with a review date, and remove access the day someone leaves; the record turns that into a lookup rather than an investigation.
Write the naming convention and the setup record
Finish with two short documents. The first is a Naming ConventionAn agreed pattern for naming campaigns, ads, events and tracking parameters so that reports can group them reliably. that joins DV360 insertion orders and line items to CM360 campaigns and placements, so that the monthly reconciliation the comparison page describes can be done without a lookup table; the Google Ads naming conventions guide sets out the same discipline for search, and the fields carry over. The second is the setup record: the owner and deputy, who holds the partner, the two advertisers and their link, the currency and time zone with the date they were agreed, the Floodlight groups and variables, the safety defaults, the lists, every person and partner with their access, and the next review date. Keep it in the business's own storage. The new ad account setup checklist gives the same ownership decisions as tickable lines, and LinkedIn advertisers will recognise the order from the tutorial on setting up LinkedIn Campaign Manager.
The first campaign is the next job, not this one. The DV360 hub sets out a first campaign in order, starting from the advertiser readiness this tutorial has just established; the programmatic campaign build sheet records each insertion order and line item before the build; and the DV360 campaign launch checklist checks the build against the signed plan before the flight starts. Anything Google requires before an advertiser can buy is set out in the help centres, which change, so this page does not list it.
A garden machinery maker sets up its advertisers before the first flight (illustrative)
Zubrekko Garden Machinery sets up DV360 and CM360 before its first flight
Zubrekko Garden Machinery, an invented maker of mowers and hedge cutters that sells through its own site and 140 dealers, plans £90,000 of programmatic display and online video over six months through an agency that holds the partner seat. The marketing director is accountable; the e-commerce manager is the deputy. They spend three working sessions with the agency and write this record.
| Item | Setup |
|---|---|
| Ownership | Agency holds the partner; the agreement now gives the business export rights to delivery, conversion and audience data |
| CM360 advertiser | Created under the agency's account, named for the brand, with the marketing director and e-commerce manager holding the top role |
| Floodlight | 2 groups: a counter group "Leads" (dealer finder used, brochure requested) and a sales group "Orders" with the order number in ord; 3 custom variables for product line, dealer region and promotion code |
| DV360 advertiser | Pounds sterling and the UK time zone, agreed with finance on day 1 |
| Link | DV360 linked to the CM360 advertiser; a test order recorded as an activity before launch |
| Safety defaults | Floor categories excluded, unlabelled content excluded pending the written suitability decision |
| Audience lists | 4 Floodlight lists created the day tags went live, 5 weeks before the first flight; the product-viewer list held about 38,000 identifiers at launch |
| Access | 3 named agency people for buying and trafficking; the analyst with reports only; the verification vendor with no platform access |
| Review | Access and the record reviewed on the first working day of each quarter |
The first flight starts on time with a remarketing line item that already has people to reach. A year later the business changes agency: because the ad server advertiser, its Floodlight history and the lists were never the agency's to take, the new agency is linked to the same CM360 advertiser in one meeting, and the reporting history carries on without a break.
Common mistakes
- Letting the agency own the ad server advertiser outright. The partner seat may have to be the agency's; the Floodlight history and the lists should not be.
- Publishing tags before the activities are designed. Group types and tag strings cannot be changed without breaking what is already deployed.
- Accepting the default currency and time zone. They govern every budget and report and are among the settings the Help Centre says cannot be changed later.
- Creating audience lists on launch day. A list starts empty and fills only from the day it exists.
- Setting safety on each line item instead of the advertiser. The next line item built in a hurry starts unsafe.
- One person from the business with access. The account then survives only as long as that person's login does.
- Access by shared login. Partners work through named access the business can see and remove.
- No written record. Without one, the next handover begins by rediscovering what exists.
