Select platform: [HTML5](https://developers.google.com/ad-manager/dynamic-ad-insertion/sdk/html5/ccpa "View this page for the HTML5 platform docs.") [Android](https://developers.google.com/ad-manager/dynamic-ad-insertion/sdk/android/ccpa "View this page for the Android platform docs.") [iOS](https://developers.google.com/ad-manager/dynamic-ad-insertion/sdk/ios/ccpa "View this page for the iOS platform docs.") [tvOS](https://developers.google.com/ad-manager/dynamic-ad-insertion/sdk/tvos/ccpa "View this page for the tvOS platform docs.") [Roku](https://developers.google.com/ad-manager/dynamic-ad-insertion/sdk/roku/ccpa "View this page for the Roku platform docs.")

<br />

To help you comply with [US states privacy laws](https://support.google.com/admob/answer/9561022),
the Google Interactive Media Ads SDK lets you use the following to parameters
to indicate whether Google must enable
[restricted data processing](https://privacy.google.com/businesses/rdp/) (RDP).
The SDK provides publishers with the ability to set RDP at an ad request level
utilizing the following parameters:

- [Google RDP](https://support.google.com/admanager/answer/14117973)
- [IAB's Global Privacy Platform (GPP) strings](https://support.google.com/admanager/answer/14117049)
- [\[DEPRECATED\] IAB US Privacy (`us_privacy`) strings](https://support.google.com/admanager/answer/9603027)

> [!NOTE]
> **Note:** The RDP, GPP, 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.

When you use one of these parameters to indicate that the user opts-out of data
sharing, Google restricts the processing of user identifiers and other data,
like demographic targeting. Under RDP, Google serves non-personalized ads only,
when provision of services to you.

You must decide how restricted data processing can support your
compliance plans. You must also decide when to enable RDP. You can
use one or more of these optional parameters at the same time, although Google
always applies the most restrictive treatment. For example, if either `RDP=1`,
the GPP string, or the `us_privacy` string indicates a user opts out, Google ad
serving enables RDP.

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:

    function requestLiveStream(assetKey, apiKey) {
      var streamRequest = new google.ima.dai.api.LiveStreamRequest();
      streamRequest.assetKey = assetKey;
      streamRequest.apiKey = apiKey;
      streamRequest.adTagParameters = {"rdp": 1};
      streamManager.requestStream(streamRequest);
    }

## IAB GPP signals

To notify Google that RDP should be enabled using IAB's signals, use the ad tag
parameters `gpp={gpp string}` and `gpp_sid={gpp section id}`. For more details
about using GPP signals, see
[Supporting the IAB's Global Privacy Platform](https://support.google.com/admanager/answer/14117049).
Google triggers RDP when certain criteria specific to the US National,
California, Colorado, Connecticut, Florida, and Virginia GPP strings are met.
For details on Global Privacy Protocol specifications, see the related section
in the previously linked article.

    function requestLiveStream(assetKey, apiKey) {
      var streamRequest = new google.ima.dai.api.LiveStreamRequest();
      streamRequest.assetKey = assetKey;
      streamRequest.apiKey = apiKey;
      streamRequest.adTagParameters = {
    "gpp": "gpp_string",
    "gpp_sid": "gpp_section_id"
    };
      streamManager.requestStream(streamRequest);
    }

> [!WARNING]
> **Warning:** The IAB deprecated the US Privacy String in January 2024, in favor of GPP. Google Ad Manager continues to read the US Privacy String in order to provide backward support to partners. We recommend migrating to GPP strings.