To help publishers comply with U.S. states privacy laws, the Google Mobile 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 signals:
- Google's RDP
- IAB-defined
IABUSPrivacy_String
When either parameter is used, Google restricts how it uses certain unique identifiers and other data processed in the provision of services to publishers. As a result, Google will only show non-personalized ads. These parameters override the RDP settings in the UI.
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, insert
the key rdp as an extra parameter with a value of 1.
final request = AdManagerAdRequest(extras: {'rdp': '1'});
IAB signal
To notify Google that RDP should be enabled using IAB's signal, insert the key
IABUSPrivacy_String as an extra parameter. Make sure that the string value you
use is compliant with the IAB
specification.
final request = AdManagerAdRequest(extras: {'IABUSPrivacy_String': 'IAB_STRING'});
Mediation
If you use mediation:
Follow the steps in Select a data processing setting to add your mediation partners to the CPRA ad partners list in the Ad Manager UI.
Consider writing the IAB signal using
UserDefaultsso mediation partner SDKs that are compliant with the IAB Specification can also read the signal.Consult each ad network partner's documentation to determine what options they offer to help towards CPRA compliance.