Stay organized with collectionsSave and categorize content based on your preferences.
To help publishers toward compliance with theCalifornia Consumer Privacy Act (CCPA), the Google Interactive Media Ads SDK allows publishers
to use two different parameters to indicate whether Google should enablerestricted data processing(RDP). The SDK
provides publishers with the ability to set RDP at an ad request level utilizing the following
parameters:
When either parameter is used, Google restricts how it uses certain unique identifiers and other
data processed in the provision of services to publishers.
Publishers should decide for themselves how restricted data processing can support their
compliance plans and when it should be enabled. It is possible to use both optional parameters at
the same time, although they have the same effect on Google's ad serving.
This guide is intended to help publishers understand the steps required to enable these options on
a per-ad-request basis.
RDP signal
To notify Google that RDP should be enabled using Google's signal, append&rdp=1to
your ad tag parameters, as shown in the following example:
To notify Google that RDP should be enabled using IAB's signal, use the ad tag parameterus_privacy. Make sure that the string value you use is compliant with theIAB specification.
The snippet below demonstrates how to create an ad request with the IAB parameter"1YNN":
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 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 for CCPA compliance.\u003c/p\u003e\n"],["\u003cp\u003eBy using either \u003ccode\u003e&rdp=1\u003c/code\u003e or \u003ccode\u003eus_privacy\u003c/code\u003e with a compliant value (e.g., "1YNN") in ad tag parameters, publishers can signal Google to restrict data usage.\u003c/p\u003e\n"],["\u003cp\u003ePublishers are responsible for determining when to enable restricted data processing based on their CCPA compliance strategies.\u003c/p\u003e\n"],["\u003cp\u003eBoth RDP and \u003ccode\u003eus_privacy\u003c/code\u003e parameters achieve the same effect on Google's ad serving and can be used simultaneously, although redundant.\u003c/p\u003e\n"],["\u003cp\u003eThis guide provides instructions for implementing these options on a per-ad-request basis for Ad Manager, AdSense, and AdMob.\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```gdscript\nSub loadStream()\n ...\n request = sdk.CreateStreamRequest()\n if m.top.streamData.type = \"live\"\n request.assetKey = m.top.streamData.assetKey\n else\n request.contentSourceId = m.top.streamData.contentSourceId\n request.videoId = m.top.streamData.videoId\n end if\n request.apiKey = m.top.streamData.apiKey\n request.player = m.player\n request.adTagParameters = \"rdp=1\";\n requestResult = sdk.requestStream(request)\n ...\nEnd Sub\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\nSub loadStream()\n ...\n request = sdk.CreateStreamRequest()\n if m.top.streamData.type = \"live\"\n request.assetKey = m.top.streamData.assetKey\n else\n request.contentSourceId = m.top.streamData.contentSourceId\n request.videoId = m.top.streamData.videoId\n end if\n request.apiKey = m.top.streamData.apiKey\n request.player = m.player\n request.adTagParameters = \"us_privacy=1YNN\";\n requestResult = sdk.requestStream(request)\n ...\nEnd Sub\n```"]]
