Forwarding consent to the IMA SDK
By default, ad requests to Google serve personalized ads, with ad selection based on both the content of the web page or app and the history of the individual user visiting it. Google also supports serving non-personalized ads. Learn more about personalized and non-personalized ads.
Using Funding Choices
When you have Funding Choices included in your site, the IMA SDK will automatically detect its presence and populate the consent setting in your ad tag. No further action is needed on your part.
Forwarding consent without Funding Choices
To force non-personalized ads, you can append
&npa=1 to your ad tag
to specify that only non-personalized ad content should be returned.
Tagging users as 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 GDPR affects publishers.
When using this feature, a TFUA (Tag For Users under the Age of Consent in Europe) 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. The parameter does not affect your use of Ad Manager key-values. Consequently, you must ensure that your use of key-values is compliant with GDPR.
Including the TFUA parameter in an ad request takes precedence over any applicable site-level settings.
To include this tag on all ad requests made from your implementation,
&tfua=1 to your ad tag.