The serving restriction dimension can be used in your AdMob Network, Bidding, and Mediation reports to compare personalized ads to non-personalized ads. This can help you understand which restrictions lead to ads not being personalized, and how these restrictions impact your revenue.
Note: Serving restriction data is not available in AdMob reporting prior to March 13, 2021. Also note that serving restriction data is only available for the AdMob Network and Open Bidding ad sources.
It is not available for third-party waterfall ad sources.
When you add this dimension to your reports, you can view which serving restrictions are affecting your AdMob traffic and how:
- Limited ads: Ads that are served in a limited way in the absence of consent for the use of cookies, mobile device identifiers, or other local storage.
- Restricted data processing (RDP): Publisher chose to enable restricted data processing (for example, using AdMob’s blocking controls) for compliance with the California Privacy Rights Act (CPRA).
- Non-personalized ads (NPA): Publisher chose to enable non-personalized ads (for example, using AdMob’s blocking controls) for compliance with Google’s EU User Consent Policy and GDPR. Also applies to ad requests subject to the LGPD.
- Basic ads: IAB TCF v2.0 basic ads were served.
- 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: Ads that are personalized using IDFA, Android Ad ID, or other available user identifiers.
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.
Ad serving restrictions due to policy issues are not included in the serving restriction dimension. Review any policy issues and their effect on ad serving in the Policy center of your account.
Expand all Collapse all
