Campaign Manager 360 (CM360)

Google’s independent ad server and measurement layer. The foundation for trafficking, Floodlight 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.

It manages creative trafficking and ad serving across publishers, while Floodlight captures conversions, revenue and other business signals that can be used across platforms including DV360 and Search Ads 360.

CM360 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.

CM360 provides a consistent measurement layer across media, helping teams establish clearer reporting rules and better understand performance across channels.

That becomes increasingly valuable as automated bidding, modelled conversions and privacy changes make platform-reported results more difficult 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

Account and site structure - advertiser, campaign and placement taxonomy designed for reporting rather than for whoever is trafficking today.
Floodlight architecture - what is a counter, what is a sale, what the custom variables carry, and which platforms are permitted to consume which activity.
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 deciding what is a real problem.
Migration and consolidation - moving from another ad server, or bringing fragmented accounts into one.

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.