What an ad server does for an advertiser
Publishers run their own ad servers to decide what fills each slot on their pages. An advertiser-side ad server is the advertiser's own record of the same events, kept under one methodology no matter who sold the media. CM360 does three jobs. It serves: a placement tag on the publisher's page or inside a programmatic creative calls CM360, which picks the right ad and returns the creative. It counts: the impression when the creative begins to render, the click when the person passes through the CM360 click redirect, and the conversion when a Floodlight tag fires on the advertiser's site. And it controls: dates, rotation, targeting and frequency caps are changed centrally after the tags have shipped, so a creative swap or a paused ad never needs a publisher to touch anything.
Without an ad server, an advertiser depends on each publisher's and each platform's counts, which differ in timing, methodology and time zone, and must chase every publisher to change a creative. With one, there is a single source of truth, one set of hosted assets and one conversion record that every channel shares. The ad serving basics guide explains the request chain, the tag types and why counts still differ at the edges.
The CM360 hierarchy
Everything in CM360 lives inside a fixed hierarchy. Knowing which level owns which setting answers most "where do I change this" questions before they are asked.
| Level | What it holds | Typical owner |
|---|---|---|
| Account | The top-level container: users, roles and permissions, subaccounts, account-wide settings | Agency or in-house ad operations lead |
| Advertiser | A brand or business unit: its creatives, landing pages, Floodlight configuration and audience lists | Account manager for that brand |
| Campaign | A flight: dates, default landing page, the placements bought and the ads that serve into them | Campaign manager |
| Site and placement | The publisher (site) and each slot bought on it (placement): size or compatibility, dates, pricing, tag type | Trafficker |
| Ad | The rule that joins placements to creatives: rotation, targeting, frequency cap, dates, priority | Trafficker |
| Creative | The asset itself: image, HTML5, in-stream video, rich media or a third-party tag | Creative or production team |
The relationships matter more than the names. Placements are what get tagged and sent to publishers; ads decide what appears in them; creatives are uploaded once at advertiser level and reused across ads and campaigns. Floodlight belongs to the advertiser rather than the campaign, which is why one configuration measures every flight the brand runs, and why audience lists built from it can be shared with DV360. Advertiser groups and subaccounts, documented in the help centre, add structure above this for agencies that manage many brands; a single-brand team rarely needs them.
Floodlight in brief
Floodlight is CM360's conversion tracking. Each advertiser has a Floodlight configuration; inside it, activity groups of type counter or sales hold the activities that represent actions worth counting, such as a lead form, a sign-up or a purchase with its revenue. Each activity has tag strings that identify it when the tag fires, and the tag itself is deployed as the Google tag with an event snippet, or in iframe or image form for pages that cannot run script. When an activity fires, CM360 looks for impressions and clicks it served to that browser within the activity's click-through and view-through windows and attributes the conversion accordingly, which is the basis for AttributionAssigning conversion credit to touchpoints. across channels and for the path reports described later.
A measurement plan should settle the activities before any trafficking begins: which actions count, which group they belong to, which need revenue and quantity, and which custom variables will carry extra detail. The Floodlight tags guide covers activity design, counting methods, Tag Manager deployment, custom variables, conversion windows and testing. When the configuration was built by someone else, the tutorial on cleaning up an inherited Floodlight configuration puts it in order without breaking conversion history or the bid strategies and audience lists that read it.
Trafficking and verification in brief
Trafficking is the sequence that turns a media plan into live ads: create the campaign, add the sites and placements that match the plan, upload creatives, create the ads that connect the two with rotation and targeting rules, attach Floodlight and third-party tracking, export the placement tags, send them to each publisher or buying platform, and check that delivery begins as expected. The order is fixed because each object depends on the one before it; a placement cannot be tagged until the campaign exists, and an ad cannot serve until it has both a placement and a creative. The trafficking workflow tutorial walks the documented sequence with a checklist at the end.
Verification is the set of CM360 features that check where and how the ads actually ran: whether tags are live and serving, the content and geography of the pages that called them, viewability measured through Active View, and blocked or unmeasurable impressions. It is the trafficker's early-warning system in the first days of a flight and the planner's evidence at the end of it.
Reporting in brief
CM360's Report Builder produces the reports most teams rely on: standard reports across any combination of advertiser, campaign, site, placement, ad and creative dimensions; Floodlight reports that count conversions by activity and split them between click-through and view-through; path-to-conversion reports that show the sequence of impressions and clicks before a conversion; and reach reports that count unique browsers (ReachUnique people who saw an ad.) and the frequency behind the raw impression totals. Reports can be scheduled, shared with other users and delivered by email, and Data Transfer provides the log-level files that a data team loads into a warehouse when the interface's aggregation is not enough. The CM360 reporting guide covers each report type, what to use it for and the reasons its numbers will not match the buying platform's.
Further guides
Further guides take on configurations the team did not build:
- Cleaning up an inherited Floodlight configuration — a tutorial that keeps conversion history and live bidding intact while it registers every activity, checks when each last received a tag and what reads it, tests counting and windows against the business question and the tags on the site, replaces rather than renames, fixes custom variables and retires activities in stages with a record in the change log.
How CM360, DV360 and SA360 fit together
CM360 is the measurement spine of Google's advertising stack for large advertisers. The Display & Video 360 hub describes the buying side: DV360 bids for programmatic inventory and can serve its own creatives, but it can also be linked to a CM360 advertiser so that the creatives are hosted in CM360 and the placements, ads and creatives for each DV360 line item are created and kept in sync automatically. The result is that a programmatic buy is counted in the same system, under the same methodology, as a direct buy with a publisher, and both share one Floodlight configuration.
The Search Ads 360 hub covers the search side. An SA360 advertiser links to the same CM360 Floodlight configuration, so a search click and a display impression that preceded the same purchase are visible in one path report rather than counted twice in two tools. This is the practical reason many advertisers keep CM360 even when nearly all their buying is programmatic: it is the only layer that sees display, video, search and direct buys as one journey. It is also why CM360 access and Floodlight configuration tend to be the first things set up when a brand moves onto the stack, before any campaign is built.
One quarter, three buying tools, one count
A furniture retailer runs a spring flight through three routes: DV360 display and video bought in open auction and two preferred deals, a direct homepage takeover with a lifestyle publisher bought on an insertion order, and non-brand search through SA360. All three are served or measured through one CM360 advertiser with a single Floodlight configuration. Across the quarter CM360 records 41.2 million impressions, of which the DV360 line items account for 33.6 million and the direct takeover for 7.6 million. The publisher reports 7.9 million for the takeover; the gap of just under 4% is within the range the team expects and is explained by time-zone cut-offs and page abandonment. Floodlight counts 9,840 purchases with 2,310 attributed to display and video on a last-interaction basis and a further 1,120 where a display impression preceded a search click. Without CM360 the search tool would have claimed all 3,430 and the display tool a large share of the same orders.
Common CM360 problems
Most CM360 problems appear as one of a handful of symptoms. The table maps each to the guide that diagnoses it.
| Symptom | Usual cause | Guide |
|---|---|---|
| Publisher and CM360 impression counts far apart | Tags without a cache buster, wrong tag type, time-zone cut-off, or page abandonment before the tag fires | Ad serving basics |
| Placement live but only the default ad serving | Ad dates, targeting or priority exclude every standard ad, or no creative is assigned | Trafficking workflow |
| Floodlight activity shows no conversions | Tag not deployed, wrong tag strings, consent blocking the tag, or the activity is in the wrong configuration | Floodlight tags; in an inherited account, Cleaning up a Floodlight configuration |
| Conversions counted twice | Sales tag firing on every load of the confirmation page, or the same action tracked by two activities; a tag fired twice, long windows or shared credit | Floodlight conversions counted twice, Floodlight tags; in an inherited account, Cleaning up a Floodlight configuration |
| DV360 and CM360 disagree on impressions | Different counting points and filtering; a sync problem between the linked advertisers | CM360 reporting |
| Reach report lower than the sum of placements | Reach is deduplicated across placements; the sum of impressions is not | CM360 reporting |
| Report arrives empty or truncated | Date range or row count beyond the documented limits of the interface | CM360 reporting |
For how the ad server sits inside the wider ecosystem of exchanges, demand-side platforms and publishers, the programmatic advertising guide is the starting point; this section assumes that picture and teaches the ad server itself.
