Below are the measures and dimensions that ChannelMix considers standard for the Placement Unique Reach dataset. There is a 1 day lag for available data and the last 30 days of data will be pulled every day.
ChannelMix applies the "Last 30 Days" relative date range model to this dataset and this can be adjusted to "Last 7 Days", "Week to Date", "Month to Date", "Last 90 Days", "Yesterday", or "Today" upon request. The relative date range applies to how the unique reach is calculated and this means that the reach can only be considered unique within the last 30 days for our standard dataset.
Please review the below limitations around the Reach Report from Google Campaign Manager (Google Documentation here):
- A NULL value for any metric in the Unique Reach report means that the reach model couldn't be calculated because there wasn't enough data, or it didn't meet Google's privacy requirements. Try running your report over more data. You can also try segmenting your data less (over fewer dimensions). The more impressions available, the more likely it is the model will return data.
- Reach data can't be summed or compared across reports. For example, the reach of line items and insertion orders can't be summed to determine the reach of a campaign.
- Cumulative reach data is available for 93 days as of November 1, 2018. Reach information can be pulled (at maximum) in 93 day blocks, and these blocks can't be added together accurately. Cumulative reach data prior to this date can be as little as 42 days.
- Because reach data is limited and can't be added together, available dimensions within reach reports are also limited.
This is an activate-able dataset through the ChannelMix Control Center.
|Field Name||Field Type||Description|
|Date||DATE||The date the activity occurred|
|Advertiser ID||STRING||Advertiser ID|
|Campaign ID||STRING||Campaign ID|
|Package/Roadblock ID||STRING||Package/Roadblock ID|
|Placement ID||STRING||Placement ID|
|Platform Type||STRING||The platform description.|
|Site||STRING||The site where the ad was served.|
|Country||STRING||The country to which the reach applies. This field is required by GCM.|
|Impressions||INTEGER||Number of times the ad was served.|
|Clicks||INTEGER||Number of times the ad was clicked.|
|Unique Click Reach||INTEGER||The estimated number of unique users (across devices) who clicked an ad during the reporting period. The click estimate is based on unique cookies, mobile device IDs, and aggregated sign-in data.|
|Unique Impression Reach||INTEGER||The estimated number of unique users (across devices) who saw an ad during the reporting period. The impression estimate is based on unique cookies, mobile device IDs, and aggregated sign-in data.|
|Unique Total Reach||INTEGER||The estimated number of unique users (across devices) who saw or clicked an ad during the reporting period. The total estimate is based on unique cookies, mobile device IDs, and aggregated sign-in data.|
|Unique Reach Average Impression Frequency||FLOAT||The average frequency at which an ad is seen by unique users (across devices) during the reporting period. A frequency of 1 means that, on average, users saw your ad once. A higher average means that more users saw your ads multiple times. The user estimate is based on unique cookies, mobile device IDs, and aggregated sign-in data.|
|Insert Date||TIMESTAMP||ChannelMix Field - When the row was inserted into ChannelMix.|
|ChannelMix Profile||STRING||ChannelMix Field - The descriptive name assigned to this data segment.|