AI-generated Key Takeaways
-
Publishers must obtain user consent for data collection and personalized ads in the European Economic Area (EEA) to comply with the EU ePrivacy Directive and GDPR.
-
The IMA SDK can automatically forward consent obtained through the User Messaging Platform (UMP) SDK or any other IAB TCF v2.0-compliant consent management provider.
-
Publishers can serve non-personalized ads by appending
&npa=1to their ad tag, and ads for users under the age of consent can be tagged with&tfua=1to disable personalized advertising and third-party ad vendor requests. -
GDPR requires publishers to provide a way for users to revoke their consent at any time, which can be implemented through privacy options within the app.
Under Google's EU User Consent Policy, you must make certain disclosures to your users in the European Economic Area (EEA) and obtain their consent for the use of cookies or other local storage where legally required, and for the collection, sharing, and use of personal data for ads personalization. This policy reflects the requirements of the EU ePrivacy Directive and the General Data Protection Regulation (GDPR).
User Messaging Platform SDK
For information on obtaining consent using the User Messaging Platform (UMP) SDK, see our User Messaging Platform SDK guide. Consent obtained through the UMP SDK are automatically forwarded to the IMA SDK.
Consent revocation
GDPR requires consent revocation to allow users to withdraw their consent choices at any time. See Privacy options to implement a way for users to withdraw their consent choices.
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 user visiting it. Google also supports serving non-personalized ads. Learn more about personalized and non-personalized ads
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.
This is accomplished with the adTagParameters property, like so:
private StreamRequest buildStreamRequest() {
...
StreamRequest request = mSdkFactory.createLiveStreamRequest(
TEST_ASSET_KEY, null, mDisplayContainer);
Map adTagParameters = new HashMap();
adTagParameters.put("npa", 1);
request.setAdTagParameters(adTagParameters);
return request;
}
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,
append &tfua=1 to your ad tag.
private StreamRequest buildStreamRequest() {
...
StreamRequest request = mSdkFactory.createLiveStreamRequest(
TEST_ASSET_KEY, null, mDisplayContainer);
Map adTagParameters = new HashMap();
adTagParameters.put("tfua", 1);
request.setAdTagParameters(adTagParameters);
return request;
}