向歐盟使用者徵求同意聲明
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
根據 Google 的《歐盟地區使用者同意授權政策》，您必須向歐洲經濟區 (EEA) 的使用者揭露特定資訊，並在法律要求的情況下，取得他們對使用 Cookie 或其他本機儲存空間的同意聲明，以及對蒐集、分享及使用個人資料以利廣告個人化的同意聲明。本政策是配合《歐盟地區電子通訊隱私指令》和《一般資料保護規則》(GDPR) 而制定。
將同意聲明轉送至 IMA SDK
根據預設，傳送給 Google 的廣告請求會放送個人化廣告，且會同時根據網頁/應用程式內容及使用者瀏覽記錄來選擇廣告。此外，Google 也支援放送非個人化廣告。
進一步瞭解個人化和非個人化廣告
使用營利成長選項
如果網站中包含資助選項，IMA SDK 會自動偵測到該選項，並在廣告代碼中填入同意聲明設定。如要啟用這項功能，請在網站上載入 Google 發布商廣告代碼 (GPT)。您無須採取任何行動。
不使用營利成長選項轉送同意聲明
如要強制放送非個人化廣告，可以在廣告代碼中附加 &npa=1，指定只應傳回非個人化廣告內容。
將使用者標記為未滿規定年齡
針對未滿規定年齡的歐洲經濟區使用者，您可以在廣告請求中加上相關處理標記。這項功能的立意是協助發布商遵守《一般資料保護規則》(GDPR)。請注意，您可能還有 GDPR 所衍生的其他法律義務。請查看歐盟發布的指南並諮詢您的法律顧問。提醒您，Google 提供工具的用意是協助發布商遵守規定，而非方便發布商規避法定義務。進一步瞭解 GDPR 對發布商的影響
使用這項功能時，廣告請求將會包含 TFUA (未滿規定年齡的歐洲使用者標記) 參數。這個參數會針對特定廣告請求停用個人化廣告功能 (包括再行銷)，並停止向第三方廣告供應商 (例如廣告評估像素和第三方廣告伺服器) 提出其他請求。這個參數不會影響您使用 Ad Manager 的鍵/值，因此請務必確認您的鍵/值用法符合 GDPR 規範。
如果在廣告請求中加入 TFUA 參數，該參數的效力將優先於任何相關網站層級設定。
如要在導入作業發出的所有廣告請求中加入這個代碼，請在廣告代碼中附加 &tfua=1。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-09-06 (世界標準時間)。
[null,null,["上次更新時間：2025-09-06 (世界標準時間)。"],[[["\u003cp\u003ePublishers serving users in the European Economic Area (EEA) must comply with Google's EU User Consent Policy, including disclosing data collection practices and obtaining consent for cookies, data usage, and ad personalization.\u003c/p\u003e\n"],["\u003cp\u003ePublishers can forward consent obtained through Funding Choices to the IMA SDK automatically using Google Publisher Tags or by manually configuring ad tags to indicate consent status for personalized or non-personalized ads.\u003c/p\u003e\n"],["\u003cp\u003eTo comply with GDPR regulations concerning users under the age of consent, publishers can use the \u003ccode\u003e&tfua=1\u003c/code\u003e parameter in ad requests, which disables personalized advertising and third-party vendor requests for that specific ad request.\u003c/p\u003e\n"],["\u003cp\u003eWhile Google provides tools to assist with compliance, publishers are ultimately responsible for fulfilling their legal obligations under GDPR and should seek guidance from legal counsel when necessary.\u003c/p\u003e\n"]]],[],null,["Select platform: [HTML5](/interactive-media-ads/docs/sdks/html5/client-side/consent \"View this page for the HTML5 platform docs.\") [Android](/interactive-media-ads/docs/sdks/android/client-side/consent \"View this page for the Android platform docs.\") [iOS](/interactive-media-ads/docs/sdks/ios/client-side/consent \"View this page for the iOS platform docs.\") [tvOS](/interactive-media-ads/docs/sdks/tvos/client-side/consent \"View this page for the tvOS platform docs.\")\n\n\u003cbr /\u003e\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\n\u003cbr /\u003e\n\nForwarding consent to the IMA SDK\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\nUsing Funding Choices\n\nWhen you have [Funding\nChoices](//support.google.com/fundingchoices#topic=7074184) included in your\nsite, the IMA SDK will automatically detect its presence and populate the\nconsent setting in your ad tag. For this to happen, [Google Publisher Tags\n(GPT)](/publisher-tag/guides/get-started) must be loaded on your site. No\nfurther action is needed on your part.\n\nForwarding consent without Funding Choices\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\n\u003cbr /\u003e\n\nTagging users as under the age of consent\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\u003cbr /\u003e"]]
