Upbuildby Uptimal

Data reference · CM360

Every CM360 metric and dimension you can ask for.

Upbuild reads Campaign Manager 360 the way an ad ops team does: standard report dimensions and metrics for delivery, plus the Floodlight configuration itself, so attribution questions get answered from settings, not folklore. These are the real API names the cm360 report and Floodlight tools use.

51Fields

20Metrics

31Dimensions

0Breakdowns

Source: Campaign Manager 360 API, reports and Floodlight resources · Updated August 2026

51 shown

Delivery metrics

10 fields

The served-media numbers of every CM360 report.

Try it in Claude, ChatGPT or Copilot Studio

Impressions, clicks and media cost by campaign for the last 30 days.

Field	Type	What it is
`impressions`	Metric	Ad impressions served. “impressions by campaign this month”
`clicks`	Metric	Clicks recorded.
`clickRate`	Metric	Clicks divided by impressions.
`mediaCost`	Metric	Media cost booked against the placements. “media cost by site last month”
`plannedMediaCost`	Metric	Cost planned on the placement, for pacing checks.
`richMediaVideoPlays`	Metric	Video starts on rich media and video ads.
`richMediaVideoCompletions`	Metric	Videos played to the end.
`richMediaVideoFirstQuartileCompletes`	Metric	Plays reaching 25 percent.
`richMediaVideoMidpoints`	Metric	Plays reaching 50 percent.
`richMediaVideoThirdQuartileCompletes`	Metric	Plays reaching 75 percent.

Viewability

4 fields

Active View measurement on served impressions.

Try it in Claude, ChatGPT or Copilot Studio

Which placements have viewability under 50 percent this month?

Field	Type	What it is
`activeViewViewableImpressions`	Metric	Impressions measured viewable. “viewability by placement”
`activeViewMeasurableImpressions`	Metric	Impressions Active View could measure.
`activeViewEligibleImpressions`	Metric	Impressions eligible for measurement.
`activeViewPercentageViewableImpressions`	Metric	Viewable share of measurable impressions.

Conversions and Floodlight metrics

6 fields

Conversion counts split by how the user got there.

Try it in Claude, ChatGPT or Copilot Studio

Conversions by Floodlight activity, split click-through vs view-through, last month.

Field	Type	What it is
`totalConversions`	Metric	All Floodlight conversions attributed. “conversions by activity last month”
`activityClickThroughConversions`	Metric	Conversions after a click.
`activityViewThroughConversions`	Metric	Conversions after an impression only.
`activityClickThroughRevenue`	Metric	Revenue attributed post-click.
`activityViewThroughRevenue`	Metric	Revenue attributed post-view. “view-through revenue by campaign”
`totalConversionsRevenue`	Metric	Revenue across both paths where tagged.

Entity dimensions

13 fields

The who-and-where of delivery rows.

Try it in Claude, ChatGPT or Copilot Studio

Top sites by impressions and clicks for campaign X.

Field	Type	What it is
`advertiser`	Dimension	Advertiser name.
`advertiserId`	Dimension	Advertiser ID.
`campaign`	Dimension	Campaign name. “spend and clicks by campaign”
`campaignId`	Dimension	Campaign ID.
`site`	Dimension	Site keyname where the ad served. “impressions by site”
`placement`	Dimension	Placement name.
`placementId`	Dimension	Placement ID.
`placementSize`	Dimension	Creative size booked on the placement.
`ad`	Dimension	Ad name.
`adId`	Dimension	Ad ID.
`creative`	Dimension	Creative name.
`creativeId`	Dimension	Creative ID.
`creativeType`	Dimension	Display, rich media, video and friends.

Floodlight configuration

12 fields

The settings that decide how conversions count: the first place to look when numbers surprise you.

Try it in Claude, ChatGPT or Copilot Studio

Audit our Floodlight activities: counting method, expected URL and lookback windows.

Field	Type	What it is
`floodlightActivity.id`	Dimension	Activity ID.
`floodlightActivity.name`	Dimension	Activity name. “list all Floodlight activities”
`floodlightActivity.countingMethod`	Dimension	STANDARD, UNIQUE, SESSION, TRANSACTIONS or ITEMS_SOLD counting. “which activities use transactions counting”
`floodlightActivity.expectedUrl`	Dimension	URL the tag is expected to fire on.
`floodlightActivity.floodlightActivityGroupId`	Dimension	Parent activity group.
`floodlightActivity.floodlightActivityGroupName`	Dimension	Group name.
`floodlightActivity.tagFormat`	Dimension	HTML, XHTML, IFRAME or IMAGE tag.
`floodlightActivity.status`	Dimension	ACTIVE or archived states.
`floodlightConfiguration.id`	Dimension	The Floodlight configuration the activity lives in.
`lookbackConfiguration.clickDuration`	Dimension	Post-click lookback window, in days. “what are our lookback windows”
`lookbackConfiguration.postImpressionActivitiesDuration`	Dimension	Post-view lookback window, in days.
`floodlightConfiguration.inAppAttributionTrackingEnabled`	Dimension	Whether in-app attribution is on.

Time and environment

6 fields

Report granularity and where the impression happened.

Try it in Claude, ChatGPT or Copilot Studio

Daily conversions by platform type for the last two weeks.

Field	Type	What it is
`date`	Dimension	One row per day. “daily impressions last 14 days”
`week`	Dimension	One row per week.
`month`	Dimension	One row per month.
`platformType`	Dimension	Desktop, mobile web, mobile app, connected TV. “conversions by platform type”
`activity`	Dimension	Floodlight activity on conversion rows.
`activityId`	Dimension	Activity ID on conversion rows.

Good to know

CM360 questions.

Why do CM360 conversions look inflated versus other systems?

Usually configuration, not fraud. When several advertisers share one Floodlight configuration, each can attribute the same conversion, multiplying the total across reports. Auditing the configuration and activity setup, exactly what these tools read, is how you find it.

What decides click-through versus view-through?

The lookback windows on the Floodlight configuration. A conversion inside the click window after a click counts post-click; inside the impression window without a click, post-view. Both windows are readable fields here.

Do the counting methods change the numbers?

Completely. STANDARD counts every fire, UNIQUE once per user per day, SESSION once per session, TRANSACTIONS and ITEMS_SOLD read revenue and quantity variables. Same site behavior, different totals by design.

Can I get report data and configuration in one conversation?

Yes, and that is the point: ask why conversions moved and the assistant can pull the delivery report and the Floodlight settings side by side.

Next

CM360 MCP guide → All platforms → Connect Upbuild in two minutes →