CM360 MCP: floodlights and placements, minus the console

Written by Uptimal, the team that builds and operates Upbuild and runs marketing analytics for multinational clients across the globe. Everything below reflects how the connector actually behaves in production.

Campaign Manager 360 is where large advertisers’ ad-server truth lives: placements, creatives served, and above all floodlight conversions. Upbuild’s CM360 family, built around tools like cm360_run_report, lets an assistant pull that reporting through your user profile, read-only, without waiting on the offline report scheduler.

Ask the ad server directly

• “Floodlight conversions by activity for last month, split by placement.”
• “Which placements delivered under 90% of booked impressions?”
• “Reach and frequency for the brand campaign, by week.”

The floodlight trap we see in real audits

Floodlight configurations can be shared across advertisers. When they are, activity-level counts can include conversions attributed under sibling advertisers, and a naive report reads several times higher than the business reality. We have diagnosed exactly this multiplying a retailer’s reported conversions by around six. The connector’s job is to keep advertiser and configuration IDs explicit so the assistant can ask the disambiguating question instead of averaging over a mess; if your CM360 numbers have ever disagreed with GA4 by an implausible factor, this is the first thing to check.

CM360 sits naturally beside DV360 (the buying side of the same Google stack) and GA4 for triangulating conversion truth. Access uses your existing CM360 user profile through the standard Google sign-in.

Frequently asked questions