[null,null,["最后更新时间 (UTC):2025-08-21。"],[[["\u003cp\u003eThe Google Interactive Media Ads SDK allows publishers to enable restricted data processing (RDP) for CCPA compliance using Google's RDP or IAB's \u003ccode\u003eus_privacy\u003c/code\u003e signals.\u003c/p\u003e\n"],["\u003cp\u003ePublishers can signal RDP to Google by appending \u003ccode\u003e&rdp=1\u003c/code\u003e to ad tag parameters or using the \u003ccode\u003eus_privacy\u003c/code\u003e ad tag parameter with a compliant IAB string value.\u003c/p\u003e\n"],["\u003cp\u003eWhile publishers can utilize both RDP signaling options, they have the same impact on Google's ad serving and should be chosen based on individual compliance needs.\u003c/p\u003e\n"],["\u003cp\u003eThese parameters are supported for ad requests from Ad Manager, AdSense, and AdMob; for other providers, publishers should check with them about supporting restricted data processing.\u003c/p\u003e\n"]]],["Publishers can enable restricted data processing (RDP) for ad requests to comply with the California Consumer Privacy Act (CCPA). This is done by using either Google's `&rdp=1` parameter or the IAB-defined `us_privacy` parameter in ad tags. When applied, Google limits its use of certain data in providing services. Both parameters have the same effect on ad serving and can be used simultaneously. Enabling RDP with each of these is demonstrated in the provided code snippets.\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```gdscript\nfunction requestLiveStream(assetKey, apiKey) {\n var streamRequest = new google.ima.dai.api.LiveStreamRequest();\n streamRequest.assetKey = assetKey;\n streamRequest.apiKey = apiKey;\n streamRequest.adTagParameters = {\"rdp\": 1};\n streamManager.requestStream(streamRequest);\n}\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```gdscript\nfunction requestLiveStream(assetKey, apiKey) {\n var streamRequest = new google.ima.dai.api.LiveStreamRequest();\n streamRequest.assetKey = assetKey;\n streamRequest.apiKey = apiKey;\n streamRequest.adTagParameters = {\"us_privacy\": \"1YNN\"};\n streamManager.requestStream(streamRequest);\n}\n```"]]