TargetingStay organized with collectionsSave and categorize content based on your preferences.
Page Summary
Ad requests can be targeted using theGADRequestConfigurationobject for global settings and theGAMRequestobject for specific request details.
Key targeting features include setting a child-directed tag for COPPA compliance and a tag for users under the age of consent for GDPR compliance.
You can filter ad content based on a maximum ad content rating and disable ad personalization using the Publisher Privacy Treatment API.
Additional targeting options include adding network extras, providing content URLs for keyword targeting, setting custom key-value pairs, and providing neighboring content URLs for brand safety.
Publisher provided identifiers (PPID) and publisher provided signals (PPS) can be used for audience-based ad delivery controls and improving programmatic monetization.
GADRequestConfigurationis an object that collects targeting information to be applied globally through
theGADMobileAdsshared instance. It can be accessed with the following code:
To ensure that all ad requests apply the request configuration changes, set
the request configuration before youInitializeGoogle Mobile Ads SDK.
Set the age treatment
To help you manage your compliance with applicable privacy regulations related
to children and teens,Google Mobile Ads SDKprovides an age treatment setting. The
age treatment setting lets you indicate whetherGoogle Mobile Ads SDKshould apply
specific ad serving protections for children or teens. When using the setting,Google Mobile Ads SDKincludes atfatparameter in ad requests. Consult your legal
counsel to determine the applicable age treatment for your users based on your
legal and regulatory obligations.
// Indicates that ad requests should have child age treatment.GADMobileAds.sharedInstance.requestConfiguration.ageRestrictedTreatment=GADAgeRestrictedTreatmentChild;
// Indicates that ad requests should have teen age treatment.GADMobileAds.sharedInstance.requestConfiguration.ageRestrictedTreatment=GADAgeRestrictedTreatmentTeen;
// Indicates that ad requests should have unspecified age treatment.GADMobileAds.sharedInstance.requestConfiguration.ageRestrictedTreatment=GADAgeRestrictedTreatmentUnspecified;
As an app developer, you can indicate whether you want Google to treat your
content as child-directed when you make an ad request. When you indicate that
you want Google to treat your content as child-directed, Google takes steps
to disable IBA and remarketing ads on that ad request. The setting options are
as follows:
SettagForChildDirectedTreatmenttotrueto indicate that you want your
content treated as child-directed for purposes of COPPA. This prevents the
transmission of the Advertising Identifier, IDFA.
SettagForChildDirectedTreatmenttofalseto indicate that you don't want
your content treated as child-directed for purposes of COPPA.
Don't settagForChildDirectedTreatmentif you don't want to indicate how
you would like your content treated with respect to COPPA.
The following example indicates that you want your content to be treated as
child-directed for purposes of COPPA:
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.
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 theGeneral
Data Protection Regulation (GDPR). Note that you may have other legal
obligations under GDPR. Review European Union guidance and consult with
your own legal counsel. Note that Google's tools are designed to facilitate
compliance and don't 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 all future ad requests.
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.
The setting can be used with all versions ofGoogle Mobile Ads SDKby
setting thetagForUnderAgeOfConsentproperty on theGADMobileAds.requestConfigurationobject and passing intrue.
SettagForUnderAgeOfConsenttotrueto indicate that you want ad
requests to be handled in a manner suitable for users under the age of
consent. This also prevents the transmission of the Advertising
Identifier, IDFA.
Not settingtagForUnderAgeOfConsentindicates that you don't want ad
requests to be handled in a manner suitable for users under the age of
consent.
The following example indicates that you want TFUA included in your ad request:
The tags to enable thechild-directed settingandtagForUnderAgeOfConsentshouldn't both simultaneously be set totrue.
If they are, the child-directed setting takes precedence.
Ad content filtering
Apps can set a maximum ad content rating for all ad requests using themaxAdContentRatingproperty ofGADRequestConfiguration. This setting applies
to all future ad requests for the remainder of the session. The possible values
for this property are based ondigital content label
classifications, and should be one
of the following constants:
GADMaxAdContentRatingGeneral
GADMaxAdContentRatingParentalGuidance
GADMaxAdContentRatingTeen
GADMaxAdContentRatingMatureAudience
The following code configures all ad requests to specify that ad content
returned should correspond to a Digital Content Label designation no higher thanGADMaxAdContentRatingGeneral.
ThePublisher Privacy Treatment(PPT) API is an optional tool that lets apps indicate whether to turn off ads
personalization for all ad requests using thepublisherPrivacyPersonalizationStateproperty ofGADRequestConfiguration. When using this feature, a publisher
privacy treatment (PPT) parameter is included in all future ad requests for the
remainder of the session.
By default, ad requests to Google are served personalized ads. The following
code turns off ads personalization for all ad requests:
Once you've configured key-value pairs in the Ad Manager UI, set custom
targeting with the key values in an ad request. Line items that target those key
values are then eligible to serve for that ad request. To target multiple values
for one key, enter values as a comma-separated string.
Apps that display dynamic content intended for varying audiences can provide a
short list of URLs through theneighboringContentURLsproperty. Neighboring
content URLs differ from thecontentURLproperty in that they are only used
for brand safety.
Suppose your app displays content from four URLs in a feed that also contains
ads. You can request ads which have a similar content rating to those URLs by
passing them like so:
You can set a publisher provided identifier (PPID) for use in frequency capping,
audience segmentation and targeting, sequential ad rotation, and other
audience-based ad delivery controls across devices.
You can send audience and contextual data aspublisher provided signals(PPS) in ad requests. With PPS, you can use your user data to improve
programmatic monetization by communicating your audience characteristics to
bidders in alltransaction types, using
standard taxonomies, without the need to share user identifiers. Your audience
characteristics can include behavioral and interest-based data (IAB Audience Taxonomy 1.1) and
contextual data (IAB Content Taxonomy 2.2).
Swift
letextras=Extras()extras.additionalParameters=[// Set the demographic to an audience with an "Age Range" of 30-34 and an// interest in mergers and acquisitions."IAB_AUDIENCE_1_1":[6,284],// Set the content to sedan, station wagon and SUV automotive values."IAB_CONTENT_2_2":[4,5,6]]letrequest=AdManagerRequest()request.register(extras)
Objective-C
GADExtras*extras=[[GADExtrasalloc]init];extras.additionalParameters=@{// Set the demographic to an audience with an "Age Range" of 30-34 and an// interest in mergers and acquisitions.@"IAB_AUDIENCE_1_1":@[@6,@284],// Set the content to sedan, station wagon and SUV automotive values.@"IAB_CONTENT_2_2":@[@4,@5,@6]};GAMRequest*request=[GAMRequestrequest];[requestregisterAdNetworkExtras:extras];
FAQ
What targeting gets used when an ad automatically refreshes?
On ad refresh, the previously specifiedGAMRequestobject is used for
targeting again.
To set new targeting, explicitly callloadRequestonGAMBannerViewwith a newGAMRequestobject.
How do I pass extra targeting parameters to mediation networks?
SeeMediationto find out how to send targeting to
mediation networks.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2026-04-29 UTC."],[],["Targeting information for ad requests is managed via `GADRequestConfiguration` for global settings and `GAMRequest` for ad-specific details. Key actions include setting `tagForChildDirectedTreatment` and `tagForUnderAgeOfConsent` for COPPA and GDPR compliance, respectively. Apps can also filter content using `maxAdContentRating`. `publisherPrivacyPersonalizationState` disables ad personalization. Content URL, custom targeting, neighboring content URLs, publisher provided identifiers (PPID) and publisher provided signals (PPS) are set through `GAMRequest` for detailed targeting.\n"]]
