Included as a cross-channel ad-serving and measurement control plane for display and video across the web, apps, YouTube, and connected TV, with first-party APIs for trafficking, reporting, attribution, billing, and dynamic creative workflows.
Concrete capability record
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.
Accounts and user profiles; sites and advertisers; Floodlight configurations and activities; campaigns, placements, ads, creatives, and creative assets; billing profiles, assignments, and rates; reports, report files, and direct report data; dynamic feeds and dynamic profiles.
Retrieve authorized trafficking and billing resources; inspect account permissions and user profiles; list campaign, placement, ad, creative, Floodlight, and dynamic-creative state; run file-based reports or query structured report data by dimensions, metrics, filters, and date range.
Insert or update supported advertisers, campaigns, placements, ads, creatives, creative assets, Floodlight resources, billing assignments or profiles, and v5 dynamic feeds or profiles; create, update, schedule, and run supported report definitions.
Every request uses Google OAuth 2.0. The published scopes are dfatrafficking for read/write trafficking, dfareporting for read/write reporting, and ddmconversions for read/write offline conversions. The authenticated CM360 user profile and its UI permissions determine accessible accounts and operations; there are no separate API permissions.
Bind each integration identity to a named CM360 user profile and account, request only the required trafficking, reporting, or conversion scopes, and preserve the account, advertiser, campaign, placement, creative, and Floodlight context in mutation logs and approvals.
The CM360 account must have API access enabled and the user profile must already hold the needed UI permissions. Direct reportData queries allow at most 1,000 rows per page, time out after 60 seconds, and are limited to 120 requests per minute per user and 10,000 per project per day; larger work should use report files. v5 also removes selected report methods and fields documented in its release notes.
First-party access
Agent access
Support: No official MCP server located
Read scope: No first-party MCP read surface verified.
Write scope: No first-party MCP write surface verified.
Authentication: Official CM360 materials reviewed expose OAuth-protected REST APIs but no provider MCP authentication contract. A customer-built adapter would authenticate with Google OAuth 2.0 and the minimum scope set required for trafficking, reporting, or offline conversions.
Approval boundary: Require confirmation before changing campaign dates, placement or creative associations, ad serving state, Floodlight configuration, billing assignments, or report delivery. Display the acting profile ID and account or advertiser context at approval time.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Google ships them.
Evidence and dates
“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.
First-party API reference or API overview recorded for this platform.
Targeted first-party core-access review
First-party developer documentation or platform overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
