Google

Campaign Manager 360

Curated major addition platform in ad serving and measurement with material relevance to the Marcom operating stack and a first-party developer surface.

Advertising & media buyingSystem of engagementExtensible SaaS
System roleSystem of engagement
Access maturityExtensible SaaS
Agent postureNo first-party provider verified
Reference updatedJun 11, 2026
BYO-UI reviewedJul 10, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Accounts, user profiles, advertisers, campaigns, placements, ads, creatives, creative assets, Floodlight configurations and activities, billing objects, and reports.

02 · Data you can retrieve

List and retrieve trafficking objects; run and retrieve attribution, reach, conversion-path, and other reports with documented dimensions, metrics, and filters.

03 · Actions and write paths

Create and update advertisers, campaigns, placements, ads, creatives, assets, and other supported trafficking resources; execute report workflows.

04 · Authentication and permissions

Google OAuth 2.0 scopes and the Campaign Manager 360 account user-profile permissions apply.

05 · Monitoring, approval, and recovery

Preserve advertiser/account boundaries, Floodlight definitions, attribution assumptions, creative approvals, and an immutable record of trafficking changes.

06 · Gaps and implementation limits

No first-party provider MCP was verified. API quotas, object-specific constraints, and account permissions apply; some campaign economics remain outside CM360.

Agent access

MCP and adjacent posture

No first-party provider MCP verified in this snapshotNo first-party provider MCP foundNo first-party provider verified

Role: none_verified

Read scope: No first-party MCP read surface verified.

Write scope: No first-party MCP write surface verified.

Authentication: Not applicable to a first-party MCP provider.

Approval boundary: Any customer-built adapter must define its own approval and confirmation controls.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access1
Identity4
Governance4
Agent access1
UI extensibility4
Portability3
Observability3
Documentation4

Proposed interfaces

What customers could build on top.

These are design proposals derived from documented access—not claims that Google ships these experiences.

Single-platform patterns

  • Cross-publisher trafficking and measurement console
  • Campaign exception cockpit
  • Creative and policy review queue
  • Budget pacing workbench
Use in the brief composer →

Multi-platform compositions

  • Campaign Manager 360 + CRM or revenue system: campaign exception cockpit
  • Campaign Manager 360 + analytics or warehouse + creative-production platform: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

3 recorded sources
Developer docsSource inventory
https://developers.google.com/doubleclick-advertisers ↗

First-party developer documentation or platform overview.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Verified fact

Tied to the representative first-party source or targeted access review.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.