How to run connected TV advertising tool implementation without chaos

Who should own the setup?

Implementation starts by giving one person authority to carry the project from signed agreement to working buying, trafficking and reporting. The connected TV advertising workflow sets out the wider process; the practical safeguard here is an owner who can decide configuration, access and budget questions without waiting for a group.

Name a deputy so holidays or other absences do not stall decisions. Give the owner a written scope that says what the tool will do, what it will not do and which existing processes it replaces. This makes requests for extras easier to assess and gives colleagues a clear reference point.

A scope should be agreed before configuration begins, rather than expanded informally during the build. The tools and supplier guide can help explain the chosen tool in the context of other supplier categories when finance or media colleagues ask why it was selected.

What information needs to be agreed before setup?

Settle the data fields, conversion definitions and naming rules before anyone configures the platform. Mapping them in a spreadsheet first helps the team identify mismatches while they are still easy to resolve, rather than discovering them in the first reporting cycle.

Agree who owns the conversion definition and compare it with the platform default. A difference between the reporting window used by the tool and the one used internally can trigger disputes in the first month, so document the chosen definition before data starts flowing.

Check whether the tool accepts the identifiers produced by connected systems. For example, if a CRM exports hashed email addresses while the platform expects customer IDs, record the mismatch during spreadsheet mapping and resolve it before launch instead of leaving it to the live campaign.

Set one structure for campaign names, such as brand, objective, audience and date. Keep each name readable in a report while making its parts consistent enough for filters to work. Record the convention in a shared document with a version number.

Give users only the access they need, set spend approval limits and remove access promptly when someone changes role. A quarterly access review helps the owner check permissions. When reviewing identifier transfers and access, consult the ICO guidance as part of the same preparation.

What does setup look like on named platforms?

The steps differ by platform, so map your data choices against the one you chose. These notes cover three common buying platforms and are a starting checklist, not a replacement for each vendor's documentation.

For UK broadcaster BVOD such as ITVX, ads are normally cleared by Clearcast before they run, so add that step to the creative timeline. Creative for programmatic CTV is served through VAST tags, so test the tag in each platform's preview before the first flight.

How can the team test the tool without stopping current work?

Run a small live campaign alongside the existing process before switching over. A parallel test lets the team compare what each system reports and check whether any differences can be explained before the old way of working is retired.

Keep both processes running for at least two weeks and compare impressions, spend and reported conversions. Small differences in reach and frequency are expected; the important check is whether the gap is explainable and stable. The measurement plan should make clear which figures the team will compare.

What should be checked before the first campaign goes live?

Check creative requirements before the first flight, including each platform's aspect ratio and audio rules. The creative checklist can support that check. Resolving rejected assets before launch protects the work already done on configuration and campaign preparation.

Google's video-format documentation can help the team check that trafficking matches the campaign structure. For the broadcast advertising context, consult the BCAP Code, which the ASA applies to TV and on-demand ads. If new assets are needed, Thinkbox's guidance on making an affordable TV advert may help keep production costs sensible.

How should regular users learn the new process?

Train the people who will operate the tool each week, not only the contract signatory. A hands-on training session should practise the three regular tasks: building a campaign, pulling a report and pausing a line item.

Write a short runbook for exceptions, including a rejected creative, a failed data sync and a platform outage. State who to contact in each case. Keep supporting references nearby, such as the ICO security guidance, the NCSC access control guidance, Ofcom advertising rules and National Archives digital records guidance, so the team can find them when a check comes up.

How can the owner tell whether the setup is ready?

Readiness means the owner can show that responsibilities, data choices, permissions, testing, creative checks and user training are in place. Use a short sign-off list to spot unfinished work; the supplier comparison can also help when the team needs to revisit how tools were assessed.

Timing depends on the number of platforms and integrations involved. Data mapping often takes longest because it depends on other teams. Score similar tools on import effort, reporting flexibility, access controls and support response times before committing, rather than postponing those checks until setup.

What should I do first?

Start by appointing the owner and writing the scope before configuring the tool. These first actions give the team a clear decision point and define what must be mapped, tested and approved before the new process replaces the existing one.