1. Home
  2. Meta Hub
  3. Tracking & Operations
  4. Meta Limited Data Use (LDU) and US State Privacy Laws: What It Does to the Pixel, Conversions API, Audiences and Reporting
Tracking & Operations · 9 min read

Meta Limited Data Use (LDU) and US State Privacy Laws: What It Does to the Pixel, Conversions API, Audiences and Reporting

By the Power Ads teamUpdated 2026-11-20Checked against 7 sources1,646 words

Limited Data Use, or LDU, is the switch Meta gives advertisers for US state privacy laws. Turn it on for an event and Meta changes how it may use that data. Leave it off and the flag has no effect. It sounds simple, but it touches the Pixel, the Conversions API, app events and customer list audiences, and each has its own syntax. This guide covers what LDU is, which states Meta's developer documentation lists today, how to send the flag, what Meta does with flagged events, what it says about performance and measurement, how to test it and the mistakes we see most often. Each rule comes from Meta's developer documentation or terms. This is a technical guide, not legal advice: whether and when you should enable LDU is a question for your own legal counsel.

What Limited Data Use is

Meta's developer documentation describes Limited Data Use as a data processing option that gives you more control over how your data is used in Meta's systems. It is off by default. Meta says you must proactively enable it, event by event or record by record, through data processing options.

When LDU is enabled for people in the states it applies to, Meta says it processes that data as a service provider or processor and limits its use of the data as set out in its State-Specific Terms. Meta's Business Tools Terms say the same from the contract side: with the flag enabled, Meta processes that event data as set out in the State-Specific Terms or as otherwise permitted by law. Those terms also put the responsibility for having a lawful basis, giving people clear notice and getting any required consent on the business that sends the data.

So LDU is not a consent banner and not a cookie setting. It is a label on the data you send, telling Meta to treat that data under a narrower set of permitted uses.

Which US states LDU covers today

Meta's current Pixel and App Events documentation lists the scope by product:

  • Business Tools (Pixel, Conversions API, app events) and Audience Network: people in California, Colorado and Connecticut.
  • Customer list custom audiences: California.
  • Dates: Meta says the expanded features became available on May 1, 2023 and took effect on June 1, 2023 for Colorado and Connecticut (Business Tools and Audience Network) and for California (customer list custom audiences). LDU flags sent for those states or products before June 1, 2023 were not applied.
  • Older app SDKs: Meta says the transition period for older SDK versions ended on July 1, 2023, after which default LDU for California was no longer applied on them, so apps need to update and send data processing options themselves.
Power AdsUnlimited Meta agency ad accounts on our corporate cards, with 24/7 support on Telegram and WhatsApp, for teams spending roughly $100,000+/mo. 4% per top-up, no setup fee. Apply for access →

How to send data processing options

Every surface takes the same three values: the option itself, a country and a state. The only accepted option is LDU. For country, Meta's Conversions API reference accepts 1 for the United States or 0 to ask Meta to geolocate the event. For state, it accepts 1000 for California or 0 to ask Meta to geolocate. Sending an empty option list explicitly marks the event as not LDU.

Meta Pixel: call fbq('dataProcessingOptions', ...) before fbq('init', ...). To explicitly opt an event out, call fbq('dataProcessingOptions', []). To enable LDU and let Meta geolocate, call fbq('dataProcessingOptions', ['LDU'], 0, 0). To enable LDU and set the location yourself, for California, call fbq('dataProcessingOptions', ['LDU'], 1, 1000). If you use the image tag instead of the JavaScript Pixel, the same values go in the dpo, dpoco and dpost URL parameters.

Conversions API: add the fields to each server event. Set data_processing_options to ["LDU"], then set data_processing_options_country and data_processing_options_state, either both to 0 for geolocation or to 1 and 1000 for California. To opt an event out, set data_processing_options to an empty array or leave the field out. Meta's geolocation example includes client_ip_address in user_data, and its reference says the state field is required when you send LDU without an IP address. It also says that if you set a country you must set a state, or Meta applies its geolocation logic to the entire event. For offline uploads, Meta says the same options can be added as columns in the CSV file.

App events and SDKs: the Graph API takes the same data_processing_options, country and state fields. The iOS and Android SDKs expose setDataProcessingOptions, and Unity has FB.Mobile.SetDataProcessingOptions, with the same empty, geolocated and California variants. Meta lists minimum versions of iOS SDK 7.1.1 and Android SDK 7.1.0.

Customer list custom audiences: add DATA_PROCESSING_OPTIONS to the upload schema and send ["LDU"] for each record that should carry the flag. Leave out the country and state keys to let Meta geolocate, or add DATA_PROCESSING_OPTIONS_COUNTRY and DATA_PROCESSING_OPTIONS_STATE to set them yourself. Meta says that to use LDU on customer lists you must upload new audiences or update existing ones with the flag, and that the flag does not carry over automatically to different audiences.

What Meta does with LDU-flagged events

The location fields decide whether the flag bites. Meta's Pixel documentation says that if LDU is enabled but the location isn't set to the US plus a covered state, Meta works out whether the event comes from one of the covered states, and applies LDU if it does. Read the other way, the documentation describes LDU applying only to covered states, so a flag on an event from a person outside California, Colorado or Connecticut doesn't put that event under the LDU rules.

For an event that does qualify, Meta says it acts as a service provider or processor and limits its use of the data under its State-Specific Terms. Meta's developer pages don't list each processing step that changes; the State-Specific Terms are the document that defines the permitted uses, so read them alongside your counsel.

One documented detail worth knowing: the reference lists only 1000, California, as a manual state code. For people in Colorado or Connecticut, the documented route is to send 0 for country and state and let Meta geolocate.

Effects on optimisation, custom audiences and measurement

Meta is brief here, and it is better to quote what it says than to guess. Its Pixel and App Events pages say businesses may notice an impact on campaign performance and effectiveness, and that retargeting and measurement capabilities will be limited when LDU is enabled. Meta doesn't publish a percentage or a list of which reports change.

What that means in practice, as practitioner reading rather than Meta's words: events that qualify for LDU are a weaker input for retargeting audiences built from site or app activity and for the measurement you see in Ads Manager, so expect fewer people in those audiences and fewer attributed results from covered states than unflagged traffic would give. If you only flag part of your traffic, compare results by region before and after the change, not overall totals.

For customer lists, the California rule is narrower: the flag is set per record and per audience, it doesn't carry over to other audiences, and Meta asks you to regularly update and maintain people's LDU statuses. If your reports already disagree with your store or GA4, LDU is one more reason; our guide to Meta vs Shopify and GA4 discrepancies covers the others.

Meta documents LDU as a field on the events and records you send, so it is set in your Pixel, server and audience code rather than in ad account settings. Power Ads supplies Meta agency ad accounts; we don't build tracking, so LDU implementation stays with you or your developer. If server events are already flowing, our event match quality guide covers the matching side.

How to test your LDU setup

Test the browser and server sides separately, then check that they agree.

  • Browser: Meta Ads Data Advisor, the Chrome and Edge extension that replaced Meta Pixel Helper, shows which Pixels loaded and event-level detail. Practitioner tip: also open your browser's network tab, find the request to facebook.com/tr and check that dpo, dpoco and dpost carry the values you meant to send.
  • Server: Meta's Test Events tool in Events Manager (Data Sources, your Pixel, Test Events) gives you a test ID to send as test_event_code. Meta says server events appear in the Test Events window once the request is sent. Log your own outgoing payloads too, so you can confirm the data_processing_options fields are there.
  • Production check: Meta says you should be able to verify events in your Pixel's Overview within 20 minutes, with raw, matched and attributed counts by connection method.
  • Remove test_event_code before going live. Meta says events sent with it are not dropped: they flow into Events Manager and are used for targeting and ads measurement.

Common implementation mistakes

These are practitioner observations from setups we've reviewed, not Meta rules, except where a doc is cited.

  • Calling dataProcessingOptions after init. Meta's Pixel docs say it must come before fbq('init'), so the call order matters.
  • Hard-coding 1 and 1000 for every visitor. That tells Meta every event is from California. If you don't know the person's state, send 0 and 0 and let Meta geolocate.
  • Setting a country with no state. Meta says it then applies its geolocation logic to the whole event, so your country value doesn't do what you intended.
  • Sending LDU from the server without an IP address or a state. Meta's reference makes the state field required in that case.
  • Browser and server out of step. If the Pixel flags an event and the deduplicated server copy doesn't, or the other way round, the two copies carry different instructions. Make the LDU decision once and pass it to both. See our Pixel and CAPI deduplication guide and Conversions API setup guide.
  • Copying the image-tag example blindly. On Meta's Pixel page, the geolocation image-tag example uses vdpo where the other examples use dpo, which looks like a typo. Use dpo.
  • Assuming a customer list flag carries over. Meta says it doesn't, so re-upload or update each audience that needs it.
  • Leaving test_event_code in production code, which Meta says still sends events into targeting and measurement.

Key takeaways

  • LDU is off by default. You turn it on per event or per record with data processing options.
  • Meta's developer docs list California, Colorado and Connecticut for Business Tools and Audience Network, and California for customer list custom audiences.
  • Send LDU with country 0 and state 0 to let Meta geolocate; 1 and 1000 means California. An empty list explicitly means no LDU.
  • On the Pixel, call dataProcessingOptions before init. On CAPI, set a state whenever you set a country, and send a state if there is no IP address.
  • Meta says LDU may affect campaign performance and limits retargeting and measurement, without publishing numbers.
  • This is not legal advice. Whether to enable LDU is a decision for you and your counsel.

FAQ

Does Meta turn on Limited Data Use automatically for California users?

No. Meta's developer documentation says you must proactively enable LDU. Older app SDKs used to apply default LDU for California, but Meta says that ended on July 1, 2023, so apps must send data processing options themselves.

Which states does LDU apply to?

Meta's current Pixel and App Events docs list California, Colorado and Connecticut for Business Tools and Audience Network, and California for customer list custom audiences. One sentence in the App Events SDK section also names Florida, Texas and Oregon, so check Meta's live documentation and State-Specific Terms before relying on a list.

What happens if I flag an event as LDU but the user is not in a covered state?

Meta says that if the location isn't set to the US plus a covered state, it determines whether the event comes from one, and applies LDU only if it does. Meta's docs describe LDU applying only to people in the covered states.

How do I send LDU through the Conversions API?

Add data_processing_options set to ["LDU"] to each server event, plus data_processing_options_country and data_processing_options_state. Use 0 and 0 to let Meta geolocate, with client_ip_address in user_data as in Meta's example, or 1 and 1000 for California. Send an empty array, or omit the field, to opt out.

Will LDU lower my reported conversions?

Meta says retargeting and measurement capabilities are limited when LDU is enabled and that campaign performance may be affected. It doesn't publish how much. Compare results from covered states before and after the change rather than overall totals.

Does the LDU flag on one customer list apply to my other audiences?

No. Meta says the flag doesn't carry over automatically to different audiences. Upload new audiences or update existing ones with the flag, and keep people's LDU statuses up to date.

Need agency ad accounts?Unlimited Meta agency accounts on our corporate cards, shared to your Business Manager through partner access. 4% per top-up, no setup fee, unused balance refunded within 24 hours (business days), free replacements, 24/7 on Telegram and WhatsApp.
@power_ads_hqGet the next one in Telegram.Meta policy shifts, spend-limit fixes and scaling notes from the Power Ads team. Join 3,000+ subscribers. Free, read-only, one tap to leave.Join channel

Sources

Power Ads background
By application only

We don't talk. We solve.

Unlimited Meta agency ad accounts on our corporate cards for teams spending roughly $100,000+ a month. 4% per top-up, no setup fee, 24/7 on Telegram and WhatsApp.

Telegram support · 24/7
TelegramWhatsAppApply