Announcement: Additional Data Processing Options Columns Required for Meta Attribution Programs (9/5/23)
Meta's Limited Data Use (LDU) feature requires advertisers using the Meta Conversions API for Offline Conversions and the Facebook Offline Conversions API (FBOC) attribution programs to specify when Meta should process data in accordance with its role as a service provider or processor with respect to people in states where Limited Data Use is available (currently California, Colorado, and Connecticut). This means that Meta will restrict the use of this data as specified in their State-Specific Terms.
Historically, LiveRamp has required marketers to include a “data_processing_options” column with one of the following values.
“LDU” (to indicate that LiveRamp should upload data to Meta with the LDU mode enabled)
“non-ldu” (to indicate that LiveRamp should upload data to Meta with LDU mode disabled)
Required Customer Actions
Starting September 30, 2023, all advertisers will need to include two additional columns, “data_processing_options_state” and “data_processing_options_country” in addition to the “data_processing_options” column. The additional columns will allow LiveRamp to pass the appropriate state and country information when an advertiser has marked an event as “LDU.”
Note
If you have provided LiveRamp with written approval to not include the "data_process_options" column, then no action is required.
If an event is marked as “LDU,” then you will need to include one of the following possible values for each column.
Note
Do not enter any other values as it will cause issues with your conversion upload.
For the “data_processing_options_state” column:
Enter “CA” for users located in California
Enter “CO” for users located in Colorado
Enter “CT” for users located in Connecticut
Enter “0” to request that Meta perform geolocation
For the “data_processing_options_country” column:
Enter “US” for United State of America
Enter “0” to request that Meta perform geolocation
If an event is marked as “non-ldu” (lowercase), then you will need to include these columns but no values.
Once you have made the appropriate changes to your conversions file, and before you upload the updated file, create a support case:
For the Product Type, select “Attribution Programs”.
For the Subject, enter “Adding Data Processing Options Columns for Meta”
For the Description, use something similar to the example below:
Hi Support,
We will be adding two new columns (“data_processing_options_state” and “data_processing_options_country) to our conversion file for the [Meta Conversions API for Offline Conversions or FBOC] attribution program. We plan to drop the file “<insert filename>” to the directory “<insert directory name>”.
Below is a list of additional attribution programs that also currently use this file:
<insert program names>
Request:
Please let us know when we can drop the file so that you can configure the new columns for each Measurement Enablement feed.
Once Support has confirmed that they are ready, upload the updated file.