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.
The following Meta products offer Limited Data Use. Availability varies by state. See the table below for details:
California | Colorado | Connecticut | Florida | Texas | Oregon | |
---|---|---|---|---|---|---|
| ✓ | ✓ Effective June 1, 2023 | ✓ Effective June 1, 2023 | ✓ Effective June 24, 2024 | ✓ Effective June 24, 2024 | ✓ Effective June 24, 2024 |
✓ | ✓ Effective June 1, 2023 | ✓ Effective June 1, 2023 | ✓ Effective June 24, 2024 | ✓ Effective June 24, 2024 | ✓ Effective June 24, 2024 | |
✓ 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, 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, 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:
Field | Description |
---|---|
Data Processing Options array | Processing options you would like to enable for a specific event or record. Current accepted value is The name of this field can be presented differently, depending on the API and implementation you are using. For example, this is 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 |
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 Note:
|
التنفيذ | إضافة خيارات معالجة البيانات |
---|---|
بيكسل المتصفح | قم بتحديث الرمز لتهيئة البيكسل من أجل تحديد الأسلوب لتعطيل وضع الاستخدام المحدود للبيانات (LDU) بوضوح: fbq('dataProcessingOptions', []); fbq('init', '{pixel_id}'); fbq('track', 'PageView'); لتمكين الاستخدام المحدود للبيانات (LDU) وجعل Meta تحدد الموقع الجغرافي: fbq('dataProcessingOptions', ['LDU'], 0, 0); لتمكين الاستخدام المحدود للبيانات (LDU) وتحديد الموقع، على سبيل المثال لكاليفورنيا: fbq('dataProcessingOptions', ['LDU'], 1, 1000); |
إشارة الصورة | أضف التالي إلى إشارة صورة البيكسل:
لمعرفة القيم المقبولة، راجع المرجع. لتعطيل الاستخدام المحدود للبيانات (LDU) بوضوح، أدخل أية قيمة فارغة في المعلمة <img src="https://www.facebook.com/tr?id={pixel_id}&ev=Purchase&dpo=" /> لتمكين الاستخدام المحدود للبيانات (LDU) وجعل Meta تحدد الموقع الجغرافي: <img src="https://www.facebook.com/tr?id={pixel_id}&ev=Purchase&vdpo=LDU&dpoco=0&dpost=0" /> لتمكين الاستخدام المحدود للبيانات (LDU) وتحديد الموقع يدويًا، على سبيل المثال لكاليفورنيا: <img src="https://www.facebook.com/tr?id={pixel_id}&ev=Purchase&dpo=LDU&dpoco=1&dpost=1000" /> |
بالنسبة لواجهتي API هاتين، يمكن تنفيذ خيارات معالجة البيانات من خلال إضافة data_processing_options
وdata_processing_options_country
وdata_processing_options_state
داخل كل حدث ضمن معلمة البيانات للأحداث.
ملاحظة: لم يعد يوصى بواجهتي API أحداث التطبيقات والتحويل بلا اتصال لعمليات الدمج الجديدة. بدلاً من ذلك، يوصى باستخدام واجهة API التحويلات حيث إنها تدعم الآن أحداث الويب والتطبيق وبلا اتصال. راجع واجهة API التحويلات لأحداث التطبيق وواجهة API التحويلات للأحداث بلا اتصال لمزيد من المعلومات.
لعدم تمكين الاستخدام المحدود للبيانات (LDU) بشكل صريح، حدد مصفوفة فارغة لكل حدث أو ببساطة قم بإزالة الحقل في حمولة البيانات:
{ "data": [ { "event_name": "Purchase", "event_time": <EVENT_TIME>, "user_data": { "em": "<EMAIL>" }, "custom_data": { "currency": "<CURRENCY>", "value": "<VALUE>" }, "data_processing_options": [] } ] }
لتمكين الاستخدام المحدود للبيانات (LDU) وجعل Meta تحدد الموقع الجغرافي:
{ "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 } ] }
لتمكين الاستخدام المحدود للبيانات (LDU) وتحديد الموقع يدويًا، على سبيل المثال لكاليفورنيا:
{ "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 } ] }
تقدم واجهة API التحويلات بلا اتصال خيار تحميل الأحداث يدويًا من ملف بتنسيق .csv
. في هذه الحالة، أضف خيارات معالجة البيانات وبلد معالجة البيانات وولاية معالجة البيانات كأعمدة داخل الملف لديك. كما يمكن العثور على المزيد من المعلومات حول هذا الأمر في دليل تحميل واجهة مستخدم.
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 }
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:
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.
Implementation | Adding Data Processing Options |
---|---|
Facebook SDK for iOS v7.1.1+ (Objective-C) | With Objective-C, use 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 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 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); |
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.
Implementation | Adding Data Processing Options |
---|---|
Facebook SDK for iOS, v5.10+ | Use To explicitly not enable Limited Data Use (LDU), use: [FBAdSettings setDataProcessingOptions:@[]]; To enable LDU and have Meta perform geolocation, use:
[FBAdSettings setDataProcessingOptions:@[@"LDU"] country:0 state:0]; To enable LDU and manually specify the location, use:
[FBAdSettings setDataProcessingOptions:@[@"LDU"] country:1 state:1000]; |
Facebook SDK for Android, v5.10+ | Use the To explicitly not enable Limited Data Use (LDU), use: AdSettings.setDataProcessingOptions(new String[] {}) To enable LDU and have Meta perform geolocation, use:
AdSettings.setDataProcessingOptions(new String[] {"LDU"}, 0, 0); To enable LDU and manually specify the location, use:
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 To explicitly not enable LDU, use: AdSettings.SetDataProcessingOptions(new string[]{}) To enable LDU and have Meta perform geolocation, use:
AdSettings.SetDataProcessingOptions(new string[] {"LDU"}, 0, 0); To enable LDU and manually specify the location, use:
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.
Implementation | Adding 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:
AdSettings.setDataProcessingOptions(new String[] {"LDU"}, 0, 0); To enable LDU and manually specify the location, use:
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:
[FBAdSettings setDataProcessingOptions:@[@"LDU"] country:0 state:0]; To enable LDU and manually specify the location, use:
[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.
Implementation | Adding 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:
AdSettings.setDataProcessingOptions(new String[] {"LDU"}, 0, 0); To enable LDU and manually specify the location, use:
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:
[FBAdSettings setDataProcessingOptions:@[@"LDU"] country:0 state:0]; To enable LDU and manually specify the location, use:
[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:
AdSettings.setDataProcessingOptions(new String[] {"LDU"}, 0, 0); To enable LDU and manually specify the location, use:
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:
[FBAdSettings setDataProcessingOptions:@[@"LDU"] country:0 state:0]; To enable LDU and manually specify the location, use:
[FBAdSettings setDataProcessingOptions:@[@"LDU"] country:1 state:1000]; After setting the LDU for the event, generate the bidder token: NSString *token = [FBAdSettings bidderToken]; |
إذا كنت تريد تمكين الاستخدام المحدود للبيانات للأشخاص المقيمين في كاليفورنيا من خلال الجماهير المخصصة بقائمة العملاء في تاريخ 1 يونيو 2023 أو بعده، فيجب عليك تحميل جماهير جديدة أو تحديث جماهيرك الحالية مع تضمين إشارة الاستخدام المحدود للبيانات. قم بتحديث جماهيرك وحالات الاستخدام المحدود للبيانات الخاصة بالأشخاص والحفاظ عليها بشكل منتظم عند الحاجة.
يُرجى ملاحظة أنه لن يتم نقل إشارة الاستخدام المحدود للبيانات المطبقة على مستخدم في جمهور واحد إلى جماهير مختلفة. بالطريقة ذاتها التي يجب على المعلنين إدارة كل جماهير مخصصة بقائمة العملاء الموجودة بشكل منفصل من خلال المعايير التي يختارونها، يجب تطبيق إشارة الاستخدام المحدود للبيانات بشكل منفصل على كل جمهور يستفيدون منه للإعلانات.
لعدم تمكين LDU
بشكل صريح للسجل، يمكنك إما إرسال مصفوفة data_processing_options
فارغة أو إزالة الحقل في حمولة البيانات. مثال على مصفوفة فارغة:
{ "payload": { "schema": [ "EMAIL", "DATA_PROCESSING_OPTIONS" ], "data": [ [ "<HASHED_DATA> ", [] ] ] } }
لتمكين LDU
بشكل صريح، وجعل Meta تعمل على تحديد الموقع الجغرافي (من خلال عدم تضمين الولاية والبلد لسجل معين)، حدد مصفوفة تحتوي على LDU
لكل سجل:
{ "payload": { "schema": [ "EMAIL", "DATA_PROCESSING_OPTIONS" ], "data": [ [ "<HASHED_DATA> ", ["LDU"] ] ] } }
لتمكين LDU وتحديد الموقع يدويًا:
{ "customer_consent": true, "payload": { "schema": [ "EMAIL", "DATA_PROCESSING_OPTIONS", "DATA_PROCESSING_OPTIONS_COUNTRY", "DATA_PROCESSING_OPTIONS_STATE" ], "data": [ [ "<HASHED_DATA>", ["LDU"], 1, 1000 ] ] } }