Stay organized with collections
Save and categorize content based on your preferences.
To help publishers toward compliance with the
California Consumer Privacy Act (CCPA), the Google Interactive Media Ads SDK allows publishers
to use two different parameters to indicate whether Google should enable
restricted 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=1 to
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 parameter
us_privacy. Make sure that the string value you use is compliant with the
IAB 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-01 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,["To 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```"]]