Can an AI agent run Campaign Manager 360 reports automatically?

Yes — it runs CM360's own reporting API directly, with the metrics and date range you specify, rather than requiring a manually built and scheduled saved report.

What can an AI agent write in CM360?

Only five collections: campaigns, placements, ads, creatives and advertiser landing pages. Floodlight configuration, user roles, subaccounts and conversion data are read-only, enforced at the path level.

Why compare CM360 numbers against Google Ads or DV360?

Because CM360 functions as the neutral ad-server record across buying platforms — reconciling its numbers against a specific DSP's self-reported figures is the actual reason most teams run CM360 reporting in the first place.

Does CM360 report cost in the same currency units as the UI?

The underlying API returns cost in nanos (rateOrCostNanos); an agent should convert this to major currency units on read so the numbers you review match what you'd see in the CM360 UI directly.

Is CM360 audit and reporting automation different from DV360 automation?

Yes — CM360 is the ad-server/measurement layer with a narrow five-collection write surface, while DV360 is the buying platform itself, with a much broader set of writable entities (insertion orders, line items, targeting). They're commonly used together, not interchangeably.

Playbooks

How to automate Campaign Manager 360 (CM360) reporting and ad-server audits with an AI agent

TL;DR

Campaign Manager 360 sits above individual buying platforms as the neutral ad-server record — which is exactly why its reports get pulled into a spreadsheet so often: reconciling CM360's numbers against what Google Ads or DV360 report is a recurring, mechanical task. An AI agent can run CM360's own reporting API directly, audit specific entity collections, and propose scoped changes — all gated the same way as every other connected platform.

Two distinct CM360 workflows

Workflow	What it covers
Reporting	Standard and saved CM360 reports — impressions, clicks, cost, activity/floodlight data — with relative or fixed date ranges
Entity audits & writes	Campaigns, placements, ads, creatives and advertiser landing pages — read any collection, write only these five

CM360's write surface is deliberately narrow: campaigns, placements, ads, creatives and advertiser landing pages are writable; floodlight configuration, user roles, subaccounts and conversion data are read-only from the agent, by design — the trafficking layer, not the measurement-integrity layer.

A concrete reporting-automation goal

1"Pull this month's CM360 report for [campaign] — impressions, clicks, cost, activity conversions." The agent runs the CM360 report directly with the relative date range you specify.
2"Compare that against what Google Ads reports for the same campaign." The agent reads both platforms in the same run and reconciles the numbers side by side — the actual point of running CM360 as your ad-server system of record.
3"Flag any placement with cost but zero recorded activity." A specific, checkable audit condition against the placements collection.
4"Pause the flagged placements." A scoped write against one of the five writable collections — shown in full before it applies, and pausing for your approval.

Why cross-platform reconciliation is the real use case

CM360 exists precisely because a single buying platform's self-reported numbers aren't always the number you plan against — DV360, other DSPs and direct buys all report into the same ad server. An agent that reads CM360 in the same run as the buying platforms it's meant to reconcile against turns a recurring spreadsheet exercise into a repeatable, on-demand question, with the actual report data behind every number it states.

Guardrails specific to CM360

Writes are restricted to campaigns, placements, ads, creatives and advertiser landing pages — every other collection is read-only, enforced at the path level, not just by convention.
A profile-level fence rejects any path naming a different user profile than the one your connection resolves to.
Cost fields (rateOrCostNanos) are converted to major currency units on read, so what you review matches CM360's own reporting UI.
Every write pauses for approval before it applies — no different from Google Ads, DV360, or any other connected platform.

The rest of what the CM360 agent does

Reporting and reconciliation is one workflow among several — see the full CM360 platform page for entity discovery and trafficking detail, or the best AI agent for Campaign Manager 360 for how to evaluate this category of tool.

Frequently asked questions

Can an AI agent run Campaign Manager 360 reports automatically?: Yes — it runs CM360's own reporting API directly, with the metrics and date range you specify, rather than requiring a manually built and scheduled saved report.
What can an AI agent write in CM360?: Only five collections: campaigns, placements, ads, creatives and advertiser landing pages. Floodlight configuration, user roles, subaccounts and conversion data are read-only, enforced at the path level.
Why compare CM360 numbers against Google Ads or DV360?: Because CM360 functions as the neutral ad-server record across buying platforms — reconciling its numbers against a specific DSP's self-reported figures is the actual reason most teams run CM360 reporting in the first place.
Does CM360 report cost in the same currency units as the UI?: The underlying API returns cost in nanos (rateOrCostNanos); an agent should convert this to major currency units on read so the numbers you review match what you'd see in the CM360 UI directly.
Is CM360 audit and reporting automation different from DV360 automation?: Yes — CM360 is the ad-server/measurement layer with a narrow five-collection write surface, while DV360 is the buying platform itself, with a much broader set of writable entities (insertion orders, line items, targeting). They're commonly used together, not interchangeably.