Enable restricted data processing

  • The Google Interactive Media Ads SDK helps publishers comply with CCPA by allowing them to use two parameters to enable restricted data processing (RDP).

  • Publishers can set RDP at an ad request level using either Google's RDP signal or the IAB-defined us_privacy parameter.

  • Enabling either RDP parameter restricts how Google uses certain unique identifiers and other data when providing services to publishers.

  • Publishers must decide how RDP supports their compliance plans and when to enable it.

  • This guide explains how to enable RDP on a per-ad-request basis using either the Google RDP signal by appending &rdp=1 or the IAB us_privacy parameter with a compliant string value.

Select platform: HTML5 Android iOS tvOS Roku

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:

https://pubads.g.doubleclick.net/gampad/ads?iu=/21775744923/external/single_ad_samples&output=vast&rdp=1

IAB signal

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":

https://pubads.g.doubleclick.net/gampad/ads?iu=/21775744923/external/single_ad_samples&output=vast&us_privacy=1YNN