Per aiutarti a rispettare le
leggi statali sulla privacy negli Stati Uniti,
l'SDK Google Mobile Ads ti consente di utilizzare il parametro
trattamento dati limitato (RDP) di Google per
indicare se abilitare il trattamento dati limitato. Google supporta anche la
Global Privacy Platform
(GPP) per gli stati USA applicabili. Quando l'SDK Google Mobile Ads utilizza uno dei due
indicatori, l'SDK limita alcuni identificatori univoci e altri dati vengono trattati
nella fornitura di servizi.
Devi decidere in che modo il trattamento dati limitato può supportare i tuoi piani di conformità
e quando attivarlo. Determina se utilizzare direttamente il parametro RDP o segnalare il consenso e le scelte relative alla privacy con la specifica GPP.
Questa guida ti aiuta ad attivare RDP in base alle richieste di annuncio e a utilizzare l'indicatore GPP.
Attiva l'indicatore RDP
Per comunicare a Google che il trattamento dati limitato deve essere attivato utilizzando l'indicatore RDP di Google, inserisci
la chiave rdp come parametro aggiuntivo con un valore di 1.
Se raccogli le decisioni relative al consenso con una piattaforma di gestione del consenso o con messaggi personalizzati, l'SDK Google Mobile Ads rispetta gli indicatori GPP scritti nell'archivio locale. L'SDK User Messaging Platform (UMP) supporta la scrittura del
segnale GPP. Per raccogliere il consenso degli stati degli Stati Uniti, consulta
Assistenza IAB USA.
[null,null,["Ultimo aggiornamento 2025-09-02 UTC."],[[["\u003cp\u003eGoogle's Mobile Ads SDK enables publishers to comply with U.S. state privacy laws using Google's RDP signal or the IAB-defined \u003ccode\u003eIABUSPrivacy_String\u003c/code\u003e to restrict data processing for non-personalized ads.\u003c/p\u003e\n"],["\u003cp\u003ePublishers can signal restricted data processing at the ad request level by adding the key \u003ccode\u003erdp\u003c/code\u003e with a value of \u003ccode\u003e1\u003c/code\u003e for Google's signal, or the key \u003ccode\u003eIABUSPrivacy_String\u003c/code\u003e with a compliant IAB string value for IAB's signal.\u003c/p\u003e\n"],["\u003cp\u003eWhen using mediation, publishers should add their mediation partners to the CPRA ad partners list in Ad Manager, potentially store the IAB signal using \u003ccode\u003eUserDefaults\u003c/code\u003e for partner access, and consult partner documentation for CPRA compliance options.\u003c/p\u003e\n"]]],["Publishers can use two parameters to enable restricted data processing (RDP) for U.S. state privacy law compliance: Google's `rdp` signal or the IAB's `IABUSPrivacy_String` signal. Both signals trigger non-personalized ads and override UI settings. To use Google's signal, add \"rdp\" with a value of \"1\" as an extra parameter in the ad request. For IAB, insert \"IABUSPrivacy_String\" with a compliant string. For mediation, add partners to the CPRA ad partners list, consider using UserDefaults for the IAB signal, and consult partner documentation. Ensure necessary account permissions are in place.\n"],null,["Select platform: [Android](/ad-manager/mobile-ads-sdk/android/privacy/us-states \"View this page for the Android platform docs.\") [iOS](/ad-manager/mobile-ads-sdk/ios/privacy/us-states \"View this page for the iOS platform docs.\") [Unity](/ad-manager/mobile-ads-sdk/unity/privacy/us-states \"View this page for the Unity platform docs.\") [Flutter](/ad-manager/mobile-ads-sdk/flutter/privacy/us-states \"View this page for the Flutter platform docs.\")\n\n\u003cbr /\u003e\n\n| **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/admanager/answer/9561023),\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/admanager/answer/14117049)\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 AdManagerAdRequest request = new AdManagerAdRequest();\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](/ad-manager/mobile-ads-sdk/unity/privacy/us-iab-support)."]]
