Ad trafficking is the work of turning an approved media plan into live, trackable campaigns. A trafficker builds the campaign in the ad server or DSP, attaches creatives and tags, sets targeting and caps, adds tracking and checks that everything works before spend begins. Trafficking services means paying a team to do that work for you.
This guide explains what trafficking involves, how a campaign hierarchy and naming convention should look, a launch timeline you can follow, and what to ask a provider. For the detailed checks, see our ad trafficking QA checklist. Our campaign management and trafficking service page describes how we work.
1What trafficking covers
| Task | What it involves |
|---|---|
| Campaign setup | Creating campaigns, line items or insertion orders with the right dates, budgets, goals, targeting and pacing |
| Creative trafficking | Uploading creatives, checking specs, adding click-through URLs and third-party tags |
| Tracking | Floodlight or conversion tags, UTM parameters, click trackers, impression trackers and viewability or brand safety tags |
| Tag management | Deploying and testing pixels, usually through a tag manager |
| QA | Checking rendering, click-through, tracking and targeting before and after launch |
| Change management | Creative swaps, flight changes, tag updates and clean-up when a campaign ends |
Trafficking sits between the media plan and the media buy. Errors made here, such as a wrong landing page, an uncapped line item or a broken tracking tag, tend to show up only after spend has gone out. Our post on the cost of ad trafficking errors shows how those mistakes happen.
2The tools involved
The stack differs by team. These are common choices in use today.
- Ad servers: Google Campaign Manager 360 is common for advertisers. Publishers often use Google Ad Manager. Other ad servers and creative platforms exist, and you should confirm what each client uses.
- DSPs: Google Display & Video 360, The Trade Desk, Amazon DSP, Yahoo or Microsoft platforms, and DOOH and CTV platforms.
- Creative and dynamic platforms: Flashtalking and similar tools for versioning and dynamic creative.
- Verification: DoubleVerify and Integral Ad Science (IAS) for viewability, invalid traffic and brand safety. Confirm which vendor the client requires, and whether it is applied through the DSP or through ad server tags.
- Tag management: Google Tag Manager and other tag managers, plus GA4 for analytics.
Some older names appear in outdated guides. Sizmek's ad server closed in 2019, and Oracle shut down Moat in 2024, so do not plan around either.
3A sample campaign hierarchy and naming convention
A clear structure makes reporting and QA easier. Below is an illustrative example, not a standard you must follow.
| Level | Example name | What it controls |
|---|---|---|
| Advertiser / client | ClientName | Account-level settings and access |
| Campaign | ClientName_Spring26_Awareness_US | Dates, overall goal, linked reporting |
| Placement / line item | CM_Video_Prospecting_CTV_US | Targeting, budget, frequency cap, pacing |
| Creative | Brand_30s_Spring26_v2 | Creative file, click-through URL, tracking tags |
Choose a delimiter and field order and use it everywhere. Include fields you will need to filter on later, such as market, channel, objective and flight. Decide up front who may create new names, otherwise variations creep in and break reporting.
Document UTM parameters the same way. A short table of allowed values for source, medium and campaign prevents the typo problem where the same traffic appears under several labels in GA4.
4A launch-day timeline
This timeline assumes a standard display or video launch. Adjust it for the number of creatives, platforms and approvals involved.
| When | What happens |
|---|---|
| T-5 to T-3 business days | Brief and creatives received. Intake form checked for missing items: flight dates, budget, targeting, landing URLs, tracking requirements and approvers |
| T-3 to T-2 days | Campaigns and line items built in staging or draft mode. Creatives uploaded. Specs checked against each publisher or exchange |
| T-2 to T-1 days | Full QA: preview all creatives, test clicks, confirm tracking tags fire, check geo and device targeting, verify caps and pacing, check brand safety and verification settings |
| T-1 day | Internal sign-off, then client or agency approval. Any fixes are retested |
| Launch day | Activate. Monitor early delivery: are impressions serving, in the right geography and placements, with tracking counts increasing? |
| T+1 day | Review the first day: spend vs plan, click-through checks, discrepancies between platforms. Log and fix issues |
| T+7 days | Check pacing, frequency, reporting alignment and creative performance |
Leave time for rejections. Some publishers and exchanges review creatives before they serve, and a rejected file at T-1 is much harder to fix than at T-5. For CTV launches, our CTV and BVOD trafficking checklist lists the extra checks. For deal-based buys, see the deal ID troubleshooting guide.
5Creative specs: always read the publisher sheet
File-weight and format limits vary by publisher, exchange and format. Initial load limits (the file size loaded before the user does anything) are typically small, with further polite loading allowed after the page loads. Treat any single figure in a blog post as a guide only, and check the current spec sheet for each placement. Record the spec you worked from in the ticket so that disputes can be settled later.
6Common failure modes and how to catch them
- Wrong or staging click-through URL. Click every ad in a fresh browser session before launch and after any change.
- Case-sensitive or missing clickTag variable. HTML5 creatives that work in a preview can fail in the live exchange. Test in the same environment as production.
- Unreplaced macros. Check the Network tab to see that macros such as cache-busters or click macros are filled in.
- Frequency caps set at the wrong level. A cap on a line item does not limit exposure across a campaign. Confirm the scope.
- Tracking not firing. Test impression and conversion tags in the real flow, not only in a tag manager preview.
- Targeting overlap or typo. Compare the delivery report with the brief on day one, by geography, device and placement.
7What to ask a trafficking provider
- Which ad servers and DSPs do your people work in every day? Can they show examples of the checks they run?
- How do you handle intake, and what do you do when information is missing?
- What is the turnaround for a standard setup, and what is the rush process?
- How are QA results recorded, and can we see them?
- What access do you need to our accounts, and how is it removed at the end?
- What happens when an error is found after launch? Who tells whom, and how fast?
Be cautious of any provider that promises no errors. Mistakes happen in every team. What matters is how often they are caught before launch, how they are recorded, and how the process improves. Our campaign launch QA page describes the checks we run.
8Next step
If you want to hand off trafficking, start with a few campaigns, a shared intake form and a QA checklist both sides can see. Contact us with your ad server, DSPs and typical weekly volume and we will suggest a scope.
