Metrics and Dimensions

This page provides tables that list and describe the available dimensions and metrics. For AdMob-specific dimensions and metrics, visit one of the following pages: Android or iOS.

Dimensions

Note: CODE and ID are used programmatically while NAME is displayed to an end user and can be localised.

Dimension Description
AD_CLIENT_ID The ID of an ad client. Example: ca-pub-088712.
AD_FORMAT_CODE The code of an ad format. Examples: text, image, html.
AD_FORMAT_NAME The name of an ad format. Examples: Text, Image, or Rich Media. The latter value is for the html format.
AD_UNIT_CODE The code of an ad unit. This value is not necessarily unique across ad clients. Example: 837572.
AD_UNIT_ID The unique ID of an ad unit. Example: ca-pub-088712:837572.
AD_UNIT_NAME The name of an ad unit.
AD_UNIT_SIZE_CODE The size code of an ad unit. Examples: 720x42 or mobile_single.
AD_UNIT_SIZE_NAME The size name of an ad unit. Examples: 720x42 or Single (Mobile).
BID_TYPE_CODE The type of a bid. Examples: cpc, cpm.
BID_TYPE_NAME A bid type name. Examples: CPC bids, CPM bids.
BUYER_NETWORK_ID The ID of an ad network that sends ads to your site.
BUYER_NETWORK_NAME The name of an ad network that sends ads to your site. Example: Google Adwords.
COUNTRY_CODE The CLDR Region Code. Examples: US, FR.
COUNTRY_NAME Region name. Examples: United States, France.
CUSTOM_CHANNEL_CODE The code of a custom channel.
CUSTOM_CHANNEL_ID The ID of a custom channel.
CUSTOM_CHANNEL_NAME The name of a custom channel.
DATE A date in YYYYMMDD format.
DOMAIN_NAME A domain name.
MONTH A month in YYYYMM format.
PLATFORM_TYPE_CODE The code of a platform type. Examples: HighEndMobile, Desktop.
PLATFORM_TYPE_NAME The name of a platform type. Examples: High-end mobile devices, Desktop.
PRODUCT_CODE The code of a product. Examples: AFC, AFS.
PRODUCT_NAME The name of a product. Examples: AdSense for Content, AdSense for Search.
TARGETING_TYPE_CODE A targeting type code. Examples: Keyword, WebSite, Publisher.
TARGETING_TYPE_NAME A targeting type name. Examples: Contextual, Reservation, Publisher.
URL_CHANNEL_ID The ID of a URL channel.
URL_CHANNEL_NAME The name of a URL channel.
WEEK The date of the first day of a week in YYYYMMDD format.

Metrics

Note: units are returned as strings.

Metric Description Units
AD_REQUESTS The number of ad units that requested ads (for content ads) or search queries (for search ads). An ad request may result in zero, one, or multiple individual ad impressions depending on the size of the ad unit and whether any ads were available. Integer
AD_REQUESTS_COVERAGE The ratio of requested ad units or queries to the number returned to the site. Decimal 0-1
AD_REQUESTS_CTR The ratio of ad requests that resulted in a click. Decimal 0-1
AD_REQUESTS_RPM The revenue per thousand ad requests. This is calculated by dividing estimated revenue by the number of ad requests multiplied by 1000. Decimal
CLICKS The number of times a user clicked on a standard content ad. Decimal
COST_PER_CLICK The amount you earn each time a user clicks on your ad. CPC is calculated by dividing the estimated revenue by the number of clicks received. Decimal. See headers in the response for the currency.
EARNINGS The estimated earnings of the publisher. Note that earnings up to yesterday are accurate, more recent earnings are estimated due to the possibility of spam, or exchange rate fluctuations. Decimal. See headers in the response for the currency.
INDIVIDUAL_AD_IMPRESSIONS The number of times an individual ad is displayed on your website. Different ad formats will display varying numbers of ads. For example, a vertical banner may consist of 2 or more ads. Also, the number of ads in an ad unit may vary depending on whether the ad unit is displaying standard text ads, expanded text ads or image ads. Integer
INDIVIDUAL_AD_IMPRESSIONS_CTR The ratio of individual ad impressions that resulted in a click. Decimal 0-1
INDIVIDUAL_AD_IMPRESSIONS_RPM The revenue per thousand individual ad impressions. This is calculated by dividing estimated revenue by the number of individual ad impressions multiplied by 1000. Decimal
MATCHED_AD_REQUESTS The number of ad units (for content ads) or search queries (for search ads) that showed ads. A matched ad request is counted for each ad request that returns at least one ad to the site. Integer
MATCHED_AD_REQUESTS_CTR The ratio of matched queries that resulted in a click. Decimal 0-1
MATCHED_AD_REQUESTS_RPM The revenue per thousand matched queries. This is calculated by dividing your estimated revenue by the number of matched queries multiplied by 1000. Decimal
PAGE_VIEWS The number of page views. Integer
PAGE_VIEWS_CTR The ratio of individual page views that resulted in a click. Decimal 0-1
PAGE_VIEWS_RPM The revenue per thousand page views. This is calculated by dividing your estimated revenue by the number of page views multiplied by 1000. Decimal

Compatibility

The metadata calls in the AdSense Management API allow you to fetch the list of available dimensions and metrics, check compatibility between them, and find out what products are supported.

metadata.dimensions

The response for this call is similar to this:

[{
  "kind": "adsense#reportingMetadataEntry",
  "id": "EXAMPLE_DIMENSION",
  "compatibleDimensions": [
    "1",
    "2",
    "4",
    ...
  ],
  "compatibleMetrics": [
    "AD_REQUESTS",
    "AD_REQUESTS_COVERAGE",
    "AD_REQUESTS_CTR",
    ...
  ],
  "supportedProducts": [
    "AFC",
    "AFV"
  ]
},
...]
  
  • The compatibleDimensions field shows a list where each item is an integer representing a group of compatible dimensions. As there is no one-to-one relation between compatible dimensions, they are represented as groups. Two dimensions are compatible if they both share one or more groups in their compatibleDimensions list.
  • The compatibleMetrics field lists the IDs of compatible metrics.
  • The supportedProducts field contains the product codes that are compatible with the dimension.

metadata.metrics

The response is similar to the response for metadata.dimensions:

  • compatibleDimensions is a list of dimension IDs, not numbers.
  • There is no compatibleMetrics field. Compatibility between metrics depends on the dimensions used.
  • supportedProducts lists the codes of the products that are compatible with the metric.

Send feedback about...

AdSense Management API
AdSense Management API