Why a programmatic account is harder to move than a self-serve account
In a self-serve platform the advertiser usually owns the account and grants an agency access, so a change of agency is a change of users. The DV360 account structure guide explains why programmatic is not like that. The partner sits at the top of the tree and is usually the agency or holding company; it holds the exchanges that may be bought from, the users and their roles, billing and partner costs, and it can hold channels, inventory sources and audiences shared by every advertiser under it. The advertiser sits under the partner and holds the currency, the link to the Campaign Manager 360 advertiser that brings Floodlight across, creatives, audiences and brand-safety defaults. The DV360 hub adds that access to the platform comes through a contract with Google or a certified reseller rather than a self-serve sign-up.
So a business can own its brand, its budget and its data and still find that the object holding its buying sits under someone else's contract. The guide to setting up a media agency agreement says the advertiser should own its ad server, its verification account and its demand-side platform seat, or at least its data and reporting within it, and sets out exit terms. Where that was written in at the start, a move is a project. Where it was not, the first job is to find out what the business actually owns.
What belongs to whom: seats, advertisers, the ad server and the data
Map every asset before the notice is served, because the answers decide the rest of the plan. The table sets out the usual position and what to confirm; the agreement, the platform's records and, where needed, Google or the reseller give the actual one.
| Asset | Usually held by | What to confirm | If the business cannot keep it |
|---|---|---|---|
| DV360 partner | The agency, holding company or reseller | Who contracted it and whether the business can be given its own | The new team uses its own partner or a new one |
| DV360 advertiser | Created under whoever holds the partner | Whether it can move, as the Help Centre and the contract allow | A new advertiser, rebuilt from exported records |
| CM360 advertiser and Floodlight | The agency's or the business's ad server account | Who holds the top role and whether more than one of the business's people do | The hardest loss: tags, history and lists are tied to it |
| Audience lists | The DV360 or CM360 advertiser; some shared from the partner | Which lists live at advertiser level and which come from the partner | Rebuilt from Floodlight and the business's own first-party data |
| Channels and inventory lists | The advertiser or the partner | Which were built for this advertiser and which are the agency's own | Exported as lists of URLs and apps and recreated |
| Deals | Created by publishers for a named buyer | Which seat each deal was issued to and when it ends | Re-issued by the publisher to the new buyer |
| Creatives | The DV360 or CM360 advertiser | Whether the source files and tags are held by the business | Rebuilt from source files |
| Reporting history | The advertisers and any exports | Which reports, files and dashboards the business can keep | Exported before access ends |
The tutorial on setting up a new advertiser builds this layer with ownership in the business from the start, and it is the template for anything the new team has to rebuild. The agency offboarding checklist covers ownership, assets, continuity and access removal for any agency and any platform; this guide adds what is specific to programmatic, and the checklist remains the place to tick it off. Bookings made outside the platform, such as television, press and poster lines, fall outside this guide, and the tutorial on handing live media bookings to a new agency or an in-house team takes them through the same change, from the notice date on each order to the credits owed each way.
Floodlight, audiences and reporting history: what must stay continuous
Floodlight is the part that must not break. The Floodlight tags guide explains that the configuration belongs to the Campaign Manager 360 advertiser, that its group and activity tag strings appear in every deployed tag, and that changing them after tags are live breaks every tag at once. A change of agency is the moment someone is tempted to tidy the configuration; it is the wrong moment. Keep the same advertiser, the same configuration and the same tags on the site, and link the new team to them. If the old agency holds the ad server account, the first request is full access for more than one person employed by the business, before anything else is discussed.
Audience lists follow. The guide to audiences in DV360 explains that lists are created at advertiser level and that the Help Centre describes the conditions under which a list can be shared with other advertisers under the same partner; it also explains that a list only collects members from the day it exists. If the DV360 advertiser cannot move, every list the new team needs has to be created in the new advertiser well before the old one stops, from the same Floodlight activities and from the business's own first-party dataData a business collects directly from its own customers, visitors and users., so that remarketing and exclusions work on the first day of the new flights. Record each list's definition, source and membership duration before access ends.
Reporting history is the third continuity question. The DV360 reporting guide describes offline reports, Data Transfer files and BigQuery routes. Export delivery, cost and conversion history at the level the business will want to compare against, by insertion order and line item with IDs, by creative and by inventory source, and keep the Floodlight reports alongside them. A new advertiser starts with no history, and next year's plan will be judged against this year's numbers.
Deals, insertion orders and live flights through the handover
A deal is created on the sell side for the buyer or buyers the publisher permits, and the deal ID has to be attached to something that bids, as the deal types guide explains. A deal issued to the old agency's seat does not follow the advertiser to a new one. The inventory and deals guide describes how deals arrive in the marketplace or are added by deal ID, and how they are assigned to line items. List every live deal, private auction (PMPAn invitation-only programmatic auction a publisher runs for selected buyers through a deal ID.), preferred and guaranteedA programmatic deal with a fixed price and reserved impressions, bought through a DSP., with the publisher, the seat it was issued to, the price and the end date, and ask each publisher early to re-issue the deals the new team will keep.
Guaranteed deals and insertion orders deserve a decision each. A guaranteed deal reserves volume the publisher has committed to deliver, so moving it mid-flight risks interrupting delivery on both sides; letting it finish under the old buyer is often simpler, with the agreement settling who manages it until then. For every live insertion order, decide whether it finishes with the old agency, is paused at a date both sides agree, or is rebuilt by the new team, and record who is accountable for pacing in each case. The worst outcome is a stretch of days in which both teams assume the other is watching. The academy checkpoint on advertiser ownership, set-up and account moves tests how to honour live insertion orders and guaranteed deals during a move.
Work the plan back from the date that cannot move. Backward planning starts from the notice date or the last day the old agency has access and schedules each step back from it, so each gets a latest start: exports before access ends, lists in the new advertiser before the first new flight, publisher conversations before deals expire, creatives approved before line items launch.
Bidding, learning and the first weeks under the new team
The bidding and pacing guide explains that each change to an automated strategy, its target or its conversion events restarts learning, and that learning needs volume. A new team in a new advertiser starts from no history at all, and even a new team in the same advertiser tends to change several things at once. Expect results to look worse for the first weeks, agree that in advance with whoever reads the reports, and ask the new team to change one thing at a time so each change can be read. Fixed bids on unfamiliar inventory, as the bidding guide recommends, are a reasonable bridge.
Ask the incoming team to run the programmatic advertising audit on what it inherits: the scorecard rates measurement, safety, deals, audiences, frequency, bidding and reconciliation, and ranks what to fix first. The agency onboarding checklist sets ownership and access up correctly for the new relationship, so the next move is easier than this one.
Taking programmatic in-house instead
Bringing the buying in-house changes who does the work, not what has to be settled. The guide to in-house and agency teams weighs the choice: in-house teams win on business knowledge, control and continuity, agencies on specialist depth and scale. For programmatic, practical questions about access and operations come first. Access: the business needs its own route to a partner, through Google or a reseller, and the Help Centre describes how partners are provisioned. Operating model: the DV360 hub notes that the platform assumes somebody traffics, checks and reports every week, and the programmatic campaign management playbook sets out that routine with named owners from flight set-up to monthly reconciliation. A business without the people to run it has bought a seat it cannot use. Everything else in this guide, Floodlight continuity, lists, deals, live flights and relearning, applies unchanged.
A pet insurer moves its programmatic buying (illustrative)
Yarnoqui Pet Insurance moves its programmatic buying to a new agency
Yarnoqui Pet Insurance, an invented pet insurer, spends about £480,000 a year on programmatic display and video through an agency that holds the partner seat. It gives 3 months' notice on 1 March, with the old agency's access ending on 31 May, and works back from that date.
| Weeks before access ends | Action |
|---|---|
| 13 | Confirms the CM360 advertiser is held in its own name; adds 2 of its own staff with the top role |
| 12 | Lists 7 live deals: 4 private auctions, 2 preferred deals and 1 guaranteed deal ending 30 April |
| 11 | Asks the 6 non-guaranteed publishers to re-issue deals to the new agency's seat from 1 June |
| 10 | Exports 24 months of delivery, cost and Floodlight conversion history by line item and creative |
| 9 | The new agency creates a DV360 advertiser under its partner, linked to the same CM360 advertiser |
| 8 | Recreates 5 Floodlight lists in the new advertiser so they fill before launch |
| 4 | Creatives rebuilt from source files and approved on the exchanges the deals use |
| 0 | Old agency access removed; the guaranteed deal finished under the old seat on 30 April |
New flights launch on 1 June on fixed bids. The quote-start cost per lead is £61 in the first fortnight against £44 in the last quarter under the old agency, as agreed in advance. The new agency moves 3 line items to an automated strategy in week 4, one at a time, and by week 9 cost per lead is £45. Because the CM360 advertiser and its Floodlight history never moved, the year-on-year report carries on without a break.
Common mistakes
- Serving notice before mapping ownership. The answers decide the timetable, and some take weeks to obtain.
- Letting the ad server go with the agency. The partner seat may be the agency's; Floodlight history should not be.
- Tidying Floodlight during the move. Changing tag strings breaks every deployed tag.
- Creating audience lists on the first day of the new flights. Lists start empty and fill only from the day they exist.
- Assuming deals follow the advertiser. Publishers issue deals to a buyer, and each one may need re-issuing.
- Moving a guaranteed deal mid-flight. Letting it finish under the old buyer is usually simpler.
- No owner for live insertion orders. Each one needs a named person accountable for pacing through the handover.
- Judging the new team in its first weeks. Automated strategies relearn, and a new advertiser starts with no history.
- Removing access before exports are complete. Delivery and conversion history has to be saved first.
