This guide explains how to provide targeting information to an ad request.
RequestConfiguration is an object that collects targeting information to be applied globally.
To update the request configuration retrieve the current configuration and perform any desired updates as follows:
For purposes of the Children's Online Privacy Protection Act (COPPA), there is a setting called "tag for child-directed treatment". By setting this tag, you certify that this notification is accurate and you are authorized to act on behalf of the owner of the app. You understand that abuse of this setting may result in termination of your Google account.
Note: It may take some time for this designation to take effect in applicable Google services.
As an app developer, you can indicate whether you want Google to treat your content as child-directed when you make an ad request. If you indicate that you want Google to treat your content as child-directed, we take steps to disable IBA and remarketing ads.
TAG_FOR_CHILD_DIRECTED_TREATMENT_TRUEto indicate that you want your content treated as child-directed for purposes of COPPA.
TAG_FOR_CHILD_DIRECTED_TREATMENT_FALSEto indicate that you don't want your content treated as child-directed for purposes of COPPA.
TAG_FOR_CHILD_DIRECTED_TREATMENT_UNSPECIFIEDif you do not wish to indicate how you would like your content treated with respect to COPPA in ad requests.
The following example indicates that you want your content treated as child-directed for purposes of COPPA:
Users under the age of consent
You can mark your ad requests to receive treatment for users in the European Economic Area (EEA) under the age of consent. This feature is designed to help facilitate compliance with the General Data Protection Regulation (GDPR). Note that you may have other legal obligations under GDPR. Please review the European Union’s guidance and consult with your own legal counsel. Please remember that Google's tools are designed to facilitate compliance and do not relieve any particular publisher of its obligations under the law. Learn more about how the GDPR affects publishers.
When using this feature, a Tag For Users under the Age of Consent in Europe (TFUA) parameter will be included in the ad request. This parameter disables personalized advertising, including remarketing, for that specific ad request. It also disables requests to third-party ad vendors, such as ad measurement pixels and third-party ad servers.
Like child-directed settings, there is a method in
RequestConfiguration for setting the TFUA parameter:
setTagForUnderAgeOfConsent, with the following options:
TAG_FOR_UNDER_AGE_OF_CONSENT_TRUEto indicate that you want the ad request to receive treatment for users in the European Economic Area (EEA) under the age of consent.
TAG_FOR_UNDER_AGE_OF_CONSENT_FALSEto indicate that you want the ad request to not receive treatment for users in the European Economic Area (EEA) under the age of consent.
TAG_FOR_UNDER_AGE_OF_CONSENT_UNSPECIFIEDto indicate that you have not specified whether the ad request should receive treatment for users in the European Economic Area (EEA) under the age of consent.
The following example indicates that you want TFUA included in your ad request:
The tags to enable the Child-directed setting and
setTagForUnderAgeOfConsent should not both simultaneously be set to true. If they are, the child-directed setting takes precedence.
Ad content filtering
Apps can set a maximum ad content rating for their ad requests using the
setMaxAdContentRating() function. AdMob ads returned have a content rating at or below that level. The possible values for this network extra are based on digital content label classifications, and should be one of the following values:
The following code configures an
RequestConfiguration object to specify that ad content returned should correspond to a digital content label designation no higher than G:
Note: Content rating filter settings specified via the SDK will override any settings configured using the AdMob UI.
The AdRequest object collects targeting information to be sent with an ad request.
Consent from European Users
This is legacy information, you should look into the User Messaging Platform for the current approach that automatically applies this information
Ads served by Google can be categorized as personalized or non-personalized, both requiring consent from users in the EEA. By default, ad requests to Google serve personalized ads, with ad selection based on the user's previously collected data. Google also supports configuring ad requests to serve non-personalized ads. Learn more about personalized and non-personalized ads.
You should ensure that somewhere in your application you ask for consent from your users to serve personalised ads. Once you have retrieved this response from your user if they have denied consent then ensure you pass it to your
The default behavior of the Google Mobile Ads SDK is to serve personalized ads. If a user has consented to receive only non-personalized ads, you can configure an
AdRequest object with the following code to specify that only non-personalized ads should be returned:
You must add this to all your