Before you start
- The concepts. Read the ad serving basics guide first: tag types, counting, rotation and default ads are used here without explanation.
- Access. A CM360 user role on the account with trafficking rights for the advertiser, and agreement on who approves the campaign before tags are sent.
- The media plan. The signed insertion orders or deal confirmations with, for each line, the publisher, the placement name, the size or format, the dates, the pricing model and the tag type the publisher accepts. Trafficking copies the plan; it cannot repair a vague one.
- Creative assets in the formats the plan calls for, named to a convention that encodes campaign, size and version, with landing page URLs and any third-party trackers from vendors.
- Floodlight activities already created and tested, following the Floodlight tags guide. Trafficking attaches them; it does not design them.
- A naming convention for campaigns, placements and ads agreed with whoever reads the reports, because every name typed here becomes a dimension value in reporting.
- Publisher contacts and their lead times for tag delivery and testing.
The trafficking sequence
Create the campaign under the right advertiser
In the Trafficking area, open the advertiser the brand belongs to and create a new campaign. Give it the name from the convention, the start and end dates from the plan, and the default landing page, which every ad inherits unless overridden. Check that the advertiser is the one whose Floodlight configuration measures this brand; a campaign created under the wrong advertiser cannot be moved, and its conversions will land in the wrong configuration. The help centre documents the option to copy an existing campaign, including its placements and ads, which saves time for a repeating flight but copies its mistakes too. Record the campaign identifier, because publishers, the buying platform and the data team will all ask for it.
Add the sites and create the placements
Each publisher in the plan is a site in CM360. Search the directory of sites first; most publishers already exist, and creating a duplicate splits reporting. Then create one placement per line on the plan: name, site, the compatibility that matches the format (display, in-stream video, in-app and the others documented), size for display, start and end dates, the pricing schedule that mirrors the insertion order, and the tag type the publisher accepts. Placement groups, documented as packages and roadblocks, bundle placements that are bought or must serve together. Placements for a linked DV360 advertiser arrive by sync and are left alone here; the DV360 hub explains that link.
Upload and check the creatives
Creatives are uploaded at advertiser level, so they can serve in any campaign of that advertiser. Upload each asset under its creative type: display image, HTML5 bundle, in-stream video, rich media from Studio, or a third-party tag pasted as a redirect creative. CM360 validates uploads and reports problems such as a bundle that references external files or a video that fails transcoding; fix them now rather than after the ad is live. Set the creative's landing page if it differs from the campaign default, add any third-party impression or click trackers the vendor supplied, and name each creative to the convention so that reports read clearly. The DV360 creatives guide covers programmatic creative formats that will be hosted here when DV360 serves through CM360.
Create the ads
An ad connects placements to creatives. In the campaign, create a standard ad of the type that matches the placement compatibility, set its dates within the campaign's, assign the placements it should serve to, and assign the creatives. Each placement also needs a default ad, which CM360 requires; make the default a real, approved creative with the right landing page rather than a blank, because the default serves whenever nothing else qualifies, including before launch and after the standard ads end. Tracking ads and click trackers are created here as well for placements that only count. One ad per intended combination of placements and creative set keeps rotation and reporting legible.
Set rotation, priority, targeting and caps
On each standard ad, choose the creative rotation the plan calls for: even, weighted with explicit weights, sequential to tell a story across exposures, or optimised towards the metric chosen, usually click rate (CTRShare of impressions that result in a click.) or a Floodlight activity. Set the priority if some ads must take precedence over others on the same placement. Apply targeting only where the plan specifies it: geography, browser, operating system, language, day and time, placement keywords or an audience list. Add a frequency cap where the deal or the creative strategy needs one. Then preview the assignments: every placement should list at least one standard ad whose dates and targeting allow it to serve on launch day.
Attach Floodlight and third-party tracking
Confirm that the Floodlight activities the campaign will be judged by exist in the advertiser's configuration and are receiving test firings. Trafficking does not change them, but the campaign's reports and any audience lists depend on them, so this is the last point to catch a missing activity before launch. Add the vendor trackers at the right level: on a creative if they should fire wherever it serves, on the ad if they belong only to this campaign's placements. For in-stream video, attach the documented event trackers to the creative. Where a verification vendor wraps the tag, follow the vendor's documented wrapping process and keep an unwrapped copy for troubleshooting.
Generate the placement tags
Select the placements in the campaign and export their tags. CM360 offers the tag formats described in the ad serving guide, and the export lets you choose the format per placement, include or exclude the default ad's preview, and add the campaign's tracking options. Export as a spreadsheet or a document to send, or to a format a publisher's system accepts. Open the export and read it: each placement should show the expected format, the cache-busting and click placeholders should be present, and the placement names should match the plan the publisher holds. Keep the exported file with the campaign record so that a later discrepancy can be traced to exactly what was sent.
Send the tags and confirm receipt
Send each publisher only the tags for their placements, with the insertion order reference, the flight dates and the contact for problems. CM360 documents sending tags by email directly from the export and downloading them to attach manually. Ask each publisher to confirm receipt and the date their line items will go live, and to tell you which tag format they implemented if it differs from the one you sent. For placements that a linked DV360 advertiser serves, no tags are sent; the sync carries them. Record every confirmation in the campaign log. Unconfirmed tags are the single most common reason a placement shows nothing on launch day. Radio, press and poster buys have no tags to send, and the tutorial on delivering creative and copy instructions to media owners runs the same confirm-and-record routine for finished material.
QA the live placements
On launch day, check delivery from both ends. In CM360, open the campaign and confirm that each placement has begun serving and that the standard ads, not the defaults, are the ones delivering. Use the ad preview for each placement to see the creative as it will render, and load the publisher's live page to see the real tag in place with the right creative and landing page; click through and confirm the click is counted and the page loads. Check the first day's impressions by placement against the plan's expected daily volume and against the publisher's own early numbers, and check Floodlight activities for conversions attributed to the campaign. The CM360 reporting guide describes the reports to use for these checks, and the CM360 hub maps the common failures to their fixes.
Trafficking checklist
Run the checklist before tags leave the account and again on launch day. Each row is a failure someone has already had. The buying side has its own pre-flight: the DV360 campaign launch checklist covers insertion orders, deals, brand safety and frequency for line items that serve through these placements.
| Check | Where | Pass condition |
|---|---|---|
| Campaign under the correct advertiser | Campaign properties | Advertiser's Floodlight configuration is the one that measures this brand |
| Campaign dates cover every placement and ad | Campaign and placement dates | No placement or ad starts before or ends after the campaign |
| One placement per plan line, no duplicates | Placement list against the media plan | Names, sizes, dates and pricing match the insertion order |
| Tag type matches what the publisher accepts | Placement tag settings | Format agreed in writing with the publisher |
| Every creative validated | Creatives list | No validation warnings; landing pages resolve |
| Every placement has a default ad with a real creative | Ads list | Default is approved and points to the right landing page |
| Every placement has at least one eligible standard ad | Ad assignments and dates | Standard ad dates and targeting allow serving on launch day |
| Rotation and weights match the plan | Ad settings | Rotation type and weights or optimisation metric as specified |
| Targeting applied only where the plan asks | Ad targeting | No stray geography or audience restriction from a copied ad |
| Floodlight activities exist and receive firings | Floodlight configuration | Each activity shows recent test firings |
| Vendor trackers at the right level | Creative and ad tracking settings | Campaign-specific trackers on ads, not shared creatives |
| Tags exported with placeholders intact | Tag export file | Cache-busting and click placeholders present on every tag |
| Tags sent to the correct publisher contact | Campaign log | Receipt and go-live date confirmed for every placement |
| Launch-day delivery verified | Campaign overview, preview, live page | Standard ads serving; clicks counted; conversions attributed |
A twelve-placement launch, start to finish
A regional bank traffics a mortgage campaign with twelve placements across four publishers plus a DV360 display line that serves through CM360. The trafficker creates the campaign on a Monday, builds the twelve placements from the plan in about ninety minutes, uploads 18 display creatives in three sizes, and creates four standard ads with weighted rotation and one default ad per placement. Tags go out on Tuesday; two publishers confirm the same day, one on Wednesday, and the fourth only after a reminder on Thursday. On launch day, eleven placements serve standard ads. The twelfth shows 9,400 impressions, all on the default ad: the standard ad's start date had been typed a week late. Fixed within an hour, the placement delivers its planned 60,000 impressions a day from the following morning, and the Floodlight report attributes the first 14 mortgage enquiries to the campaign by the end of the week.
For the reasons an advertiser traffics creative in an ad server rather than only in its buying platform, the CM360 versus DV360 comparison sets out what each tool is for. Once trafficking is done, the programmatic campaign management playbook carries the flight through daily pacing, weekly placement and frequency reviews and monthly reconciliation.
Common mistakes
- Trafficking from a draft plan. Every later change to the plan becomes a change to placements, ads and tags already sent.
- Creating a new site instead of finding the existing one. Reporting for that publisher splits in two forever.
- A blank default ad. It serves whenever the standard ads cannot, which is more often than anyone intends.
- Copying a campaign and keeping its targeting. Last quarter's geography exclusion quietly applies to this quarter's national flight.
- Sending one export to every publisher. Each publisher receives tags for placements that are not theirs, and some will implement them.
- No confirmation log. When a placement is silent on launch day, nobody can say whether the tag was ever received.
- Skipping the live-page check. The ad preview shows what CM360 would serve; only the publisher's page shows what was implemented. The ad serving basics guide explains why the two can differ.
