Ad Manager report dimensions

• 18-24
• 25-34
• 35-44
• 45-54
• 55-64
• 65+

• Male
• Female

Note: Non-mobile app impressions are always classified as "Unknown."

Event name measures data collected from impressions or clicks. Possible values include:

• ad_impression
• ad_click
• in_app_purchase
• ecommerce_app_purchase
• session_start

“ In-app browser ” is a browser embedded within an app.

• Winner: The bid won because it wasn’t rejected for any reason.
• Outbid: The bid lost to another candidate in the auction.
• Floor: The bid lost because its CPM was below the seller's reserve.
• Optimized pricing: The bid was below the floor price set by optimized pricing.
• No consent: The bid lost because the associated GDPR ad technology provider didn’t have user consent. 
• Unidentified vendor: The bid lost because the GDPR ad technology provider was unidentified.
• Publisher blocked: The bid lost because it was blocked by the publisher’s settings.
• Other: The bid lost for another reason, such as URL filtering.

The name of the ad technology provider as it appears on the Global Vendor List (GVL).

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.

Note: If the creative is part of a creative set, the "Creative ID" column may show the creative set ID. For technical details, view the SOAP API "CREATIVE_ID" entry .

Size of creative that served to the ad slot request. Creative size doesn't represent the actual size of a creative being served. This dimension represents the "Targeted Ad Unit Size" of the creative which is served. Since a Creative size can only be associated with filled impressions, this dimension is not compatible with the Unfilled impressions metric.

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.

• Audio: Audio ads 
• Fluid: Google rendered Native & Fluid ads
• Interstitial: Interstitial ads
• Native: Custom rendered native ads
• Video/Overlay: Video ads
• <width>x<height>: Fixed-size ads

Any other values show as "Unknown".

Note: This dimension can't appear in the same report as the "Unfilled impressions" metric. They are incompatible.

• Sent to winner
• Not sent to winner

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:

• "Secure signal delivery = Not sent to winner" with
• "Secure signal presence = Present", and
• You've successfully completed your secure signals implementation.

• Downloaded: Follows IAB count on download ( Digital Video Ad Measurement Guidelines 2009 ).
• Begin to render: An impression is counted after creative assets have begun rendering. Follows IAB begin to render ( Digital Video Ad Measurement Guidelines 2018 ).
• Unknown: An impression from Ad Exchange or AdSense (like, a non-Ad server impression), or an Ad server impression from before the introduction of this dimension in June, 2020.

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.

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.

• Measured: The data for the metric was directly measured by client code that either Google controls or with which Google has intimate familiarity, or it uses OMID data from client code that was certified by Google or IAB Tech Lab.
• Provided: The data for the metric uses OMID data or other publisher-provided signals that were not certified by Google or IAB Tech Lab.
• Inferred: The data for the metric was inferred using sound judgment; however, it was not directly measured on the client. The inferred metric may originate from Google or a third party.
• (Not applicable): Indicates the source is not supported.

Optimization types include: First Look , Optimized competition , Target CPM , or All Other Traffic.

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.

• Limited ads: Traffic where only limited ads can serve.
• Restricted data processing (RDP): Includes traffic where the publisher requested restricted data processing using the tagging parameter or the now-deprecated network control , or traffic where GPP strings triggered restricted data processing .
• Non-personalized ads (NPA): Includes traffic where the publisher requested non-personalized ads using the tagging parameter or the network control .
• Basic ads: Traffic where only IAB TCF v2.0 basic ads are eligible to serve. This matches users whose provided TC string includes consent for purpose 1 and legal bases for purposes 2, 7, 9, and 10, but no consent for purposes 3 or 4.
• Personalization disabled:Traffic where personalization was disabled by the mobile device’s user controls, other user personalization opt-out controls, or other cases where personalization wasn't feasible.
• No restriction: Traffic without any of the restrictions listed above.

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 .

Shows the best eligible UPR, which may not be the applied UPR or the rejection reason. Other factors or rules could cause a bid's rejection.

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.

The estimated percentage of viewability based on an ad slot's historical and environment data, grouped into buckets. Possible values include:

• ≥50%
• 20% to 49%
• ≤19%
• Unknown

Possible values include:

• Active: A user identifier was present and active.
• Restricted: A user identifier was present, but its usage was restricted by how cookies may be used . For example, personalization is not allowed.
• Missing: A user identifier wasn't present.

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."

Compatible only with "Bids" and "Average bid CPM" metrics.

Compatible only with "Bids" and "Average bid CPM" metrics.

Provides more transparency into advertisers whose identities are not otherwise available. This dimension sometimes makes large-volume reports run more slowly.

• Web caches and others:Domains that are associated with ad servers are grouped here, including Ad Manager and third-party, because we only report on the top-level domain. So if an ad server domain includes redirect parameters, we truncate the full URL, even though the request is valid and may be associated with revenue and impressions.

  You may want to combine this dimension with the "Advertiser (classified)" dimension, as we can often identify the advertiser associated with such domains.

• Unknown:This dimension shows the top 10,000 advertiser domains across Ad Exchange and Open Bidding, ranked by revenue. Any advertiser beyond this limit is placed into the "unknown" category.

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.

Shows performance by buying agency. Not all buyers pass the agency name. As a result, if we don’t show a name, we may display "(unknown)" or "(No agency)."

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.

Applies to Ad Exchange and Open Bidding. Shows "(Not applicable)" for other demand channels.

Shows "(Not applicable)" 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 Deal ID value is the auction package deals ID for Open Auction demand channel.

View a breakdown of data by a bidder-provided ID for revenue verification . If a bidder doesn't provide such an ID, “Unknown” is displayed. If there is insufficient data, or data that didn't meet our privacy or quality requirements, “Other” is displayed.

Reports the Protected Audience API delivery.

Values include:

• Delivered by Protected Audience API
• Not delivered by Protected Audience API

Reports "(None)" if publisher provided signals aren't available.

The Agency value is present only when the agency is set up. Additional values include:

• "Unknown" is shown when an agency isn't set up.
• "(Not applicable)" is shown for demand channels other than Ad Exchange.

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.

The agency holding company value is present when the agency holding company or agency name is set up. Additional values include:

• "Unknown" is shown when agency holding company or agency name isn't set up.
• "(Not applicable)" is shown for demand channels other than Ad Exchange.

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.

• Ad Exchange (includes First look)
• AdSense
• Ad server (direct-sold line items)
• Mediation
• Open Bidding
• Header Bidding
• SDK Bidding
• Protected Audience seller (non-Google)

• Bulk
• Header Bidding (detected)
• House
• Network
• Open Auction - Auction Package
• Open Auction - First Look
• Open Auction - General
• Other (can represent video inventory sharing, as well as reservation ads, such as Bumpers and uncategorized Ad server ads)
• Preferred Deals
• Price Priority
• Programmatic Guaranteed
• Private Auction
• Sponsorship
• Standard

Shows “(Unknown)” if curation wasn’t targeted.

Shows the ID of the curation partner whose data segment or curated packages were targeted.

Shows “0” if curation wasn’t targeted.

• Yes
• No

Learn more about  curation partners .

Shows “0” if auction package deal is not applicable. 

See also the Is curation targeted dimension.

This dimension is deprecated. Use " Requested ad sizes " instead.

Use the "Ad Server Targeted Impressions" and "Ad server impressions" metrics to differentiate between targeted and untargeted impressions.

This is a flattened version of the Placement (all) dimension. Impressions, clicks, revenue, and other metrics can appear in multiple report rows.  Learn more

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":

• Reports on all ad sizes in each request to reflect multi-size inventory more accurately.
• Broader compatibility with other dimensions and metrics.
• Compatible with filters to limit the sizes included.
• Format: WxH (no spaces, comma-separated).

All ad unit sizes included in an ad request display in the report on the same line. This reflects how many impressions are available for a given tag. For example, if your ad request (or, tag) contains 2 sizes, such as 300x250, 300x600 , there will be one row in the report with both sizes, and they are separated by a comma. Video ad request sizes are appended with "v", such as "300x250v".

The type of video placement.

In keeping with IAB guidelines, the "Video placement" field will be deprecated in 2024.

Indicates whether a valid PPID (Publisher-provided identifier) was present on a given ad request. Covers both reservation and programmatic traffic. Possible values include:

• Present: A valid PPID was present
• Missing: A PPID was not present or had an invalid form

Learn more

Reports the presence of secure signals  in the ad request. Values include: 

• Present
• Missing

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:

• "Secure signal delivery = Not sent to winner" with
• "Secure signal presence = Present", and
• You've successfully completed your secure signals implementation.

• Purchased: Traffic redirected from properties other than owned (acquired or otherwise incentivized activity)
• Organic: Direct URL entry, site search, or app download
• Undefined: Value not set in the GPT or mobile SDK

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

• Animated image
• Audio
• Auto display (also known as Magazine style ads)
• Image
• Rich Media
• Text
• Video

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.

• No Dynamic Allocation: (direct requests, or an unknown ad server) Ads served by Ad Exchange outside of dynamic allocation. This includes impressions that are served directly on a page or via another ad server that does not support dynamic allocation.
• Dynamic Allocation with no Ad Manager competition: (regular backfill) Backfill by Ad Exchange where it did not receive a reserve price by the publisher’s ad-server via dynamic allocation.
• Dynamic Allocation with Ad Manager competition: Backfill by Ad Exchange where it was able to beat the reserve price sent by the publisher’s ad-server via dynamic allocation.

Applies to Ad Exchange and Open Bidding. Shows "(Not applicable)" for other demand channels.

• Refreshed: Traffic that is auto-refreshed, which refers to the action of serving or changing advertising or content in an automatic manner when a publisher calls auto refresh Google Publisher Tag (GPT) API on the ad request.
• Not refreshed:All other traffic.

• Active:A user identifier was present and active.
• Restricted:A user identifier was present in the ad request, but personalization was not allowed.
• Missing:A user identifier wasn't present.

Possible values include:

• Active: A user identifier was present and active.
• Restricted: A user identifier was present in the ad request but personalization was not allowed.
• Missing: A user identifier wasn't present.

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. 

Possible values include:

• Active: A user identifier was present and active.
• Restricted: A user identifier was present in the ad request but personalization was not allowed.
• Missing: A user identifier wasn't present.

Possible values include:

• Third-party IDs: Third-party cookie or device ID
• PPID: Publisher provided identifier
• First-party IDs: First-party identifiers
• No personalization: No personalization was possible, but an ID was chosen for other purposes, such as frequency caps. Note that this classification will be phased out in favor of “non-personalizable IDs” and “personalization restricted.” Shows only for data occurring before April 16, 2024. 
• Non-personalizable IDs: An ID that can’t be used for personalization was present. Other uses, such as frequency caps, were possible. 
• Personalization restricted: An ID was present, but personalization was not possible due to a serving restriction. Other uses, such as frequency caps, were possible. 
• No ID: No ID was available.

• Topics not available:The client doesn’t have topics support (for example, it’s an app or a non-Chrome browser), or topics are unavailable for another reason.
• Topics empty:The client can provide topics, but the list is empty.
• Topics provided:The ad request included a list of one or more topics.

Reports "(None)" if publisher provided signals aren't available.

Publisher provided signals allow Ad Manager publishers to annotate key-values and audience lists with IAB taxonomy categories.

Reports "(None)" if publisher provided signals aren't available.

Publisher provided signals allow Ad Manager publishers to annotate key-values and audience lists with IAB taxonomy categories.

Vendors present on a given creative or impression. 

Values include:

• Company name (vendor ID), for instance, Numberly (2664)
• "-" for no certified vendors detected
• N/A for non-Ad Exchange traffic

Review Ad technology providers .

Continent associated with the IP address from the ad slot request.  

Possible values include Unknown, Africa, Americas, Asia, Europe, and Oceania.

Assignments help you define revenue sharing or ad serving relationships with partner publishers. Depending on your permissions, you can select from some or all of the following types of assignments.

• Track: Define a revenue share agreement with a publishing partner for display or video ads. Revenue share is expressed in terms of a percentage value on the assignment.
• Redirect: Send either a percentage or an absolute number of video ad requests to a partner publisher. The redirect is handled through a third-party VAST tag.
• Share: Share specified video inventory with a partner Ad Manager publisher. Your partner can then book line items directly against that inventory in their own Ad Manager network.

A publisher with whom you have an agreement to share ads and revenue.

Organize your  partners  by label. Labels allow you to later report by label and leverage other ad serving features.

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.

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.

Each ad server in the VAST chain.

This dimension replaces the legacy "Content metadata" dimension, which has been deprecated.

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 .

This dimension replaces the legacy "Metadata key" dimension, which has been deprecated.

Reporting data reflects the current state, not the historical state, of CMS metadata associations.

Learn how to report on video content metadata .

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 typefilter, set to is any of> Video tagwhen 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.

Video groups assembled and targeted based on filters or by selecting individual videos, or both. The content bundles  are automatically updated when new content is ingested with matching metadata.

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 typefilter, set to is any of >  Video tagwhen reporting on this dimension.

This dimension will soon be deprecated and replaced with the "CMS metadata" dimension.

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 .

The bitrate of the selected media file.

The duration of the actual media played.

The time it took for the media to load.

The MIME type of the selected media file.

Indicates whether an ad used VPAID 1, 2, 3, or did not use VPAID.

A reusable ad spot  that can be added to an ad break template, as well as directly targeted by a video line item.

This dimension will soon be deprecated and replaced with the "CMS metadata key" dimension.

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 typefilter, set to is any of >  Video tagwhen reporting on this dimension.

Learn how to report on video content metadata .

To limit results to video-only traffic, filter your results using the Request typefilter, set to is any of Video tag.

To limit results to video-only traffic, filter your results using the Request typefilter, set to is any of Video tag.

The numerical version of a VAST creative that is returned, which may be useful in determining which version of VAST is requested on your ad tags, or if you distribute different ad tags to different players or partner inventory. Possible versions are: VAST 2, VAST 3, VAST 4, and Not applicable (for non-video requests).

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.

• If an opportunity is filled, this will be the duration of the ad served.
• If an opportunity is unfilled, this will be the network opportunity duration.

Shows publishers the performance of their video ad inventory broken out by source. The following values include:

• Measured: Measured by the Video SDK
• Inferred: A  DAI SSB or ActiveView presumed viewability event
• Provided: All other Video SDK-less cases

• iOS IMA SDK
• Android IMA SDK
• HTML5 IMA SDK
• tvOS IMA SDK
• Roku GAM Utils
• Roku IMA SDK
• Roku PAL
• iOS PAL
• Android PAL
• HTML5 PAL
• tvOS PAL
• Cast PAL
• iOS GMA SDK
• Android GMA SDK
• Unknown
• SDK-less
• Other

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.

The service that has stitched the ad into the user stream and that may be useful in determining feature support or for troubleshooting. Possible sources are: Dynamic Ad Insertion, Server-side, Client-side, or Unknown. The values for this dimension are Ad Manager DAI Stitcher, Google Cloud Video Stitcher and other.

This dimension can be combined with all video dimensions, request type, ad request resource, date and time, ad unit, and all creative dimensions. It is compatible with impression metrics; video viewership, interaction, and error metrics.

• Dynamic Ad Insertion
• Dynamic Ad Insertion API (pod serving)
• Dynamic Ad Insertion server-side beaconing
• Server-side
• Client-side
• Unknown

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.

Provide dimension feedback

• Apple tablet
• Apple phone/touch
• Android tablet
• Android phone
• WebOS
• Blackberry
• Unknown: The query is from a mobile device, but we can't detect more specific details (e.g., whether it's from iOS, Android, a tablet, a phone, etc.).

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:

• AMP:User is viewing the ad on an Accelerated Mobile Page , which has been designed to load mobile web content faster.
• App:User is viewing the content through a mobile app on their smartphone or tablet. Note that Ad Manager identifies mobile apps via use of the SDK. Publishers using simplified URL tags to make requests for an app may see inconsistent results.
• Desktop web:User is viewing the content through a PC or laptop computer.
• In-stream video and audio:Ads played within the context of a video or audio stream in the same video or audio player that a user is viewing video or listening to audio content.
• Mobile web:User is viewing the content from their mobile or tablet browser.
• Other:Ad Manager can't detect where the user is viewing the content.

• AMP Ad tag
  An impression is attributed to a request from an <amp-ad> tag. This tag allows AMP Ads to load faster than standard ads or ads from other tag types. If this value is something other than "AMP Ad tag" (such as "Google Publisher Tag" or "Other"), you're likely running ads from a custom domain. You may want to replace them with <amp-ad> tags, so AMP Ads can load faster. Learn more .
• Google Publisher Tag
  An impression is attributed to the Google Publisher Tag .
• GPT Light
  An impression is attributed to the  GPT Light tag .
• GPT Simple URL
  An impression is attributed to a  Tagless request , which allows ads in environments where JavaScript isn’t supported.
• Video Tag
  An impression is attributed to a request from a video player .
• Mobile Ads SDK
  An impression is attributed to a request that was built through the Google Mobile Ads SDK , so the ad is on an app.
• Show Ads
  An impression attributed to the "Show ads" synchronous tag for Ad Exchange Direct traffic.
• Ads by Google
  An impression attributed to the "Ads by Google" asynchronous tag for Ad Exchange Direct traffic.
• Other
  Indicates less common requests, such as Video Companion ad tag.

Note that the value "Google Ad Manager Tag" is no longer in use, but shows for compatibility reasons. 

Note: Desktop operating systems and non-mobile app impressions are always classified as "Unknown."

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.

The mobile device operating system. Not available for desktop inventory and may exclude some less common operating systems.

Note: Desktop operating systems and non-mobile app impressions are always classified as "Unknown."

• Web: User is viewing the content through a PC or laptop computer, or from their mobile or tablet browser.
• App: User is viewing the content through a mobile app on their smartphone or tablet. Note that Ad Manager identifies mobile apps via use of the SDK. Publishers using simplified URL tags to make requests for an app may see inconsistent results.
• AMP: User is viewing the ad on an Accelerated Mobile Page , which has been designed to load mobile web content faster.
• Other: Ad Manager can't detect where the user is viewing the content.

Displays which SDK renders the ad on mobile apps. 

Values include:

• 3P SDK:Ad rendered by third-party SDK. Recommended to report together with “Buyer network” and “bidder” dimensions. 3P SDK does not report Total clicks.
• GMA SDK:Ad rendered by Google Mobile Ads (GMA) SDK.
• Not applicable:Non-mobile traffic and unfilled request.

Category of the user's browser.

Possible values include Google Chrome, Safari, Microsoft Edge, Firefox, In-app browser, and Not applicable (App).

Note: Desktop operating systems and non-mobile app impressions are always classified as "Unknown."

Learn more about finding app names and IDs .

• Ownedmeans you've successfully claimed the app as yours.
• Not ownedmeans you haven't claimed the app as yours.
• Not applicable means the App ID is not available.

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.

Note:This dimension can return a "Not applicable" value when requests are eligible for Open Bidding, but no Open Bidding partners actually bid.