Campaign Manager 360 (CM360)

Google’s independent ad server and measurement layer. The foundation for trafficking, Floodlight conversion measurement and cross-platform attribution.

What it is

Campaign Manager 360 (CM360) sits at the centre of Google’s enterprise advertising ecosystem, connecting campaign delivery with measurement.

At the heart of that measurement is Floodlight, CM360’s conversion tracking technology. Floodlight captures actions such as purchases, leads, registrations and other business outcomes, creating conversion signals that can be used across CM360, Display & Video 360 (DV360) and Search Ads 360 (SA360).

CM360 also manages creative trafficking and ad serving across publishers, providing a consistent layer for measuring campaign activity across channels.

It can also provide log-level Data Transfer data. When connected with BigQuery, this gives organisations a much deeper view of campaign activity, customer journeys and cross-channel performance than standard platform reporting alone.

Why it matters

Marketing performance is often measured across multiple platforms, each with its own attribution methods and reporting rules. That can leave organisations with different versions of the same conversion.

Floodlight provides a common conversion measurement framework across Google Marketing Platform, while CM360 provides the broader infrastructure for ad serving, campaign measurement and attribution.

Getting that setup right matters beyond reporting. Floodlight data can feed audience creation, attribution and automated bidding in platforms such as DV360 and SA360, meaning poor conversion architecture can affect both what marketers see and how campaigns optimise.

That becomes increasingly important as browser restrictions, modelled conversions and privacy changes make platform-reported results harder to compare.

The goal isn’t simply to collect more data, but to create a measurement foundation teams can trust and use to make better decisions.

What Louder does

Floodlight architecture and implementation - designing counters, sales activities, custom variables and conversion rules around the outcomes that actually matter to the business.
Floodlight audits and QA - identifying missing, duplicated or incorrectly configured activities and checking that conversion signals are being captured and passed correctly.
Server-side Floodlight - assessing and implementing server-side approaches where they can improve measurement reliability, signal quality and control.
Account and site structure - advertiser, campaign and placement taxonomy designed for reporting rather than for whoever is trafficking today.
Trafficking and QA - tag generation, placement setup, creative rotation, verification wrapping and a QA process that catches errors before flight.
Data Transfer to BigQuery - log-level reporting, path analysis and cross-platform frequency.
Discrepancy investigation - reconciling CM360, publisher and platform counts and determining what is a genuine measurement problem.
Migration and consolidation - moving from another ad server or bringing fragmented accounts into one environment.

Common challenges

Counters firing on every page load. A Floodlight set to count every conversion where once per session was intended inflates everything downstream, including the bidding in DV360 and SA360 that consumes it.
Discrepancies treated as faults. A single-digit percentage gap between ad server and publisher counts is structural and expected. Investigating it as an error can absorb weeks and produce nothing.
View-through windows left at the default. A thirty-day view-through window in a browser environment that no longer supports the identifiers it depends on produces a number that means something quite different to what it meant when the window was set.
Custom variables never populated. Empty u-variables mean segment and path analysis is impossible after the fact, and there is no way to backfill it.