Ce document a été mis à jour.
La traduction en Français (France) n’est pas encore terminée.
Anglais mis à jour : 1 mai
Français (France) mis à jour : 13 juin 2023

Data Processing Options for US Users

Limited Data Use is a data processing option that gives you more control over how your data is used in Meta’s systems and better supports your compliance efforts with various US state privacy regulations. To utilize this feature, you must proactively enable Limited Data Use. When Meta receives data with Limited Data Use enabled from people in the states where Limited Data Use applies, we will process that data in accordance with our role as a service provider or processor, as applicable, and limit the use of that data as specified in our State-Specific Terms.

Meta products that offer the Limited Data Use

The following Meta products offer Limited Data Use. Availability varies by state. See the table below for details:

CaliforniaColoradoConnecticutFloridaTexasOregon

Meta Business Tools

  • Meta Pixel
  • App Events via Facebook SDK
  • App Events API
  • Conversions API
  • Offline Conversions API

Effective June 1, 2023


Effective June 1, 2023


Effective June 24, 2024


Effective June 24, 2024


Effective June 24, 2024

Audience Network SDK


Effective June 1, 2023


Effective June 1, 2023


Effective June 24, 2024


Effective June 24, 2024


Effective June 24, 2024

Customer List Custom Audiences


Effective June 1, 2023

Limited Data Use is sent through a parameter called Data Processing Options, and it can optionally be sent alongside a user’s country and state. If an advertiser is not sure of the country or state, they can opt for Meta to determine if the event or record is from an applicable state.

For Business Tools and Audience Network SDK

For Business Tools and Audience Network, Limited Data Use is available only for people in California, Colorado, Connecticut, Florida, Texas, or Oregon. If a business enables Limited Data Use but does not set the location parameters to US and California, Colorado, Connecticut, Florida, Texas, or Oregon we will determine if the event is from one of those states. If Limited Data Use is enabled for an event in California, Colorado, Connecticut, Florida, Texas, or Oregon we will process data in accordance with our role as a service provider or processor and limit the use of that data in accordance with our State-Specific Terms.

Businesses may notice an impact to campaign performance and effectiveness, and retargeting and measurement capabilities will be limited when Limited Data Use is enabled.

For Customer List Custom Audiences

For Customer List Custom Audiences, Limited Data Use is available only for people in California. If Limited Data Use is enabled for a record in a customer list from California, we will process data in accordance with our role as a service provider and limit the use of that data in accordance with our State-Specific Terms. If a business enables Limited Data Use but does not set the location parameters to US and California, we will determine if the record is from California.

Businesses may notice an impact to audience size when Limited Data Use is enabled.

Supported APIs are listed below.

Learn more about Data Processing Options:

Reference

FieldDescription

Data Processing Options

array

Processing options you would like to enable for a specific event or record. Current accepted value is LDU for Limited Data Use.


The name of this field can be presented differently, depending on the API and implementation you are using. For example, this is dataProcessingOptions for a Meta Pixel JavaScript call, but data_processing_options for a Conversions API call. Please see the example calls below.


An empty array can be sent to explicitly specify that this event or record shouldn't be processed with the Limited Data Use restrictions.

Data Processing Options Country

integer

Optional for most APIs. See note below for details.


A country that you want to associate with this data processing option. Current accepted values are 1 for the United States of America, or 0 to request that Meta perform geolocation.

Data Processing Options State

integer

Optional for most APIs. See note below for details.


A state that you want to associate to this data processing option. Current accepted values are 1000 for California, 1001 for Colorado, 1002 for Connecticut, 1003 for Florida, 1004 for Oregon, 1005 for Texas, or 0 to request that we perform geolocation.


Note:

  • If you set a country, you must also set a state. Otherwise, we will perform geolocation.

Supported Tools and APIs

Meta Pixel

ImplémentationAjout des options de traitement des données

Pixel de navigateur

Mettez à jour le code d’initialisation du pixel de manière à spécifier la méthode dataProcessingOptions avant d’appeler fbq('init').


Pour ne pas activer le mode LDU (Limited Data Use, Utilisation limitée des données) de manière explicite :

fbq('dataProcessingOptions', []);
fbq('init', '{pixel_id}');
fbq('track', 'PageView');

Pour activer le mode LDU et demander à Meta d’effectuer une géolocalisation :

fbq('dataProcessingOptions', ['LDU'], 0, 0);

Pour activer le mode LDU et indiquer le lieu, par exemple la Californie :

fbq('dataProcessingOptions', ['LDU'], 1, 1000);

Tag d’image

Ajoutez ce qui suit au tag d’image Pixel :

  • dpo : options de traitement des données
  • dpoco : pays associé aux options de traitement des données
  • dpost : état associé aux options de traitement des données

Consultez les références pour connaître les valeurs acceptées.


Pour ne pas activer explicitement le mode LDU, transmettez une valeur vide pour le paramètre dpo :

<img src="https://www.facebook.com/tr?id={pixel_id}&ev=Purchase&dpo=" />

Pour activer le mode LDU et demander à Meta d’effectuer une géolocalisation :

<img src="https://www.facebook.com/tr?id={pixel_id}&ev=Purchase&vdpo=LDU&dpoco=0&dpost=0" />

Pour activer le mode LDU et indiquer le lieu manuellement, par exemple la Californie :

<img src="https://www.facebook.com/tr?id={pixel_id}&ev=Purchase&dpo=LDU&dpoco=1&dpost=1000" />

Conversions API and Offline Conversions API

Pour ces deux API, implémentez les options de traitement des données en ajoutant data_processing_options, data_processing_options_country et data_processing_options_state dans le paramètre data de vos évènements.

Remarque : nous ne recommandons plus les API App Events et Offline Conversions pour les nouvelles intégrations. Nous vous recommandons au contraire d’utiliser l’API Conversions dans la mesure où elle prend maintenant en charge les évènements Web, d’application et hors ligne. Pour plus d’informations, consultez l’API Conversions pour les évènements d’application et l’API Conversions pour les évènements hors ligne.

Pour ne pas activer l’utilisation limitée des données (LDU) de manière explicite, indiquez un tableau vide pour chaque évènement ou supprimez simplement le champ de la charge utile :

{
    "data": [
        {
            "event_name": "Purchase",
            "event_time": <EVENT_TIME>,
            "user_data": {
                "em": "<EMAIL>"
            },
            "custom_data": {
                "currency": "<CURRENCY>",
                "value": "<VALUE>"
            },
            "data_processing_options": []
        }
    ]
}

Pour activer le mode LDU et demander à Meta d’effectuer une géolocalisation :

{
    "data": [
        {
            "event_name": "Purchase",
            "event_time": <EVENT_TIME>,
            "user_data": {
                "em": "<EMAIL>",
                "client_ip_address": "256.256.256.256"
            },
            "custom_data": {
                "currency": "<CURRENCY>",
                "value": "<VALUE>"
            },
            "data_processing_options": ["LDU"],
            "data_processing_options_country": 0,
            "data_processing_options_state": 0
        }
    ]
}

Pour activer le mode LDU et indiquer le lieu manuellement, par exemple la Californie :

{
    "data": [
        {
            "event_name": "Purchase",
            "event_time": <EVENT_TIME>,
            "user_data": {
                "em": "<EMAIL>"
            },
            "custom_data": {
                "currency": "<CURRENCY>",
                "value": "<VALUE>"
            },
            "data_processing_options": ["LDU"],
            "data_processing_options_country": 1,
            "data_processing_options_state": 1000
        }
    ]
}

Interface d’importation manuelle

L'API Offline Conversions vous donne la possibilité d'importer manuellement vos évènements depuis un fichier .csv. Dans ce cas, ajoutez les colonnes Data Processing Options (Options de traitement des données), Data Processing Country (Pays associé au traitement des données) et Data Processing State (État associé au traitement des données) dans votre fichier. Vous trouverez plus d’informations à ce sujet dans l’interface d’utilisation d’importation.

App Events API

Graph API

To implement Data Processing Options using the Graph API, add data_processing_options, data_processing_options_country, and data_processing_options_state to your API call.

To explicitly not enable LDU, send an empty data_processing_options array:

{
  "event": "CUSTOM_APP_EVENTS",
  "application_tracking_enabled": "1",
  "advertiser_tracking_enabled": "1",
  "custom_events": ["fb_mobile_purchase"],
  "data_processing_options": []
}  

To enable LDU and have Meta perform geolocation, you can send an event with the following code:

{
  "event": "CUSTOM_APP_EVENTS",
  "application_tracking_enabled": "1",
  "advertiser_tracking_enabled": "1",
  "custom_events": ["fb_mobile_purchase"],
  "data_processing_options": ["LDU"],
  "data_processing_options_country": 0,
  "data_processing_options_state": 0
}  

To enable LDU and manually specify the location, e.g., for California, you can send an event with the following code:

  {
  "event": "CUSTOM_APP_EVENTS",
  "application_tracking_enabled": "1",
  "advertiser_tracking_enabled": "1",
  "custom_events": ["fb_mobile_purchase"],
  "data_processing_options": ["LDU"],
  "data_processing_options_country": 1,
  "data_processing_options_state": 1000
}  

Mobile SDKs

We recommend using our latest versions to ensure the functionality of Data Processing Options. The below implementation instructions are accurate for the following SDK versions:

  • iOS Facebook SDK v7.1.1 or higher
  • Android Facebook SDK v7.1.0 or higher
  • Unity SDK v7.21.0 or higher

Please update if you are using any versions below the ones listed above.

As of July 1, 2023, we are ending the Transition Period for older versions of App Events via the Facebook SDK, whereby we applied Limited Data Use to all personal information shared about people in California. The ability to enable default Limited Data Use will no longer be available for any versions below iOS Facebook SDK v7.1.1, Android Facebook SDK v7.1.0 and Unity SDK v7.21.0. If you choose to use Limited Data Use for a person in California, Colorado, Connecticut, Florida, Texas, or Oregon on or after July 1, 2023, you must update your SDK and implement Data Processing Options as set forth in this document.

ImplementationAdding Data Processing Options

Facebook SDK for iOS v7.1.1+ (Objective-C)

With Objective-C, use FBSDKSettings setDataProcessingOptions.


To explicitly not enable Limited Data Use (LDU), use:

[FBSDKSettings setDataProcessingOptions:@[]];

To enable LDU and have Meta perform geolocation, use:

[FBSDKSettings setDataProcessingOptions:@[@"LDU"] country:0 state:0]; 

To enable LDU and manually specify the location, e.g., for California, use:

[FBSDKSettings setDataProcessingOptions:@[@"LDU"] country:1 state:1000];   

Facebook SDK for iOS v7.1.1+ (Swift)

With Swift, use setDataProcessingOptions.


To explicitly not enable LDU, use:

Settings.setDataProcessingOptions(modes: [])   

To enable LDU and have Meta perform geolocation, use:

Settings.setDataProcessingOptions(modes: ["LDU"], country: 0, state: 0)

To enable LDU and manually specify the location, e.g., for California, use:

Settings.setDataProcessingOptions(modes: ["LDU"], country: 1, state: 1000)  

Facebook SDK for Android v7.1.0+

Use the setDataProcessingOptions method.


To explicitly not enable LDU, use:

FacebookSdk.setDataProcessingOptions(new String[] {});   

To enable LDU and have Meta perform geolocation, use:

FacebookSdk.setDataProcessingOptions(new String[] {"LDU"}, 0, 0);   

To enable LDU and manually specify the location, e.g., for California, use:

FacebookSdk.setDataProcessingOptions(new String[] {"LDU"}, 1, 1000);  

Unity SDK v7.21.1+

To explicitly not enable LDU, send an event with:

FB.Mobile.SetDataProcessingOptions(new string[] {});

To enable LDU and have Meta perform geolocation, send an event with:

FB.Mobile.SetDataProcessingOptions(new string[] {"LDU"}, 0, 0); 

To enable LDU and manually specify the location, e.g., for California, send an event with:

FB.Mobile.SetDataProcessingOptions(new string[] {"LDU"}, 1, 1000);  

Audience Network SDK

We recommend using our latest Audience Network SDK versions to ensure the functionality of Data Processing Options. The below implementation instructions are accurate for Audience Network SDK versions 5.10 and above.

As of July 1, 2023, we are ending the Transition Period for older versions of Audience Network SDK, whereby we limited the data for all personal information that businesses share about people in California and the ability to enable default Limited Data Use will not be available for Audience Network SDK versions below 5.10. If you choose to use Limited Data Use to indicate a person in California, Colorado, Connecticut, Florida, Texas, or Oregon or on or after July 1, 2023, you must update your SDK and implement Data Processing Options as set forth in this document.

ImplementationAdding Data Processing Options

Facebook SDK for iOS, v5.10+

Use FBAdSettings setDataProcessingOptions.


To explicitly not enable Limited Data Use (LDU), use:

[FBAdSettings setDataProcessingOptions:@[]];

To enable LDU and have Meta perform geolocation, use:

  • Country: 0 to request that we determine the location
  • State: 0 to request that we determine the location
[FBAdSettings setDataProcessingOptions:@[@"LDU"] country:0 state:0];

To enable LDU and manually specify the location, use:

  • Country: 1 to indicate USA
  • State: 1000 to indicate California, 1001 for Colorado, 1002 for Connecticut, 1003 for Florida, 1004 for Oregon, 1005 for Texas
[FBAdSettings setDataProcessingOptions:@[@"LDU"] country:1 state:1000];

Facebook SDK for Android, v5.10+

Use the setDataProcessingOptions method.


To explicitly not enable Limited Data Use (LDU), use:

AdSettings.setDataProcessingOptions(new String[] {}) 

To enable LDU and have Meta perform geolocation, use:

  • Country: 0 to request that we determine the location
  • State: 0 to request that we determine the location
AdSettings.setDataProcessingOptions(new String[] {"LDU"}, 0, 0);

To enable LDU and manually specify the location, use:

  • Country: 1 to indicate USA
  • State: 1000 to indicate California, 1001 for Colorado, 1002 for Connecticut, 1003 for Florida, 1004 for Oregon, 1005 for Texas
AdSettings.setDataProcessingOptions(new String[] {"LDU"}, 1, 1000);

Unity SDK, v5.10+ (not using the Audience Network-supplied Unity wrapper)

If you are not using the Audience Network-supplied Unity wrapper, enter the following code.


using UnityEngine;
using System.Runtime.InteropServices;

namespace AudienceNetwork
{
public static class AdSettings
{

public static void SetDataProcessingOptions(string[] dataProcessingOptions)
{
#if UNITY_ANDROID
AndroidJavaClass adSettings = new AndroidJavaClass("com.facebook.ads.AdSettings");
adSettings.CallStatic("setDataProcessingOptions", (object)dataProcessingOptions);
#endif

#if UNITY_IOS
FBAdSettingsBridgeSetDataProcessingOptions(dataProcessingOptions, dataProcessingOptions.Length);
#endif
}

public static void SetDataProcessingOptions(string[] dataProcessingOptions, int country, int state)
{
#if UNITY_ANDROID
AndroidJavaClass adSettings = new AndroidJavaClass("com.facebook.ads.AdSettings");
adSettings.CallStatic("setDataProcessingOptions", (object)dataProcessingOptions, country, state);
#endif

#if UNITY_IOS
FBAdSettingsBridgeSetDetailedDataProcessingOptions(dataProcessingOptions, dataProcessingOptions.Length, country, state);
#endif
}

#if UNITY_IOS
[DllImport("__Internal")]
private static extern void FBAdSettingsBridgeSetDataProcessingOptions(string[] dataProcessingOptions, int length);

[DllImport("__Internal")]
private static extern void FBAdSettingsBridgeSetDetailedDataProcessingOptions(string[] dataProcessingOptions, int length, int country, int state);
#endif
}
}

After entering this code, you can follow the Unity SDK instructions in the row below as if you are using the Unity wrapper.

Unity SDK, v5.10+ (using the Audience Network-supplied Unity wrapper)

If you are using the Audience Network-supplied Unity wrapper, use the following SetDataProcessingOptions.


To explicitly not enable LDU, use:

AdSettings.SetDataProcessingOptions(new string[]{})

To enable LDU and have Meta perform geolocation, use:

  • Country: 0 to request that we determine the location
  • State: 0 to request that we determine the location
AdSettings.SetDataProcessingOptions(new string[] {"LDU"}, 0, 0);

To enable LDU and manually specify the location, use:

  • Country: 1 to indicate USA
  • State: 1000 to indicate California, 1001 for Colorado, 1002 for Connecticut, 1003 for Florida, 1004 for Oregon, 1005 for Texas
AdSettings.SetDataProcessingOptions(new string[] {"LDU"}, 1, 1000);

Publishers using a Mediation Partner must set the Data Processing Options (Limited Data Use) on the Meta Audience Network SDK before initializing the Mediation SDK so that it is received by us in the bidding request.

ImplementationAdding Data Processing Options

Android

To explicitly not enable LDU for the event, use:

AdSettings.setDataProcessingOptions(new String[] {}) 

To enable LDU and have Meta perform geolocation, use:

  • Country: 0 to request that we determine the location
  • State: 0 to request that we determine the location
AdSettings.setDataProcessingOptions(new String[] {"LDU"}, 0, 0);

To enable LDU and manually specify the location, use:

  • Country: 1 to indicate USA
  • State: 1000 to indicate California, 1001 for Colorado, 1002 for Connecticut, 1003 for Florida, 1004 for Oregon, 1005 for Texas
AdSettings.setDataProcessingOptions(new String[] {"LDU"}, 1, 1000);

After setting LDU, initialize the Mediation Partner SDK as per usual.

iOS

To explicitly not enable Limited Data Use (LDU), use:

FBAdSettings setDataProcessingOptions:@[]];

To enable LDU and have Meta perform geolocation, use:

  • Country: 0 to request that we determine the location
  • State: 0 to request that we determine the location
[FBAdSettings setDataProcessingOptions:@[@"LDU"] country:0 state:0];

To enable LDU and manually specify the location, use:

  • Country: 1 to indicate USA
  • State: 1000 to indicate California, 1001 for Colorado, 1002 for Connecticut, 1003 for Florida, 1004 for Oregon, 1005 for Texas
[FBAdSettings setDataProcessingOptions:@[@"LDU"] country:1 state:1000];

After setting the LDU for the event, initialize the Mediation Partner SDK as per usual.

For publishers that are working with us through Bidding Kit and other Server-side Bidding, please follow the implementation methods below.

ImplementationAdding Data Processing Options

Android/Bidding Kit 2.0

To explicitly not enable LDU, use:

AdSettings.setDataProcessingOptions(new String[] {})

To enable LDU and have Meta perform geolocation, use:

  • Country: 0 to request that we determine the location
  • State: 0 to request that we determine the location
AdSettings.setDataProcessingOptions(new String[] {"LDU"}, 0, 0);

To enable LDU and manually specify the location, use:

  • Country: 1 to indicate USA
  • State: 1000 to indicate California, 1001 for Colorado, 1002 for Connecticut, 1003 for Florida, 1004 for Oregon, 1005 for Texas
AdSettings.setDataProcessingOptions(new String[] {"LDU"}, 1, 1000);

After setting the LDU for the event, generate the bidder token:

String token = BidderTokenProvider.getBidderToken(Context);

iOS/Bidding Kit 2.0

To explicitly not enable Limited Data Use (LDU), use:

[FBAdSettings setDataProcessingOptions:@[]];

To enable LDU and have Meta perform geolocation, use:

  • Country: 0 to request that we determine the location
  • State: 0 to request that we determine the location
[FBAdSettings setDataProcessingOptions:@[@"LDU"] country:0 state:0];

To enable LDU and manually specify the location, use:

  • Country: 1 to indicate USA
  • State: 1000 to indicate California, 1001 for Colorado, 1002 for Connecticut, 1003 for Florida, 1004 for Oregon, 1005 for Texas
[FBAdSettings setDataProcessingOptions:@[@"LDU"] country:1 state:1000];

After setting the LDU for the event, generate the bidder token:

NSString *token = [FBAdSettings bidderToken];

Other Server-Side Bidding

For each platform follow the instructions below to specify LDU for the event and retrieve the bidder token before making the server-side bid request.


For Android client:

To explicitly not enable LDU, use:

AdSettings.setDataProcessingOptions(new String[] {}) 

To enable LDU and have Meta perform geolocation, use:

  • Country: 0 to request that we determine the location
  • State: 0 to request that we determine the location
AdSettings.setDataProcessingOptions(new String[] {"LDU"}, 0, 0);

To enable LDU and manually specify the location, use:

  • Country: 1 to indicate USA
  • State: 1000 to indicate California, 1001 for Colorado, 1002 for Connecticut, 1003 for Florida, 1004 for Oregon, 1005 for Texas
AdSettings.setDataProcessingOptions(new String[] {"LDU"}, 1, 1000);

After setting the LDU for the event, generate the bidder token:

String token = BidderTokenProvider.getBidderToken(Context);

For iOS client:

To explicitly not enable Limited Data Use (LDU), use:

[FBAdSettings setDataProcessingOptions:@[]];

To enable LDU and have Meta perform geolocation, use:

  • Country: 0 to request that we determine the location
  • State: 0 to request that we determine the location
[FBAdSettings setDataProcessingOptions:@[@"LDU"] country:0 state:0];

To enable LDU and manually specify the location, use:

  • Country: 1 to indicate USA
  • State: 1000 to indicate California, 1001 for Colorado, 1002 for Connecticut, 1003 for Florida, 1004 for Oregon, 1005 for Texas
[FBAdSettings setDataProcessingOptions:@[@"LDU"] country:1 state:1000];

After setting the LDU for the event, generate the bidder token:

NSString *token = [FBAdSettings bidderToken];

Customer List Custom Audiences

Si vous voulez activer l’utilisation limitée des données pour les personnes résidant en Californie via des audiences personnalisées créées à partir d’un fichier clientèle et ce, à partir du 1er juin 2023, vous devez importer de nouvelles audiences ou mettre à jour vos audiences existantes en y intégrant le marqueur d’utilisation limitée des données. Si nécessaire, mettez régulièrement à jour vos audiences et les statuts des personnes concernées par l’utilisation limitée des données et assurez-en la maintenance.

Veuillez noter qu’un marqueur d’utilisation limitée des données appliqué à un·e utilisateur·ice dans une audience ne sera pas automatiquement transféré à d’autres audiences. De la même manière que les annonceurs doivent gérer séparément chacune de leurs audiences personnalisées créées à partir d’un fichier clientèle selon les critères sélectionnés, le marqueur d’utilisation limitée des données doit s’appliquer séparément à chaque audience utilisée à des fins publicitaires.

Pour NE PAS activer le mode LDU de manière explicite pour l’enregistrement, vous pouvez soit envoyer un tableau vide data_processing_options, soit supprimer le champ de la charge utile. Exemple de tableau vide :

{
   "payload": {
       "schema": [
           "EMAIL",
                    "DATA_PROCESSING_OPTIONS"
       ],
       "data": [
           [
               "<HASHED_DATA>
",
                           []
           ]
       ]
   }
}

Pour activer le mode LDU de manière explicite et demander à Meta d’effectuer la géolocalisation (en n’insérant pas l’État ni le pays dans l’enregistrement donné), utilisez un tableau contenant le mode LDU pour chaque enregistrement :

{
   "payload": {
       "schema": [
           "EMAIL",
                    "DATA_PROCESSING_OPTIONS"
       ],
       "data": [
           [
               "<HASHED_DATA>
",
                           ["LDU"]
           ]
       ]
   }
}

Pour activer le mode LDU et spécifier le lieu manuellement :

{
    "customer_consent": true,
    "payload": {
        "schema": [
            "EMAIL",
            "DATA_PROCESSING_OPTIONS",
            "DATA_PROCESSING_OPTIONS_COUNTRY",
            "DATA_PROCESSING_OPTIONS_STATE"
        ],
        "data": [
            [
                "<HASHED_DATA>",
                ["LDU"],
                1,
                1000
            ]
        ]
    }
}