Update
Campaign Manager 360 — reporting, entity audits and trafficking writes
TL;DR
The ad-server side of Google Marketing Platform. The agent runs CM360 reports directly, audits campaigns, placements, creatives and Floodlight configuration, and can write to exactly five trafficking collections — with measurement infrastructure left deliberately read-only.
What shipped
- The full CM360 reporting lifecycle, using the current API's plain-named dimensions and metrics.
- Entity reads for campaign, placement, creative and Floodlight audits, plus change-log forensics.
- Trafficking writes restricted to five collections: campaigns, placements, ads, creatives and advertiser landing pages.
- Archive-not-delete semantics, matching what CM360's API actually supports, with new ads created inactive.
Why the write surface is narrow
Floodlight is measurement infrastructure that every campaign's conversion tracking depends on. Letting an agent modify it would risk breaking attribution across everything, for a task that almost never needs it — so it stays read-only while the trafficking layer is writable.
Frequently asked questions
- Can the agent delete a CM360 campaign?
- No — CM360's API has no delete for trafficking entities. The correct operation is archiving, which is what the agent does.
- Can it modify Floodlight configuration?
- No, deliberately. Floodlight is measurement infrastructure and stays read-only; only the five trafficking collections are writable.