[null,null,["最后更新时间 (UTC):2025-08-21。"],[[["\u003cp\u003ePublishers 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.\u003c/p\u003e\n"],["\u003cp\u003eThe 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.\u003c/p\u003e\n"],["\u003cp\u003ePublishers can serve non-personalized ads by appending \u003ccode\u003e&npa=1\u003c/code\u003e to their ad tag, and ads for users under the age of consent can be tagged with \u003ccode\u003e&tfua=1\u003c/code\u003e to disable personalized advertising and third-party ad vendor requests.\u003c/p\u003e\n"],["\u003cp\u003eGDPR 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.\u003c/p\u003e\n"]]],["Users in the EEA must provide consent for cookies and personal data use, adhering to the EU User Consent Policy, ePrivacy Directive, and GDPR. Consent can be obtained through the User Messaging Platform (UMP) SDK, automatically forwarding to the IMA SDK. Consent revocation must be implemented. To force non-personalized ads, append `&npa=1`; for users under the age of consent, append `&tfua=1` to the ad tag, disabling personalized ads and third-party vendor requests.\n"],null,["# Request consent from EU users\n\n| **Note:** Consent reporting requires IMA SDK for Android version 3.1.3 or higher\n\nUnder Google's [EU User Consent\nPolicy](//www.google.com/about/company/consentstaging.html),\nyou must make certain disclosures to your users in the European\nEconomic Area (EEA) and obtain their consent for the use of cookies or\nother local storage where legally required, and for the collection,\nsharing, and use of personal data for ads personalization. This policy\nreflects the requirements of the EU ePrivacy Directive and the General\nData Protection Regulation (GDPR).\n\nUser Messaging Platform SDK\n---------------------------\n\nFor information on obtaining consent using the User Messaging Platform (UMP)\nSDK, see our [User Messaging Platform SDK\nguide](/ad-manager/dynamic-ad-insertion/sdk/android/privacy). Consent obtained through the UMP\nSDK are automatically forwarded to the IMA SDK.\n\nConsent revocation\n------------------\n\nGDPR requires [consent revocation](//support.google.com/admanager/answer/10114217)\nto allow users to withdraw their consent choices at any time. See\n[Privacy options](/ad-manager/dynamic-ad-insertion/sdk/android/privacy#privacy_options)\nto implement a way for users to withdraw their consent choices.\n\nForwarding consent to the IMA SDK\n---------------------------------\n\n| **Note:** On version 3.16.2 or higher, the IMA SDK automatically populates the TC String in the ad tag from the UMP SDK or any other IAB TCF v2.0-compliant consent management provider.\n\nBy default, ad requests to Google serve personalized ads, with ad selection\nbased on both the content of the web page or app and the history of the user\nvisiting it. Google also supports serving non-personalized ads.\n[Learn more about personalized and non-personalized\nads](//support.google.com/admanager/answer/9005435)\n\nTo force non-personalized ads, you can append `&npa=1` to your ad tag\nto specify that only non-personalized ad content should be returned.\n\nThis is accomplished with the `adTagParameters` property, like so: \n\n```scdoc\nprivate StreamRequest buildStreamRequest() {\n ...\n StreamRequest request = mSdkFactory.createLiveStreamRequest(\n TEST_ASSET_KEY, null, mDisplayContainer);\n Map adTagParameters = new HashMap();\n adTagParameters.put(\"npa\", 1);\n request.setAdTagParameters(adTagParameters);\n return request;\n}\n```\n\n\u003cbr /\u003e\n\nTagging users as under the age of consent\n-----------------------------------------\n\nYou can mark your ad requests to receive treatment for users in the European\nEconomic Area (EEA) under the age of consent. This feature is designed to\nhelp facilitate compliance with the [General Data Protection Regulation\n(GDPR)](//eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32016R0679).\nNote that you may have other legal obligations under GDPR. Please review\nthe European Union's guidance and consult with your own legal counsel.\nPlease remember that Google's tools are designed to facilitate compliance\nand do not relieve any particular publisher of its obligations under the\nlaw. [Learn more about how GDPR affects\npublishers](//support.google.com/admanager/answer/7666366)\n\nWhen using this feature, a TFUA (Tag For Users under the Age of Consent in\nEurope) parameter will be included in the ad request. This parameter disables\n[personalized advertising](//support.google.com/admanager/answer/9005435),\nincluding remarketing, for that specific ad request. It also disables\nrequests to third-party ad vendors, such as ad measurement pixels and\nthird-party ad servers. The parameter does not affect your use of\nAd Manager key-values. Consequently, you must ensure that your use of\nkey-values is compliant with GDPR.\n\nIncluding the TFUA parameter in an ad request takes precedence over any\napplicable site-level settings.\n\nTo include this tag on all ad requests made from your implementation,\nappend `&tfua=1` to your ad tag. \n\n```scdoc\nprivate StreamRequest buildStreamRequest() {\n ...\n StreamRequest request = mSdkFactory.createLiveStreamRequest(\n TEST_ASSET_KEY, null, mDisplayContainer);\n Map adTagParameters = new HashMap();\n adTagParameters.put(\"tfua\", 1);\n request.setAdTagParameters(adTagParameters);\n return request;\n}\n```\n\n\u003cbr /\u003e\n\nThe example above uses a live stream request, but the same applies to VOD streams."]]