AI agent for Campaign Manager 360: ad-server reporting and entity audits
The agent connects to Campaign Manager 360 over the same Google OAuth login used for Google Ads and DV360 — one connection carries every CM360 user profile your login holds. It reads the ad-server side of your stack: campaigns, placements, creatives and Floodlight activities, plus the full CM360 Reporting lifecycle (create, run and parse reports on demand), so delivery, reach and conversion numbers from the ad server line up against what Google Ads and DV360 claim. Reads and reporting run immediately; trafficking writes are approval-gated — nothing changes in your ad server without a human saying yes.
What the agent does with Campaign Manager 360
- Reads campaigns, placements, creatives and Floodlight activities across every user profile on the connection.
- Runs the full CM360 Reporting lifecycle on demand — builds the report, runs it and parses the result into an answer, not a CSV attachment.
- Audits entity hygiene — expired flights still trafficked, inactive placements, creatives past their end dates, silent Floodlight activities.
- Reconciles ad-server delivery against Google Ads and DV360 buying data for a served-vs-billed view.
- Proposes trafficking changes — every write pauses for human approval before it touches the ad server.
Real use cases
CM360 is the measurement backbone of a Google Marketing Platform stack — the numbers of record when buying platforms disagree. These are realistic goals for a connected CM360 profile.
| Goal you'd type | What the agent does |
|---|---|
| "Build a last-30-days delivery report — impressions, clicks, conversions by campaign and placement." | Creates and runs the CM360 report with those dimensions, parses the result, and returns the breakdown with outliers flagged. |
| "Audit our active campaigns for trafficking hygiene issues." | Reads campaigns, placements and creatives and flags expired flights, inactive placements and similar entity problems worth cleaning up. |
| "Do our Floodlight conversions line up with what Google Ads is reporting?" | Pulls Floodlight activity data from CM360 and conversion data from Google Ads, lines them up, and quantifies the attribution gap. |
| "Which placements served fewer than 1,000 impressions last week?" | Runs the placement-level delivery report and surfaces the under-delivering placements worth investigating or removing. |
Guardrails
- Reads and reporting run immediately; trafficking writes are approval-gated — a human signs off before anything changes in the ad server.
- One Google OAuth connection covers CM360 alongside Google Ads and DV360 — same per-organization credential isolation, no separate login.
- Reports are created, run and parsed by the agent — you get the answer, and the underlying report definition stays inspectable in CM360.
Frequently asked questions
- Can the agent change my CM360 trafficking setup?
- Only with your approval. Reads and reporting run immediately; any trafficking write is proposed first and pauses for a human sign-off before it applies to the ad server.
- What's the difference between CM360 and DV360?
- DV360 is the buying platform (programmatic bidding and budgets); Campaign Manager 360 is the ad server and measurement layer that serves creatives and counts delivery across buys. The agent connects both, separately, over one Google login.
- Do I need a separate login to connect CM360?
- No — CM360 reuses the same Google OAuth connection as Google Ads and DV360, and one connection carries every CM360 user profile your login has access to.
- Can it audit our Floodlight setup?
- Yes — it reads Floodlight activities and configuration, flags silent or misassigned activities, and can reconcile Floodlight conversion counts against your buying platforms' reported conversions.