Tools and providers
Part of How to choose programmatic advertising tools and providers
Planning a programmatic advertising tool rollout
A practical programmatic advertising rollout plan: map workflows, audit data, assign an owner and test in stages before retiring the old process.
What to take away
- The common mistake is buying the licence before mapping the workflow, so the platform is configured to the vendor's demo rather than your process.
- Write a one-page inventory covering every tool, seat count, renewal date and monthly cost in pounds before you speak to a sales team.
- Name one internal owner. Shared ownership is the main reason rollouts stall after week two.
- Audit the lawful basis for audience data used in programmatic advertising at the design stage, using the ICO guidance below.
Start with the inventory, not the demo
Most teams book the demo first, and the sales engineer configures the screen around a campaign that does not resemble your own. You spend a quarter rebuilding what you already paid for.
Platform inventory fields
- Demand-side platform
- Ad server
- Verification vendor
- Reporting layer
- Finance export
- Owner, seats, renewal, monthly cost
List every platform that touches a campaign: the demand-side platform, ad server, verification vendor, reporting layer and finance export. Record the owner, seat count, renewal date and monthly cost in pounds for each.
That list is the scope document. If a prospective tool does not remove a line from it, ask why it is being bought. Our programmatic advertising tools and supplier guide for 2027 gives wider category context; use your inventory to define which capabilities a shortlisted product must replace or support.
Map the workflow the tool has to serve
Write the campaign lifecycle as it runs: brief, plan, trafficking, live checks and reconciliation. Mark every handover where a person copies data between systems. That is where implementation effort goes.
Then decide which platform owns which step. A demand-side platform may run bidding, while the ad server keeps the creative record and finance keeps the invoice.
Examples of programmatic demand-side platforms include Google Display & Video 360 (DV360) and The Trade Desk; Google Ad Manager is an ad server, while Integral Ad Science (IAS) provides ad verification. Treat these as examples, not recommendations: confirm each product's role, integrations and data responsibilities during procurement.
Decide what stays manual
Reconciliation often stays manual for a quarter while the numbers bed in.
Set the cutover date and the fallback
Keep the old process live for one full billing cycle. Name who can switch back, and the trigger for doing so.
Data, consent and privacy by design
Any tool that ingests audience data needs a written lawful basis and a retention rule before it goes live. The ICO's guidance on designing products that protect privacy explains how to build the controls in. For UK campaigns, assess the UK GDPR and Data Protection Act 2018, and check the Privacy and Electronic Communications Regulations 2003 (PECR) where cookies or similar technologies are used. Record the applicable lawful basis, such as consent or legitimate interests where justified; complete a data protection impact assessment (DPIA) before processing likely to result in high risk, and check whether the organisation must pay the ICO data protection fee.
Restrict fields to what the campaign needs, set a deletion date, and log who can export. If the vendor cannot say where data is stored, treat that as a procurement answer.
Name an owner and a decision rule
One person owns the implementation. They hold the milestone list, chair the weekly call and sign off each stage.
Set a decision rule for disputes: the owner decides, and the vendor records it in the shared project file.
Worked example: a mid-sized English agency
An agency with 14 media staff replaces a reporting vendor and adds a creative workflow tool. Figures are illustrative.
| Item | Monthly cost |
|---|---|
| Reporting platform, 14 seats | £1,400 |
| Creative workflow tool, 14 seats | £900 |
| Integration build, one-off | £3,200 |
| Training, two half-days | £1,100 |
First-year cost is roughly £30,800. Removing two manual reporting days a month saves about £1,000 at internal rates, so payback lands at roughly 14 months. That payback depends on the agency's existing baseline and cannot be derived from these figures alone; validate net incremental spend and savings before using it as a buying case.
Use our programmatic advertising supplier comparison as a further framework, and compare each shortlisted tool's quoted licence and implementation terms with the internal hours it is expected to remove.
Run the rollout in stages
Stage one: give the team read-only access to a sandbox; pass the gate by confirming user permissions and data mappings. Stage two: run one live campaign with one team; compare delivery, verification and reporting with the old process, and log exceptions. Stage three: move to full traffic only after the owner signs off the checks and the fallback test passes, then retire the old process.
Use the sandbox to test campaign setup, trafficking, live checks and reporting against the lifecycle you mapped.
Hold payment on the final milestone until the fallback test passes.
Common questions
How long should implementation take?
For a mid-sized agency, six to ten weeks from contract to full traffic is realistic, plus two weeks if data migration is involved.
Who should own the project?
A senior media operations lead, not the person who negotiated the contract. The owner needs authority over workflow changes.
What if the vendor misses a milestone?
Agree service levels (SLA), service credits, exit rights and data-portability obligations in writing. Apply the agreed remedy in the contract, usually a service credit, rather than extending the timeline without a written change note.
Do we need legal review?
Yes, if personal data crosses a border or the tool profiles individuals. Ask your data protection lead before signing.
