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

Programmatic Advertising › Campaign Manager 360

CM360 Reporting

How to report from Campaign Manager 360: standard reports, Floodlight and path-to-conversion reports, reach and verification reports, scheduling and transfer.
Guideintermediate9 min readUpdated

Report types

Report Builder offers a small set of report types, each built for a question the others answer badly. Choosing the right type is most of the work; the dimensions and metrics inside it follow from the choice.

Report typeQuestion it answersTypical use
StandardWhat was served, clicked and converted, by any combination of advertiser, campaign, site, placement, ad, creative and dateWeekly delivery and pacing, invoice reconciliation, creative performance
FloodlightHow many times each activity fired and which media was credited, split into click-through and view-throughConversion reporting, cost per action, revenue from sales tags
Path to conversionWhat sequence of impressions and clicks preceded each conversion, and how long it tookChannel interaction, assisted conversions, window decisions
ReachHow many unique browsers saw or clicked the ads and how often, deduplicated across the chosen dimensionsPlanning frequency caps, judging whether a flight widened or deepened
Cross-dimension reachHow much the audiences of two dimension values overlap, such as two sites or two placementsDeciding whether a second publisher adds people or repeats them

Instant reporting, a lighter interface documented alongside Report Builder, answers quick questions over a recent window without building a saved report. The verification area is separate from Report Builder and is covered below. For reporting from the buying side, the DV360 reporting guide covers the platform that bought the media; its numbers and CM360's will differ for reasons set out in each section here.

Standard reports and dimensions

A standard report is a table: dimensions down the side, metrics across, a date range and optional filters. The dimensions mirror the trafficking hierarchy, which is why clean naming at trafficking time pays off here: advertiser, campaign, site, placement, placement group, ad, creative, plus date, browser, platform, country and the other request attributes CM360 records. Metrics begin with impressions, clicks and click rate, extend to Active View columns for viewable and measurable impressions, video metrics for in-stream creatives, rich media interactions for Studio creatives, and the Floodlight columns for total, click-through and view-through conversions and for revenue from sales activities.

The documented behaviours that trip people up are worth stating. Report Builder applies limits on the date range a report can span and the number of rows it returns; the help centre documents both, and a report that comes back truncated has usually hit one of them. Metrics are reported in the account's time zone, so a comparison with a publisher or a platform set to a different zone needs a day-boundary adjustment before anyone argues about the total. Floodlight metrics in a standard report are attributed under the activity's windows and the default model; they are counts of credited conversions, not raw activity firings.

A useful discipline is to build a small set of saved standard reports per advertiser, each tied to a question and a key performance indicator (KPI): delivery against plan by placement and day, creative performance by ad and creative, and a reconciliation report at placement and date grain for the invoice. Saved reports keep their dimensions and filters, so the Monday report is the same table every Monday and the trend is readable.

Floodlight and path reports

The Floodlight report type puts the activity at the centre. Its dimensions include the Floodlight configuration, activity group and activity, with the click-through and view-through split as separate columns, and the custom Floodlight variables defined on the configuration available as dimensions or, for number-typed variables, as metrics. Revenue and quantity from sales activities appear here, which makes this the report for cost per action and return calculations at activity level. Read it alongside the Floodlight tags guide because every column depends on how the activity was designed: the counting method decides what one conversion is, and the windows decide which media gets the credit.

The path-to-conversion report changes the unit from the conversion to the sequence before it. Each row is a conversion and the interactions that preceded it within the lookback window, with dimensions for the number of interactions in the path, the time from first interaction to conversion, the interaction type and the channel or placement at each position. It is the only report in the stack that shows a search click and a display impression on the same row, which is why advertisers who buy through several routes keep CM360 even when a buying platform could report on its own. The Attribution models that CM360 documents, from last interaction through to data-driven and custom models, are applied in the attribution tools and in path reports to redistribute credit across those positions. The model is a reporting choice, not a counting one; changing it moves credit between placements without changing how many conversions exist.

Reach and verification reports

Reach reports count browsers rather than serves. A reach report over a set of placements and a date range returns impression reach, click reach and the average impression frequency for the combination, with the deduplication done across every dimension in the report. That is why the reach total is lower than the sum of placement reach values and why the (Reach) and (Frequency) figures cannot be derived from a standard report by arithmetic. The cross-dimension reach report takes two dimension values, such as two sites, and reports the exclusive reach of each and the overlap, which is the evidence for whether a second placement added people or added frequency.

Google documents the basis of these counts: they are cookie-based and therefore counted per browser and device rather than per person, and they are affected by the browser restrictions and consent states that limit cookies. A reach report is an honest count of what the ad server could see, which is not the same as the people who saw the ad. The cross-platform reach and frequency guide covers how to read reach when the same campaign runs in platforms that cannot see each other's browsers.

Verification lives in its own area of CM360 rather than in Report Builder. It reports whether tags are live and serving as expected, the content classification and geography of the pages that requested ads, Active View viewability and measurability, and impressions that were blocked. Viewability columns also appear in standard reports, so the daily pacing report can carry the viewable rate without a separate pull; the verification area is for the investigation when a rate drops or a placement serves somewhere it should not.

Illustrative example — not a real result

Reading one flight through four reports

A travel insurer runs a six-week flight across three publishers and a DV360 line, all served through CM360. The standard report shows 28.4 million impressions and 61,000 clicks, with the DV360 line delivering 19.1 million of the impressions at a viewable rate of 68% against the publishers' 74%. The Floodlight report shows 3,120 quotes started and 940 policies bought, with view-through accounting for 2,210 of the quotes and 410 of the policies. The reach report returns 9.6 million browsers at an average frequency of just under three, well under the cap of eight the team set, so the frequency cap did not bind. The cross-dimension reach report shows a 41% overlap between the two largest publishers, which the planner uses to drop the smaller of the two from the next flight and move its budget to the DV360 line, where exclusive reach was highest. Verification shows the third publisher serving 6% of impressions on pages classified outside the agreed categories; the placement is paused and the publisher credits the impressions.

Scheduling and sharing

Every saved report can be scheduled. CM360 documents daily, weekly and monthly frequencies with a start and end for the schedule, a relative date range such as the previous week so that each run covers the right period, and delivery by email to a list of recipients in the formats the interface supports. Reports can also be shared with other users of the account, who then see the same definition and can run it themselves; sharing the definition rather than the file keeps everyone on one table.

Three habits make schedules reliable. Use relative date ranges and never a fixed one, or every run after the first repeats the same period. Name the report for the question and the audience rather than the date it was built, because schedules outlive their builders. And keep the recipient list to people who act on the table; a scheduled report that nobody opens is still a report someone is responsible for when its numbers are wrong. Where the organisation reports in a business intelligence tool, a scheduled export into a shared location is often enough, and the DV360 reporting guide describes the equivalent on the buying side so that the two land in the same place.

Data transfer to a warehouse

Data Transfer is CM360's log-level export. Google documents it as a set of files delivered to a Google Cloud Storage bucket on a schedule, containing one row per impression, click, rich media event and Floodlight activity, together with match tables that translate the identifiers in those files into the names of campaigns, placements, ads, creatives and activities. The files are designed to be loaded into BigQuery, and Google documents a transfer service that automates that load. Once there, a data team can join the ad server's events to each other and to first-party data: impressions to conversions by browser for a custom attribution model, exposure counts for a frequency analysis the reach report cannot express, or media cost from the buying platform against Floodlight revenue at a grain the interface never offers.

The trade-offs are real. The files are large, they arrive on their own schedule rather than on demand, the schema is documented but changes over time, and the identifiers in them follow the same cookie and consent limits as every other CM360 count. The help centre documents how long files remain available in the bucket and the retention of the underlying data; plan the load to run within that window. Data Transfer suits an advertiser with a standing analytical question and a team to maintain the pipeline; for everyone else, saved and scheduled reports from Report Builder answer the question sooner. The Campaign Manager 360 hub sets out how these reports sit beside the serving and Floodlight layers they describe.

Common mistakes

  • Comparing CM360 to the buying platform for equality. Different counting points, filtering and time zones make a gap normal; investigate the trend, not the existence.
  • Reading Floodlight columns in a standard report as raw firings. They are credited conversions under the activity's windows and the default model.
  • Adding placement reach values to get campaign reach. Reach only deduplicates inside one report; build the report at the level the question asks.
  • Fixed date ranges on scheduled reports. Every run repeats the first period.
  • Changing the attribution model and announcing more conversions. The model moves credit; it cannot create a conversion that was not counted.
  • Ignoring the row and date-range limits. A truncated report looks complete and is not.
  • Starting Data Transfer without a question. The pipeline costs more than the reports it replaces unless a defined analysis needs event-level rows.

Frequently asked questions

Why is the reach report lower than the impressions in the standard report?

Impressions count every serve, so a browser that saw the ad many times contributes many impressions. Reach counts each browser once across the placements and dates in the report, so the same activity contributes one unit of reach and several units of frequency. The two reports answer different questions and should not be expected to add up.

Should attribution be read from CM360 or from DV360?

Read the raw activity counts from CM360, because it sees every buying route that shares the Floodlight configuration, and read platform-attributed counts from the platform that made the buy. DV360 and SA360 each attribute conversions to their own media under their own rules, so their counts are shares of the CM360 total rather than alternatives to it. Comparing the two shows how much of the conversion volume each channel touched.

When is Data Transfer needed rather than a scheduled report?

When the question needs event-level detail that aggregation hides: a custom attribution model, a frequency analysis that joins impressions to conversions per browser, or a join with first-party data in a warehouse. Scheduled reports cover most reporting needs and are far simpler to run. Data Transfer adds engineering work and a data team to maintain it, so it should be adopted for a defined question rather than in case one arrives.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. Campaign Manager 360 Help — Google

Related