What this checkpoint covers
The questions draw on the tutorial on setting up a new advertiser, the tutorial on moving display from Google Ads to DV360 and the guide to moving a programmatic account to a new agency. Every scenario is set at Imbersfoy Lanes, an invented group of bowling and arcade venues that takes bookings online and has bought display through agencies for some time.
Task
Write a short answer to each question before opening the explanations: the action and the reason. Count an answer as right only if the reason matches. For every miss, note what you overlooked and reread the linked section; if you missed several on the display move, redo the exercise on moving a hiking boot maker's display into DV360.
Questions
- Imbersfoy Lanes' agency holds the DV360 partner seat and offers to create the DV360 advertiser, the CM360 advertiser and the Floodlight configuration under its own accounts "to save time". Is any of that acceptable, and what must Imbersfoy insist on?
- The agency's trader is about to create the DV360 advertiser in the agency's billing currency and time zone, and to ship Floodlight tags with provisional activity names that "can be tidied later". What do you stop, and why?
- For the move from Google Ads display, the agency proposes to recreate the remarketing lists, ad groups and responsive display ads in DV360 during launch week. What is wrong with the plan?
- A fortnight into the parallel run, the operations director wants to move all display budget to DV360 because its cost per booking looks lower. Read the figures below and say what you recommend.
- A year later Imbersfoy changes agency. The outgoing agency offers to "clean up" the Floodlight activities before handing over, and the incoming one suggests starting a fresh CM360 advertiser. What do you say to each?
- At the notice date a guaranteed deal with a family entertainment publisher still has weeks to run, and several insertion ordersThe contract for a direct or guaranteed media buy, recording what will run, where, when, at what price and what happens if it does not run. are live. How should each be handled?
- In the first weeks under the new agency, cost per booking rises and the board asks whether the change was a mistake. What should already have been agreed, and what do you ask the new team to do?
Imbersfoy Lanes: the first two weeks of the parallel run
| Source | Google Ads display | DV360 |
|---|---|---|
| Each platform's own conversion column, cost per booking | £9.10 | £6.40 |
| Imbersfoy's booking system, credited by tagged landing URLs under one rule, cost per booking | £8.20 | £11.90 |
| Gate written before launch for the first stage | Within 15% of £8.20, so no more than £8.20 × 1.15 ≈ £9.43 |
The DV360 line items are on fixed bids, the Floodlight lists were created a week before launch and some creatives are still in review on one exchange.
Answers explained
- The partner, yes; the history-carrying layer, only with the business holding it. The partner usually belongs to whoever contracted with Google or a reseller. The CM360 advertiser and Floodlight, the lists, creatives and reporting must sit where Imbersfoy can reach and export them, with more than one of its own people holding the top role, and the export right written into the agreement before the first campaign (what sits above the first line item; ownership clauses in the guide to setting up a media agency agreement).
- Both. Treat currency and time zone as permanent and agree them with finance: a wrong choice means a second advertiser and a split history. Floodlight group types are fixed at creation and tag strings sit in every deployed tag, so design the configuration before any tag ships (advertiser settings and Floodlight design).
- It treats a rebuild as a copy, and too late. Plan as if no list crosses over: Floodlight lists must exist weeks ahead to fill. Ad groups become line items designed from the plan, responsive display ads become creatives in the sizes the inventory sends, reviewed per exchange (why the move is a rebuild).
- Hold. On the one agreed measure, from Imbersfoy's own booking system, DV360 is behind and outside the gate written before launch. Its own column is for diagnosis. Early weeks run on fixed bids, young lists and creatives still in review, so the gate holds rather than stops, and budget moves in stages only once it is passed (the parallel run and staged budget).
- No to both. Floodlight must stay continuous: same advertiser, same configuration, same tags, with the new team linked to them. A change of agency is the wrong moment to tidy, because changing tag strings breaks every tag. If the DV360 advertiser cannot move, lists are recreated in the new one well before the old stops, and reporting history is exported before access ends (what must stay continuous).
- A decision each, worked back from the access end date. Letting the guaranteed deal finish under the buyer it was issued to is usually simpler; ask the publisher early and agree who manages it until then. Each insertion order finishes with the old agency, pauses on an agreed date or is rebuilt, with a named person accountable for pacing (deals, insertion orders and live flights).
- That results would look worse at first. Automated strategies relearn after change, and a new advertiser has no history. Ask the team to change one thing at a time, bridge on fixed bids and run the programmatic advertising audit on what it inherited (bidding and the first weeks).
Where to go next
If the ownership questions caught you out, compare the agency offboarding checklist with the setup record from the boot maker exercise. Then continue to the second module and work through handling a brand safety incident for a car seat maker.
