Untuk mendiskusikan dan memberikan masukan tentang produk kami, bergabunglah ke channel Discord Ad Manager resmi di server Komunitas Iklan dan Pengukuran Google.
Untuk membantu penayang mematuhi
California Consumer Privacy Act (CCPA), Google Interactive Media Ads SDK memungkinkan penayang
menggunakan dua parameter berbeda untuk menunjukkan apakah Google harus mengaktifkan
pemrosesan data yang dibatasi (RDP). SDK
memberi penayang kemampuan untuk menetapkan RDP di tingkat permintaan iklan menggunakan parameter berikut:
Jika salah satu parameter digunakan, Google membatasi penggunaan ID unik tertentu dan data lain yang diproses dalam penyediaan layanan kepada penayang.
Penayang harus memutuskan sendiri bagaimana pemrosesan data yang dibatasi dapat mendukung rencana kepatuhan mereka dan kapan pemrosesan data yang dibatasi harus diaktifkan. Anda dapat menggunakan kedua parameter opsional secara bersamaan, meskipun keduanya memiliki efek yang sama pada penayangan iklan Google.
Panduan ini dimaksudkan untuk membantu penayang memahami langkah-langkah yang diperlukan untuk mengaktifkan opsi ini berdasarkan per permintaan iklan.
Sinyal RDP
Untuk memberi tahu Google bahwa RDP harus diaktifkan menggunakan sinyal Google, tambahkan &rdp=1 ke
parameter tag iklan Anda, seperti yang ditunjukkan dalam contoh berikut:
Untuk memberi tahu Google bahwa RDP harus diaktifkan menggunakan sinyal IAB, gunakan parameter tag iklan
us_privacy. Pastikan nilai string yang Anda gunakan mematuhi
spesifikasi IAB.
Cuplikan di bawah menunjukkan cara membuat permintaan iklan dengan parameter IAB
"1YNN":
[null,null,["Terakhir diperbarui pada 2025-09-06 UTC."],[[["\u003cp\u003eGoogle's Interactive Media Ads SDK offers two parameters, Google's RDP and IAB's \u003ccode\u003eus_privacy\u003c/code\u003e, for publishers to signal restricted data processing in compliance with the CCPA.\u003c/p\u003e\n"],["\u003cp\u003eWhen either parameter is used, Google limits its use of certain unique identifiers and data to support publisher compliance.\u003c/p\u003e\n"],["\u003cp\u003ePublishers can choose how and when to enable restricted data processing using these parameters, which are supported for Ad Manager, AdSense, and AdMob ad tags.\u003c/p\u003e\n"],["\u003cp\u003eTo enable RDP, append \u003ccode\u003e&rdp=1\u003c/code\u003e for Google's signal or \u003ccode\u003e&us_privacy=<IAB string>\u003c/code\u003e for IAB's signal to your ad tag parameters, ensuring the IAB string adheres to their specification.\u003c/p\u003e\n"],["\u003cp\u003eFor third-party ad providers, publishers should contact them directly regarding restricted data processing support.\u003c/p\u003e\n"]]],[],null,["Select platform: [HTML5](/interactive-media-ads/docs/sdks/html5/client-side/ccpa \"View this page for the HTML5 platform docs.\") [Android](/interactive-media-ads/docs/sdks/android/client-side/ccpa \"View this page for the Android platform docs.\") [iOS](/interactive-media-ads/docs/sdks/ios/client-side/ccpa \"View this page for the iOS platform docs.\") [tvOS](/interactive-media-ads/docs/sdks/tvos/client-side/ccpa \"View this page for the tvOS platform docs.\")\n\n\nTo help publishers toward compliance with the [California Consumer Privacy Act (CCPA)](//support.google.com/admob/answer/9561022), the Google Interactive Media Ads SDK allows publishers\nto use two different parameters to indicate whether Google should enable\n[restricted data processing](//privacy.google.com/businesses/rdp/) (RDP). The SDK\nprovides publishers with the ability to set RDP at an ad request level utilizing the following\nparameters:\n\n- Google's RDP\n- [IAB-defined](//github.com/InteractiveAdvertisingBureau/USPrivacy/blob/master/CCPA/US%20Privacy%20String.md) `us_privacy`\n\n| **Note:** The RDP and `us_privacy` ad tag parameters are supported for ad tags originating from Ad Manager, AdSense, and AdMob. If you use a third-party ad provider, contact the provider about supporting restricted data processing.\n\n\nWhen either parameter is used, Google restricts how it uses certain unique identifiers and other\ndata processed in the provision of services to publishers.\n\n\nPublishers should decide for themselves how restricted data processing can support their\ncompliance plans and when it should be enabled. It is possible to use both optional parameters at\nthe same time, although they have the same effect on Google's ad serving.\n\n\nThis guide is intended to help publishers understand the steps required to enable these options on\na per-ad-request basis.\n\nRDP signal\n\n\nTo notify Google that RDP should be enabled using Google's signal, append `&rdp=1` to\nyour ad tag parameters, as shown in the following example: \n\n```scdoc\nhttps://pubads.g.doubleclick.net/gampad/ads?iu=/21775744923/external/single_ad_samples&output=vast&rdp=1\n```\n\nIAB signal\n\n\nTo notify Google that RDP should be enabled using IAB's signal, use the ad tag parameter\n`us_privacy`. Make sure that the string value you use is compliant with the\n[IAB specification](//github.com/InteractiveAdvertisingBureau/USPrivacy/blob/master/CCPA/US%20Privacy%20String.md).\n\n\nThe snippet below demonstrates how to create an ad request with the IAB parameter\n`\"1YNN\"`: \n\n```scdoc\nhttps://pubads.g.doubleclick.net/gampad/ads?iu=/21775744923/external/single_ad_samples&output=vast&us_privacy=1YNN\n```"]]
