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.
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.
[[["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-22 UTC."],[[["\u003cp\u003eGoogle Mobile Ads SDK enables Restricted Data Processing (RDP) using Google's signal or the IAB-defined \u003ccode\u003eIABUSPrivacy_String\u003c/code\u003e, allowing publishers to comply with U.S. state privacy laws.\u003c/p\u003e\n"],["\u003cp\u003eEnabling RDP signals restricts Google's use of certain data, resulting in the display of non-personalized ads and overriding RDP UI settings.\u003c/p\u003e\n"],["\u003cp\u003ePublishers can implement RDP on a per-ad request basis using extra parameters, \u003ccode\u003erdp\u003c/code\u003e for Google's signal and \u003ccode\u003eIABUSPrivacy_String\u003c/code\u003e for IAB's signal.\u003c/p\u003e\n"],["\u003cp\u003eWhen using mediation, publishers should configure CPRA settings in AdMob, potentially store the IAB signal using \u003ccode\u003eUserDefaults\u003c/code\u003e, and consult each ad network partner's documentation for compliance options.\u003c/p\u003e\n"]]],["Publishers can enable restricted data processing (RDP) for ad requests to comply with U.S. privacy laws. This is done by adding parameters to ad requests, either using Google's `rdp` signal (value: `1`) or IAB's `IABUSPrivacy_String` signal. Both signals trigger non-personalized ads and override UI settings. For mediation, add partners to the CPRA list, consider using `UserDefaults` for the IAB signal, and check each partner's documentation for compliance options. Ensure you have necessary account permissions.\n"],null,["| **Important:** Verify that you have **Account Management** permission to complete the configuration for EU Consent and GDPR, US State regulations, and User Messaging Platform. See [Manage user access to your\n| account](//support.google.com/admob/answer/2784628) for details.\n\nTo help you comply with\n\n[U.S. states privacy laws](//support.google.com/admob/answer/9561022),\n\nthe Google Mobile Ads SDK lets you use Google\n[restricted data processing](//business.safety.google/rdp/) (RDP) parameter to\nindicate whether to enable RDP. Google also supports the\n\n[Global Privacy Platform](//support.google.com/admob/answer/14126918)\n\n(GPP) for applicable US states. When the Google Mobile Ads SDK uses either\nsignal, the SDK restricts certain unique identifiers and other data is processed\nin the provision of services to you.\n\nYou must decide how restricted data processing can support your compliance plans\nand when to enable. Determine whether to use the RDP parameter\ndirectly or signaling consent and privacy choices with the\n[GPP Specification](//github.com/InteractiveAdvertisingBureau/Global-Privacy-Platform).\n\nThis guide helps you enable RDP on a per-ad request basis and use the GPP\nsignal.\n\nEnable the RDP signal\n\nTo notify Google that RDP must be enabled using Google's RDP signal, insert\nthe key `rdp` as an extra parameter with a value of `1`. \n\n AdRequest request = new AdRequest();\n request.Extras.Add(\"rdp\", \"1\");\n\n\u003cbr /\u003e\n\n| **Tip:** You can use network tracing or a proxy tool such as [Charles](//www.charlesproxy.com/) to capture your app's HTTPS traffic and inspect the ad requests for a `&rdp=` parameter.\n\nUse the IAB GPP Signal\n\nIf you collect consent decisions with a consent management platform or your own\ncustom messaging, the Google Mobile Ads SDK respects GPP signals written to\nlocal storage. The User Messaging Platform (UMP) SDK supports writing the GPP\nsignal. To gather US state consent, see\n[US IAB Support](/admob/unity/privacy/us-iab-support)."]]