이는 게시자가
캘리포니아 소비자 개인 정보 보호법 (CCPA)에 따라 게시자는 Google 양방향 미디어 광고 SDK를 통해
두 개의 다른 매개변수를 사용하여
제한적인 데이터 처리 (RDP) SDK
게시자는 다음을 활용하여 광고 요청 수준에서 RDP를 설정할 수 있습니다.
매개변수:
[null,null,["최종 업데이트: 2025-07-25(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 enable restricted data processing (RDP) for CCPA compliance.\u003c/p\u003e\n"],["\u003cp\u003eWhen either RDP or \u003ccode\u003eus_privacy\u003c/code\u003e parameter is used, Google limits the use of certain identifiers and data processed in ad serving, aiding publishers in CCPA compliance.\u003c/p\u003e\n"],["\u003cp\u003ePublishers can use Google's RDP signal by adding \u003ccode\u003e&rdp=1\u003c/code\u003e to ad tag parameters, while IAB's signal is enabled using the \u003ccode\u003eus_privacy\u003c/code\u003e parameter with a compliant string value like \u003ccode\u003e"1YNN"\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThis guide helps publishers implement these options on a per-ad-request basis to manage data usage and potentially aid in CCPA compliance efforts.\u003c/p\u003e\n"]]],[],null,["# Enable restricted data processing\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\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\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```"]]
