Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

CM360

Ad server and measurement platform.
Campaign Manager 360Ad TechtechnologyUpdated

Definition

Campaign Manager 360 is described in its help centre as a web-based ad management system for advertisers and agencies that helps manage digital campaigns across websites and mobile, with ad serving, targeting, verification and reporting. An ad server on the advertiser side stores creatives, decides which to show when a placement calls for one, counts the impression and the click, and records conversions via its own tags. The point is independence: the publisher or DSP reports what it sold; the ad server reports what it served. The registry summary names the three jobs, third-party ad serving, Floodlight tracking and cross-channel reporting, and the Campaign Manager hub explains each. The ad serving basics guide covers the mechanics for readers new to ad servers.

How it works

Trafficking is the setup work. An advertiser in CM360 holds campaigns; each campaign holds placements, one per site or platform and ad size, and ads that assign creatives to placements with rotation, dates and targeting rules. Generating a placement produces a tag that the publisher or DSP inserts; when the slot loads, the tag calls CM360, which selects an ad, records an impression, and returns the creative or a redirect to it. Clicks route through CM360 before the landing page, so the click is counted on the way.

ObjectRole
AdvertiserOwner of campaigns, creatives and the Floodlight configuration
CampaignFlight with its placements, ads and default landing page
PlacementThe slot on one site or platform, with size and pricing fields
AdWhich creatives serve in a placement, with rotation and targeting
CreativeThe asset itself: image, rich media, video, tracking-only
Floodlight activityA conversion to count, with its tag and counting method

Floodlight is the conversion side. A Floodlight configuration belongs to the advertiser; activities within it define the actions to count, with counter activities for events and sales activities for transactions with a value. The Floodlight tag, now usually deployed through the Google tag or Tag Manager, fires on the site, and CM360 matches the conversion to the impressions and clicks it served within the lookback window. The Floodlight tags guide covers implementation. Verification checks where ads served: geography, content classification, viewability through Active View, and blocking rules. Reporting in Report Builder provides standard, reach, path-to-conversion and Floodlight reports, with data transfer files available for warehouse-level analysis.

In practice

CM360 is adopted when creatives run in more than one place and the advertiser needs a count that is not the seller's: direct publisher buys alongside programmatic, several DSPs, or a search programme measured on the same conversions as display. It also carries frequency and sequencing across those sources, and it is the system of record when a publisher invoices against delivered impressions. Smaller advertisers buying through one platform rarely need it; the platform's own serving and reporting suffice until a second buying route appears and the two counts have to be reconciled.

Illustrative example — not a real result

Reconciling publisher and ad server counts

An insurer runs a direct buy with a news publisher for 2,000,000 impressions at a £9 CPM, trafficked through CM360 with a sales Floodlight activity on its quote-complete page. At the end of the month the publisher's report shows 2,040,000 impressions; CM360 shows 1,910,000, a 6.4% discrepancy, within the tolerance the contract sets at 10%. Report Builder's Floodlight report attributes 1,240 quotes to the placement, 310 click-through and 930 view-through within a 30-day window; the path-to-conversion report shows that 42% of those quotes also had a paid search click, which the agency uses to argue for a lower view-through weight when the publisher invoices against conversions.

What it is not

Campaign Manager is not a buying platform: it holds no budget, places no bids and buys no inventory; DV360, Google Ads and direct insertion orders do that. It is not a publisher ad server, which is Google Ad Manager's role on the sell side; the two count the same impression from opposite ends, and reconciling them is routine. It is not an analytics tool; Floodlight counts conversions it can match to served ads, not site behaviour in general. It is not an attribution product, even though its path-to-conversion report shows the sequence of served touchpoints before a conversion; the help centre is the reference for which attribution features remain in the product. And it is not required to use DV360 or SA360, though both are more useful with it.

DV360 is the buying platform most often paired with CM360: DV360 line items can serve creatives trafficked in Campaign Manager, and the Floodlight activities defined here are the conversions DV360 bids toward. SA360 uses the same Floodlight configuration on the search side, which is what makes one conversion count span search, display and video. Attribution is the question the path-to-conversion report answers partially: given the impressions and clicks CM360 served before a Floodlight conversion, which gets credit under which rule. The limits of that answer, walled gardens whose impressions it cannot see and the decline of cross-site identifiers, are the reason ad server attribution is read alongside platform-neutral approaches rather than instead of them. Google Ad Manager is the publisher-side counterpart whose counts CM360 is most often reconciled against.

Common mistakes

  • Trafficking without a naming convention. Placement names are what every report groups by; name them for site, format, size and audience from the start.
  • Floodlight tags firing on the wrong pages. A sales activity on every page overstates conversions and misleads every connected bid strategy.
  • Ignoring the discrepancy. A gap between seller and ad server counts beyond the agreed tolerance is a billing issue; check it monthly.
  • Reading view-through as caused. The ad server proves the impression came first; it cannot prove it mattered.
  • One lookback window for every activity. Considered purchases and impulse actions warrant different windows; set them per activity.
  • Forgetting consent and tag updates. Legacy Floodlight tags that ignore consent signals under-count or breach policy; migrate to the Google tag.

More terms to look up

Where this term is used

Sources

  1. Campaign Manager 360 Help — Google

Related