Ad Manager report dimensions
Below are all of the dimensions available in Ad Manager reports, along with information about applicable report types and categorization. Filter the table with one or more keywords to search for dimensions.
Impression counting method
Impressions and viewability related metrics are only accredited for specific impression counting methods.
You can filter your report by:
- Impression counting method Begin to render.
Methods other than "Begin to render" aren't MRC accredited for impressions and viewability based metrics.
Dimension | Report type and metric category |
---|---|
Audience segment (billable) Name of billable Audience segment. This includes both first-party and third-party segments used for billing purposes. Helps understand how impressions are allocated on your Ad Manager invoice. Learn more about how audience segment billing works. | Historical Audience, Looker Studio Connector |
Data partner Name of Audience segment data partner. If the segment is first-party, your Ad Manager network name is displayed. | Historical Audience, Looker Studio Connector |
Audience segment (targeted) Name of targeted audience segment, including all first-party and third-party segments that matched the user on the winning line item. | Historical Audience |
Age
User age. Possible values (in years):
| Analytics Analytics |
App version
The version string of the app. This dimension in Historical report type only applies to backfill traffic that is newer than November 18, 2023. | Historical, Analytics Platform, Analytics |
Domain
Shows performance by top domain, such as "example.co.uk". Excludes subdomains. | Historical, Analytics Platform, Analytics, Looker Studio Connector |
Gender
User gender based on inferred behavior and interests. Possible values:
| Analytics Analytics |
Operating system & version Note: Non-mobile app impressions are always classified as "Unknown." | Analytics Analytics |
Screen class
The code class of the screen. | Analytics Analytics |
Screen name
The name of the screen. | Analytics Analytics |
Event name
| Analytics Analytics |
Browser “In-app browser” is a browser embedded within an app. | Historical, Analytics Platform, Analytics, Looker Studio Connector |
Interests
Shows categories of user interests, such as sports. | Analytics Analytics |
Page path
The navigation users followed to the page. | Analytics Analytics |
Page title and screen class
The title of the viewed page and the class of the device's screen the page was viewed on. | Analytics Analytics |
Page title and screen name
The title of the viewed page and the name of the device’s screen the page was viewed on. | Analytics Analytics |
Platform
The type of platform used, such as Android, iOS, or web. | Analytics Analytics |
Stream name
The name of the stream. | Analytics Analytics |
Bid range
The range within which the bid falls, divided into $0.10 buckets. | Historical Bids (Beta) |
Bid rejection reason
Reason the bid lost or did not participate in the auction. Possible values include:
| Historical Bids (Beta) |
Protected Audience seller (non-Google) The origin of a non-Google seller you partner with to get impressions through Protected Audience. | Historical Delivery |
TCF vendor (Deprecated) Any ad technology provider name value returned here is representative of bid rejections specific to that ad technology provider, while a value of "(Not applicable)" indicates no bid rejections due to one or more ad technology providers. Combine this dimension with the "Bid rejection reason" dimension for more insights. | Historical Delivery |
TCF vendor ID (Deprecated)
The ID of the ad technology provider as it appears on the Global Vendor List (GVL). Only appears in the exported version of a report. | Historical Delivery |
Advertiser The name of the advertiser company assigned to an order. Select dimension attributes to display labels, advertiser type, and more. | Historical, Future sell-through, Reach, Technical ad delivery (Beta) Delivery, Looker Studio Connector |
Activity (Deprecated) Name of individual Activity. Reports only historical data after its deprecation on February 22, 2024. | Historical Delivery, Looker Studio Connector |
Activity group (Deprecated) Reports only historical data after its deprecation on February 22, 2024. | Historical Delivery, Looker Studio Connector |
Creative
Creative that served to the ad slot request. Select dimension attributes to display click-through URL, SSL scan results, or custom fields. When the Creative dimension is used to generate and download a report, the Creative ID column may contain either Creative.id or creative set id (master's Creative.id) if the creative is part of a creative set. Learn more
| Historical Delivery, Looker Studio Connector |
Creative size (Deprecated) When the Creative size dimension is included in a report, companion delivery that is otherwise rolled up under master delivery is surfaced, so you may see higher totals than expected. This dimension is deprecated. Use "Creative size (delivered)" instead. | Historical Delivery |
Creative size (delivered)
Any other values show as "Unknown". Note: This dimension can't appear in the same report as the "Unfilled impressions" metric. They are incompatible. Ad Exchange impression numbers reported using this dimension may differ from the legacy "Creative Size" dimension due to how "Creative Size (delivered)" counts some Google Ads text ads. How this dimension differs from "Creative size":
| Historical Delivery |
Creative type Type of creative that served to the ad slot request. Values include:
Audio ads: Many creative types include audio ads. To see a breakdown of audio ads, you can also include a size dimension. | Historical Delivery, Looker Studio Connector |
Secure signal delivery (Beta)
Secure signal sharing is a processor feature that lets publishers pass obfuscated signals (such as user IDs) to third-party bidders on RTB bid requests. Shows how including secure signals and sending them to bidders can impact metrics, such as Total impressions and Total CTR. Likely, the Bidder hasn't chosen to receive the signal(s) if you see a combination of:
| Historical Delivery |
Impression counting method
The method used for counting impressions. Possible values include:
Sometimes, there may be discrepancies or negative numbers when the impression counting method dimension is used. This can occur when a begin-to-render ping is received, but a downloaded ping is not received. | Historical Delivery, Looker Studio Connector |
Line item The name of the line item associated to the Creative that served to the ad slot request. Select dimension attributes to display quantity, cost type, delivery indicator, and other information. Reservation traffic for this dimension may return a dash (-) in reporting. The dash can indicate delivery via inventory sharing. | Historical, Future sell-through, Reach, Technical ad delivery (Beta) Delivery, Looker Studio Connector |
Line item type Type of line item associated to the Creative that served to the ad slot request. Reservation traffic for this dimension may return a dash (-) in reporting. The dash can indicate delivery via inventory sharing. | Historical, Future sell-through, Reach Delivery, Looker Studio Connector |
Master and Companion creative For video master and companion creatives, master ads play within the video player; companion ads, usually display, serve to non-video ad slots in conjunction with the master. | Historical Delivery, Looker Studio Connector |
Active View measurement source
| Historical Delivery |
Order The name of the Order associated to the line item linked to the Creative that served to the ad slot request. Select dimension attributes to display labels, salesperson, traffickers, and more. Reservation traffic for this dimension may return a dash (-) in reporting. The dash can indicate delivery via inventory sharing. | Historical, Future sell-through, Reach, Technical ad delivery (Beta) Delivery, Looker Studio Connector |
Programmatic buyer The name of the buyer on a programmatic proposal. This dimension is only available if Ad Manager Programmatic Direct is enabled in your network. | Historical, Reach, Sales Delivery, Looker Studio Connector |
Programmatic channel Channel of transaction. Includes Preferred Deals, Programmatic Guaranteed, Private Auctions, and the Open Auction. Transactions via First Look are included in Open Auction transactions. | Historical, Reach, Sales Delivery, Looker Studio Connector |
Verified advertiser (Deprecated) Name of the verified advertiser you want to add to your list of companies. Verified advertisers are mapped between Ad Exchange and Ad Manager. Learn more | Historical Delivery |
Verified brand (Deprecated) Name of the verified brand you want to add to your list of companies. Brands are children that are mapped to parent advertisers, providing you with more granular blocking and pricing options and reporting data. | Historical Delivery |
Verified categories Names of the verified categories you want to add to your list of companies. Categories allow you to organize and filter your audience segments by common themes, such as Demographics, Geographic, or Interest. | Historical Delivery |
Optimization type (Beta) | Historical Looker Studio Connector |
Advertiser (classified) Name of the advertiser, as classified by Google, associated with a creative transacted through Ad Exchange and Exchange Bidding, including Programmatic Guaranteed and Preferred Deals. Classification is non-exhaustive. Some values may appear as "(Not applicable)" and this is expected behavior. When an advertiser uses creatives associated with different landing pages, Ad Manager won't be able to determine the specific creative that will serve in advance. Instead, Ad Manager will check the advertiser mappings for each landing page and randomly report the affiliated advertiser. | Historical Delivery, Looker Studio Connector |
Brand (classified) Name of the brand, as classified by Google, associated with a creative transacted through Ad Exchange and Exchange Bidding, including Programmatic Guaranteed and Preferred Deals. Classification is non-exhaustive. Some values may appear as "(Not applicable)" and this is expected behavior. | Historical Delivery, Looker Studio Connector |
Serving restriction
Shows performance distributed by serving restriction. If an ad call can be subject to multiple restrictions, only the first match from the order below will be reported. Reporting figures won't overlap.
Some ad requests may fall into multiple categories in this list. In these cases, the ad request is sorted into the first applicable category according to the order shown here. Policy restrictions are not included in the Serving restrictions dimension and should be reviewed in the Policy center. Available for date ranges starting on or after January 14, 2021.
| Historical Delivery, Looker Studio Connector |
Creative technology Type of technology used to serve the creative. Possible values are "AMPHTML", "Standard HTML", "Custom HTML", "Video", or "Other". Data for this dimension is only available for campaigns that served after March 3, 2018. | Historical |
Unified pricing rule The unified pricing rule used to set the price applied to programmatic demand. "No pricing rule applied" may mean that the impression was unfilled, there was no matching unified pricing rule, or the auction candidate was ineligible for unified pricing rule filtering. (For example, Standard or Sponsorship line items).
Any price set applies to Open Auction and Private Auction traffic across Open Bidding and Ad Exchange that matches the targeting criteria, including First Look. Traffic from Ad Exchange and AdSense backfill is subject to the unified pricing floor.
When the floor is set using target CPM, Ad Manager attempts to achieve a target CPM across all inventory sources that are covered by the unified pricing rule. Therefore, if a unified pricing rule report is broken out granularly but doesn’t include rows for all covered inventory sources, you may see “Average eCPM” values that are below the rule’s target CPM. Learn more about activating CPM on unified pricing rules.
Note: In the above description, "price" or "pricing" refers to either target CPM or floor prices.
| Historical Delivery, Looker Studio Connector |
Yield partner (classified) Name of the yield partner, as classified by Google. Classification is non-exhaustive. Some values may appear as "(Not applicable)" and this is expected behavior. | Historical Delivery, Looker Studio Connector |
Yield partner tag For Ad Exchange, the value "Ad Exchange" is displayed. Note that metrics for the "Ad Exchange" yield partner tag are counted once for each applicable yield group Ad Exchange is part of. Only applies to Mediation; not Open Bidding. | Historical Delivery, Looker Studio Connector |
Predicted viewability bucket (Beta)
| Historical Delivery, Looker Studio Connector |
User identifier status (Deprecated) Possible values include:
Note: This dimension only reports values based on third-party IDs.
In comparison to "Third-party ID status," "User identifier status" first checks permissions, then ID presence. Because it checks permissions first it may have the value "restricted," even if no ID is present. This dimension was previously called "User cookie status." | Historical Delivery, Looker Studio Connector |
Ad experiences (Beta) | Historical Delivery |
Ad technology provider (Beta) Compatible only with "Bids" and "Average bid CPM" metrics. | Historical Delivery |
Ad technology provider ID (Beta)
The ID of the ad technology provider (ATP) associated with the bid. Only appears in the exported version of a report. | Historical Delivery |
Ad technology provider domain (Beta) Compatible only with "Bids" and "Average bid CPM" metrics. | Historical Delivery |
Buyer network (Beta)
Identifies to publishers which buyers, including buyer networks that represent accounts (or "seats" on the exchange) owned by DSPs and ad networks, transacted on their inventory. | Historical Delivery |
Advertiser domain (Beta) Provides more transparency into advertisers whose identities are not otherwise available. This dimension sometimes makes large-volume reports run more slowly.
Reports that use the “Advertiser domain” dimension will show 100% Ad Exchange Coverage for all rows except "(unknown)". For this reason, Ad Exchange Ad Requests and Ad Exchange Coverage should be disregarded for those rows. In some scenarios, such as RTB ads, the advertiser domain may be one of multiple submitted domains and we don't know the specific creative chosen to be served. In this case, the advertiser domain reported is one randomly chosen from the list of possible domains. "Not Applicable" indicates incompatibility with Ad server, AdSense, and Mediation demand channels. | Historical Delivery |
Advertiser vertical (Beta) The categories displayed are identical to the ones that publishers can block. When combined with dimensions such as "Buyer networks" and "Advertisers (classified)," this dimension can provide information to effectively allocate inventory and adjust pricing strategies to include high-value advertiser segments. Why do I see "Unknown" values?
A very small number of impressions can't be categorized. And in some instances, specific advertisers can't be mapped to an Advertiser vertical. This dimension is best used when combined with other data such as "Advertisers (classified)" and "Buyer network." Reports that use the "Advertiser vertical" dimension will show 100% Ad Exchange Coverage for all rows except "(unknown)". For this reason, Ad Exchange Ad Requests and Ad Exchange Coverage should be disregarded for those rows. "Not Applicable" indicates incompatibility with Ad server, AdSense, and Mediation demand channels. | Historical Delivery |
Buying agency (Deprecated) Reports that use the "Buying agency" dimension will show 100% Ad Exchange Coverage for all rows except "(Unmatched ad requests)." For this reason, Ad Exchange Ad Requests and Ad Exchange Coverage should be disregarded for those rows. "Not Applicable" indicates incompatibility with Ad server, AdSense, and Mediation demand channels. | Historical Delivery |
Is First Look (Beta) | Historical Delivery, Looker Studio Connector |
Bidder (Beta)
Shows publishers the performance of bidders, including Open Bidders and Authorized Buyers, who bid on their inventory. Available for Open Auction and Private Auction. | Historical Delivery |
First Look pricing rule (Beta) Applies to Ad Exchange and Open Bidding. Shows "(Not applicable)" for other demand channels. | Historical Delivery |
Programmatic deal name (Beta)
Shows publishers the performance of Preferred Deals, Private Auction, and Programmatic Guaranteed (Standard and Sponsorship) broken out by a Programmatic deal name. Shows "(Not applicable)" if no Preferred Deal, Private Auction, or Programmatic Guaranteed was involved. Previously called “Deal name.” | Historical Delivery |
Programmatic deal ID (Beta)
Shows performance of Preferred Deals, Private Auction, and Programmatic Guaranteed (Standard and Sponsorship). The Programmatic deal ID is a system-generated number used to identify a deal between a buyer and a publisher. Shows "0" if no Preferred Deal, Private Auction, or Programmatic Guaranteed was involved. Note: Some buyers may submit multiple bids at the same price for a single auction through different auction package deals, which aren't reported in Google Ad Manager. For these types of bidding, the Programmatic deal ID value is the auction package deals IDfor Open Auction demand channel. Previously called “Deal ID.” | Historical Delivery |
Secure signal name (delivered) (Beta) | Historical Delivery |
Protected Audience API delivery (Beta) Values include:
| Historical Delivery |
Multiplex style name Break down your reports by Multiplex style. Multiplex styles (retired) determine how grids of ads look for a segment of inventory. | Historical Delivery, Looker Studio Connector |
Publisher provided signals (delivered) (Beta) Reports "(None)" if publisher provided signals aren’t available. | Historical Delivery |
Video ad formats rule | Historical Delivery, Looker Studio Connector |
Agency (Beta) The Agency value is present only when the agency is set up. Additional values include:
Supported agencies include: Omnicom, Dentsu, Publicis, Havas, and GoodWay Group. The spend per agency only displays when it comes from a DSP that is making proper bid response declarations about the buyer for whom they're bidding. DSPs that support such declarations are DV360, Yahoo, and Amazon. | Historical Delivery |
Ad Exchange product (Beta) | Historical Inventory |
Ad unit (all levels) The name of the ad unit. Select dimension attributes to display the ad unit code. | Historical, Future sell-through, Reach, Technical ad delivery (Beta) Inventory, Looker Studio Connector |
Ad request size (Deprecated) Only selectable with limited set of metrics, including "unfilled impressions" and "codeserves." Only shows a single size per request, even if the request contained multiple sizes. The Creative sizes dimension generally matches the ad request size when the ad request contains a single size. This dimension is deprecated. Use "Requested ad sizes" instead. | Historical |
Key-values
Key-values associated to an ad slot request. Use the "Ad Server Targeted Impressions" and "Ad server impressions" metrics to differentiate between targeted and untargeted impressions. | Historical Inventory |
Placement Name of the placement that currently includes an ad unit associated with an impression, click, or other event. Learn more | Historical, Future sell-through Inventory, Looker Studio Connector |
Requested ad sizes
Includes all ad sizes in each ad request, accurately reflecting ad requests with multiple inventory sizes. The size is displayed in the format "wxh" with multiple sizes separated by comma (for example, 300x250, 600x300v). You can apply filters to this dimension to only include certain sizes. Video ad request sizes are appended with "v", such as "640x480, 300x250v". How this dimension differs from "Ad request size":
| Historical Inventory |
Channel (Beta) Shows publisher performance by inventory segment. Sometimes, there may be multiple channels with the same name. When the Channel dimension is included in a report or you choose it as a filter, the report aggregates the data from all the like-named channels and displays the combined data in the report results. This may lead the calculated total ad requests to exceed the actual total number of ad requests. Inventory that isn't associated with any channel will be excluded from the report. Applies to Ad Exchange and Open Bidding. Shows "(Not applicable)" for other demand channels. | Historical Inventory |
Ad request sizes | Future sell-through Inventory |
Video placement (Deprecated) In keeping with IAB guidelines, the "Video placement" field will be deprecated in 2024. | Historical Inventory |
Custom dimensions
View dimensions created from key-values defined in your network. Learn more | Historical Inventory |
Inventory bundle
The name of the inventory bundle associated to the line item linked to the Creative that served to the ad slot request. Learn more | Historical Inventory, Looker Studio Connector |
Inventory format (Beta)
| Historical Inventory, Looker Studio Connector |
Child network code | Historical Inventory |
Ad unit (top level) The name of the ad unit. Displays only top-level ad units, with impression data for each child ad unit aggregated toward the total for its parent ad unit. Select dimension attributes to display the ad unit code. | Historical, Future sell-through, Reach, Technical ad delivery (Beta) Inventory, Looker Studio Connector |
PPID presence (Deprecated)
| Historical Inventory |
ATT consent status
| Historical Inventory |
Secure signal presence (Beta)
Secure signal sharing is a processor feature that lets publishers pass obfuscated signals (such as user IDs) to third-party bidders on RTB bid requests. Shows how including secure signals and sending them to bidders can impact metrics, such as Total impressions and Total CTR. Likely, the Bidder hasn't chosen to receive the signal(s) if you see a combination of:
| Historical Inventory |
Traffic source (Beta)
Note: Publishers must set the traffic source to "Purchased" or "Organic" on the ad request to see those values in reporting. If no value is set, we'll report "Undefined." Core compatibility | Historical Inventory, Looker Studio Connector |
URL (Beta) Applies to Ad Exchange and Open Bidding. Shows "(Not applicable)" for other demand channels. If you use subdomains and include the “URL” dimension in reports, your impression and revenue numbers may be inflated. Say that you have a site with a base domain of example.com and the subdomains one.example.com and two.example.com. If you include the URL in your report, data for the subdomains gets counted twice (as part of both the base domain and the subdomain), thus overstating impressions and revenue. Including the “Site” dimension can provide more accurate numbers, but this data also may include impressions to sites that you don’t control or that don’t have your ad tag directly on them. Learn more. | Historical Inventory |
Ad type (Beta)
Not all of these ad types will appear on your inventory. Applies to Ad Exchange, Open Bidding, and AdSense. Shows "(Not applicable)" for other demand channels. | Historical General inventory |
Dynamic allocation (Beta)
Applies to Ad Exchange and Open Bidding. Shows "(Not applicable)" for other demand channels. | Historical General inventory |
Auto-refreshed traffic
| Historical Inventory |
Secure signal name (presented) (Beta) | Historical Inventory |
PPID status
| Historical Inventory |
Third-party ID status Possible values include:
In comparison to “User identifier status,” “Third-party ID status” first checks presence, then permissions. Because it checks presence first it may have the value "missing," regardless of whether the user has opted out of personalization. | Historical Inventory |
First-party ID status (Beta) Possible values include:
| Historical Inventory |
Primary personalization ID type Possible values include:
| Historical Inventory |
Topics status
| Historical Inventory |
Publisher provided signals (all levels) (Beta) Reports "(None)" if publisher provided signals aren’t available. | Historical Inventory |
Publisher provided signals (top level) (Beta) Reports "(None)" if publisher provided signals aren’t available. | Historical Inventory |
Creative vendor Values include:
Review Ad technology providers. | Historical Inventory |
Publisher provided signals (data provider) (Beta) | Historical Inventory |
Video placement (new) (Beta) | Historical Inventory |
City City associated to IP address from ad slot request | Historical Geography, Looker Studio Connector |
Country Country associated to IP address from ad slot request | Historical, Future sell-through Geography, Looker Studio Connector |
Metro DMA region associated with the IP address included in the ad slot request. | Historical Geography, Looker Studio Connector |
Postal code Postal code associated with IP address from the ad slot request. Available for the following countries: Canada, France, Germany, India, the UK, and the USA. | Historical Geography, Looker Studio Connector |
Region Region associated with the IP address included in the ad slot request. | Historical Geography, Looker Studio Connector |
Continent (Beta) Possible values include Unknown, Africa, Americas, Asia, Europe, and Oceania. | Historical, Future sell-through Geography, Looker Studio Connector |
Ad network name Name of the ad network. | Historical Mediation, Looker Studio Connector |
Mediation type Type of mediation request, as defined for each network in a mediation group. For example, "Mobile app". | Historical Mediation, Looker Studio Connector |
Native ad format name Break down your reports by native ad formats. Native ad formats define the variables that determine the content of your ads. Note that non-native values display as “(Non-native ad)” and are included in the totals. | Historical Native, Looker Studio Connector |
Native style name Break down your reports by native style. Native styles determine how your native creatives look for a segment of inventory. Note that non-native values display as “(No native style)” and are included in the totals. | Historical Native, Looker Studio Connector |
Creative billing type Creative type as associated on your Google Ad Manager invoice. | Historical Looker Studio Connector |
Assignment
| Historical, Partner finance, Technical ad delivery (Beta) Partner, Looker Studio Connector |
Inventory ownership (Deprecated) Shows publishers the ownership of Scaled Partner Management (sub-syndicated) domains.
If inventory ownership for video ad requests displays as "uncategorized," this is likely because the Applies to Ad Exchange and Open Bidding. Other demand channels will show "(Not applicable)." This is an account-level setting and not available to all publishers. | Historical Partner |
Partner
A publisher with whom you have an agreement to share ads and revenue. | Historical, Partner finance, Technical ad delivery (Beta) Partner |
Network partner name (Beta) Displays the name of the network partner. If the network partner name for video ad requests displays "non-represented," this is likely because the Supported for Ad Exchange and Open Bidding demand channels. Other channels will show (Not applicable). This is an account-level setting and not available to all publishers. | Historical Partner |
Partner label (Deprecated)
Organize your partners by label. Labels allow you to later report by label and leverage other ad serving features. | Historical, Partner finance Partner, Looker Studio Connector |
Date Note: The exported date format is based on the language and/or location associated with the Google account of the person creating the report. In reports created by other users, such as scheduled reports, the exported date format may differ from the format in reports created by you. | Historical, Future sell-through, Technical ad delivery (Beta) Time unit, Looker Studio Connector |
Day of week Calendar day of the week (e.g., Monday, Tuesday) | Historical, Future sell-through, Reach, Technical ad delivery (Beta) Time unit |
Hour | Historical Time unit, Looker Studio Connector |
Month and year The related month and year. Example: "October 2019" | Historical, Future sell-through, Reach, Partner finance, Technical ad delivery (Beta) Time unit, Looker Studio Connector |
Week Weekly date range, formatted as "M/D/YY - M/D/YY". | Historical, Future sell-through, Reach, Technical ad delivery (Beta) Time unit, Looker Studio Connector |
Ad server redirect position
The position of a redirect in the VAST chain. For example, for a chain of A > B > C, A is in position 0, B is in position 1, etc. | Video creative quality (Beta) Video |
Ad server VAST version
The VAST version of each ad server in the VAST chain. | Video creative quality (Beta) Video |
Ad serving system
Each ad server in the VAST chain. | Video creative quality (Beta) Video |
CMS metadata Contains a dimension for each key in your CMS metadata. Reporting data reflects the current state, not the historical state, of CMS metadata associations. Learn how to report on video content metadata. | Historical Video |
CMS metadata key Reporting data reflects the current state, not the historical state, of CMS metadata associations. Learn how to report on video content metadata. | Historical Video, Looker Studio Connector |
Content
The video content ingested in Ad Manager. The content source status must be active to serve ads. Video ads not targeted to specific content using the cmsid and vid parameters appear as "Not applicable" with this dimension. To limit your report to only content-specific traffic, apply the Request type filter, set to is any of > Video tag when reporting on this dimension. This will show "Not applicable" when a request comes for content that hasn't been ingested or requests don't match ingested content. | Historical, Future sell-through Video, Looker Studio Connector |
Content bundle Reports with this dimension show all bundles where content appeared, not only the targeted bundles. Video ads not targeted to specific content using the cmsid and vid parameters appear as "Not applicable" with this dimension. To limit your report to only content-specific traffic, apply the Request type filter, set to is any of > Video tag when reporting on this dimension. | Historical Video, Looker Studio Connector |
Content metadata Displays metrics for content metadata values whose keys are enabled and mapped. Each dimension under "content metadata" is a metadata key. When you choose a dimension, the report displays the metrics for all the values assigned to that key. Learn how to report on video content metadata. | Historical Video |
Creative media bitrate
The bitrate of the selected media file. | Video creative quality (Beta) Video |
Creative media duration
The duration of the actual media played. | Video creative quality (Beta) Video |
Creative media loading latency
The time it took for the media to load. | Video creative quality (Beta) Video |
Creative media type
The MIME type of the selected media file. | Video creative quality (Beta) Video |
Creative media VPAID version
Indicates whether an ad used VPAID 1, 2, 3, or did not use VPAID. | Video creative quality (Beta) Video |
Custom event Applicable to Ad Manager Video and Rich Media. | Historical Video, Looker Studio Connector |
Custom event type Type of Ad Manager Video and Studio custom event triggered. | Historical Video, Looker Studio Connector |
Custom spot (Beta) | Historical Video |
Fallback position The position of an ad returned as a result of video fallback with a VAST redirect. This dimension is compatible with impressions, clicks, conversions, and other metrics that result from fallback and non-fallback ads being served. | Historical Video, Looker Studio Connector |
Inventory share assignment Shows the name for the inventory share assignment. | Historical Video |
Inventory share outcome Shows who received a share. Either a host or a partner receives shares. | Historical Video |
Live stream The name given to a live stream in Ad Manager. | Historical Video, Looker Studio Connector |
Live stream ad break The name given to the ad break of a live stream in Ad Manager. | Historical Video, Looker Studio Connector |
Metadata key Displays metrics for the keys you mapped to video content metadata. Metrics shown per key are an aggregate of all values assigned to that key. There is no limit to the number of keys displayed in a report. Video ads not targeted to specific content using the cmsid and vid parameters appear as "Not applicable" with this dimension. To limit your report to only content-specific traffic, apply the Request type filter, set to is any of > Video tag when reporting on this dimension. Learn how to report on video content metadata. | Historical Video, Looker Studio Connector |
Position in pod To limit results to video-only traffic, filter your results using the Request type filter, set to is any of Video tag. | Historical Video, Looker Studio Connector |
Position of pod
The location of the pod (groups of ads shown in sequence) within the video content. Some example positions are: "Pre-roll", "Mid-roll", "Post-roll", and "Unknown position", which represents truly unknown, non-podded video or non-video traffic. To limit results to video-only traffic, filter your results using the Request type filter, set to is any of Video tag. | Historical Video, Looker Studio Connector |
VAST version (Beta) For redirects, this is not the VAST version from the third-party ad server. This dimension can be combined with all video dimensions, including content metadata, date and time, request type, ad unit and placement, and all delivery dimensions. It is compatible with total impressions metrics; sell-through metrics; viewership, error, and interaction metrics. | Historical Video, Looker Studio Connector |
Video ad duration (Beta) Shows publishers the performance of their video ad inventory broken out by duration set on their requests in ranges of seconds and minutes. Examples: 6-10 seconds or 2-5 minutes. A dash ("-") value may indicate the following:
| Historical Video |
Video ad request duration
| Historical Video |
Video ad type (Beta) Shows publishers the performance of their video ad inventory broken out by type. Includes the following formats:
Applies to Ad Exchange, Open Bidding, and AdSense. Shows "(Not applicable)" for Ad Server. | Historical Video |
Video continuous play type (Beta) | Historical Video, Looker Studio Connector |
Video measurement source
| Historical Video |
Video redirect third party (Beta) The third party where Google Ad Manager was redirected for the creative, based on the domain. This may be useful in determining fill rate of different creative vendors or for troubleshooting errors by server. Commonly used vendors are displayed by name; others are shown by domain. This dimension is based on the "Creative" dimension, and is compatible with the same dimensions and metrics. | Historical Video |
Video SDK version
See more information on each SDK. This dimension can be combined with all video dimensions, request type, date and time, ad unit, and all creative dimensions. It is compatible with impression metrics; video viewership, interaction, and error metrics. | Historical Video, Looker Studio Connector |
Ad request source
The description indicating where the ad came from, which may be useful in determining feature support or for troubleshooting. Possible sources are:
This dimension can be combined with all video dimensions, request type, date and time, ad unit, and all creative dimensions. It is compatible with impression metrics; video viewership, interaction, and error metrics. | Historical Platform, Looker Studio Connector |
Device category Shows delivery by device category: Connected TV (CTV) device(Beta), Desktop, Feature phone, Set-top box (STB), Smart display, Smartphone, Smart speaker, and Tablet. | Historical Platform, Looker Studio Connector |
Devices (Beta) Shows performance by specific user mobile device. Possible values include:
| Historical Platform |
Inventory types (expanded) Note: Video takes precedence over any other value, for example, if there is an in-stream video impression on a desktop device, it will be attributed to in-stream video and not desktop web. Values include:
| Historical Platform |
Request type (Beta)
Note that the value "Google Ad Manager Tag" is no longer in use, but shows for compatibility reasons. | Historical Platform, Looker Studio Connector |
Targeting Information about the browser, device, and other environments into which a line item or creative served. The data included in this dimension is delineated by the prefixes below:
| Historical Platform |
Browser “In-app browser” is a browser embedded within an app. | Historical, Analytics Platform, Analytics, Looker Studio Connector |
Operating system (Beta) Note: Desktop operating systems and non-mobile app impressions are always classified as "Unknown." | Historical Platform, Looker Studio Connector |
App SDK version (Beta) The Google Mobile Ads SDK version integrated into the app. Google Mobile Ads SDK for iOS and for Android traffic are both supported. The Google Mobile Ads SDK version for Android traffic is only supported from June 23, 2023; prior to that date, this dimension will return a dash (-) in reporting for Android. | Historical Platform, Looker Studio Connector |
Site (Beta) Shows publishers data for their domains and subdomains. The use of this dimension isn't the same as reporting on URLs. Unlike URLs, the Site dimension doesn't have to be manually defined in the user interface to generate results. Returns "(unknown)" for data from sites with invalid URLs. Applies to Ad Exchange and Open Bidding. Shows "(Not applicable)" for other demand channels. | Historical Platform |
Operating system category Note: Desktop operating systems and non-mobile app impressions are always classified as "Unknown." | Reach Platform |
Ad location (Beta) Shows whether a given piece of publisher inventory was above (ATF) or below the fold (BTF) of a page. Here are reasons why you may see "Unknown" as an Ad location value:
| Historical Platform |
Branding type (Beta) This dimension applies to Ad Exchange and Open Bidding. Shows “(Not applicable)” for other demand channels. Reports that use the "Branding type" dimension will show 100% Coverage for all rows except "(Unmatched ad requests)". For this reason, Ad Requests and Coverage should be disregarded for those rows. | Historical Platform |
Applies to Ad Exchange and Open Bidding. Shows “(Not applicable)” for other demand channels. “Personalized” (formerly known as "Interest-based") may include contextual targeting when user data, such as cookie ID, isn’t available. If you selected “Non-personalized ads” in the EU user control settings, you might still see ads under “Personalized” even though user data isn’t being used. The remaining possible values for this dimension are:
| Historical Platform |
Bandwidth (Beta) Allows publishers to see performance by different mobile user connection types, such as cable, DSL, and OC12. Available for Ad Exchange and Open Bidding. | Historical Platform |
Carrier (Beta) Allows publishers to see performance by mobile user connectivity, such as “Verizon (US).” Available for Ad Exchange and Open Bidding. | Historical Platform |
Interaction type
Whether the impression was a rewarded request or not, in which case "Unknown" is displayed. Learn more about rewarded ads. | Historical Platform |
Inventory types
Shows performance by general groups of inventory. Possible values are:
| Historical Platform, Mobile |
App names
Shows performance by mobile app. "(Not applicable)" may appear if the app name could not be resolved. For a complete view, add the "App ID" dimension. | Historical Platform |
Rendering SDK
| Historical Delivery |
Is AdX direct (Beta) Returns "TRUE" for AdX Direct traffic (new) and "FALSE" otherwise (all existing Historical report traffic). | Historical Platform |
Browser category (Beta) Possible values include Google Chrome, Safari, Microsoft Edge, Firefox, In-app browser, and Not applicable (App). | Historical, Reach Platform |
Operating system category (Beta) Possible values include Unknown, Other, Android, and Apple iOS. Note: Desktop operating systems and non-mobile app impressions are always classified as "Unknown." | Historical Platform |
App ID Learn more about finding app names and IDs. | Historical Platform |
Domain
Shows performance by top domain, such as "example.co.uk". Excludes subdomains. | Historical, Analytics Platform, Analytics, Looker Studio Connector |
App ownership status
The app must be confirmed through app readiness before you claim the app as owned. The app then goes through an approval process where the app receives a status. App status is at the time of analysis, not at the time of the ad event. | Historical Platform |
Demand Channel
| Historical, Reach Delivery, Looker Studio Connector |
Yield group Note: This dimension can return a "Not applicable" value when requests are eligible for Open Bidding, but no Open Bidding partners actually bid. Impressions, clicks, revenue, and other metrics can appear in multiple report rows. | Historical, Technical ad delivery (Beta) Delivery, Looker Studio Connector |
Yield partner Name of the "Ad network" company within a yield group. Learn more about yield partners. The value "(Not applicable)" may be returned for Yield Partner. This occurs when a request that is eligible for Open Bidding receives no bids from Open Bidding partners.
| Historical, Technical ad delivery (Beta) Delivery |
Yield partner type (Deprecated) Mediation attributes for a yield partner. Possible values include: Mediation, Open Bidding, or Ad Exchange. This dimension is deprecated. Use Demand Channel, instead. | Historical Yield group, Looker Studio Connector |
Demand subchannel
| Historical, Reach Delivery, Looker Studio Connector |
All salespeople Breakdown of data by both primary Salesperson and all Secondary salespeople assigned to an Order. | Historical, Reach, Sales Users |
Salesperson Aggregated data rolled up under the primary Salesperson assigned to an Order. Note: For Historical reports, you can also include the "Line item" dimension. | Historical, Future sell-through, Reach Users, Looker Studio Connector |
Try your keywords on Google Web Search. |