AI-generated Key Takeaways
-
Google's Mobile Ads SDK enables publishers to comply with U.S. state privacy laws by offering restricted data processing (RDP) options.
-
Publishers can signal RDP using either Google's
rdp
parameter or the IAB-definedIABUSPrivacy_String
in ad requests. -
When RDP is enabled, Google limits data usage and shows non-personalized ads, overriding UI settings.
-
Mediation requires adding partners to the CPRA list in Ad Manager and consulting partner documentation for compliance options.
To help you comply with U.S. states privacy laws, the Google Mobile Ads SDK lets you use Google restricted data processing (RDP) parameter to indicate whether to enable RDP. Google also supports the Global Privacy Platform (GPP) for applicable US states. When the Google Mobile Ads SDK uses either signal, the SDK restricts certain unique identifiers and other data is processed in the provision of services to you.
You must decide how restricted data processing can support your compliance plans and when to enable. Determine whether to use the RDP parameter directly or signaling consent and privacy choices with the GPP Specification.
This guide helps you enable RDP on a per-ad request basis and use the GPP signal.
Enable the RDP signal
To notify Google that RDP must be enabled using Google's RDP signal, insert
the key rdp
as an extra parameter with a value of 1
.
final request = AdManagerAdRequest(extras: {'rdp': '1'});
Use the IAB GPP Signal
If you collect consent decisions with a consent management platform or your own custom messaging, the Google Mobile Ads SDK respects GPP signals written to local storage. The User Messaging Platform (UMP) SDK supports writing the GPP signal. To gather US state consent, see US IAB Support.