Announcing Required Formatting Changes for Facebook Offline Conversions Integration Customers (7/16/20)
Starting July 30, 2020, any users of LiveRamp’s Facebook Offline Conversions integration will need to add an additional column to their transaction data files to make sure data about California consumers is processed appropriately in the integration. After that date, files that do not include that column will not be able to be delivered to Facebook.
This is due to the fact that Facebook recently released a Limited Data Use (LDU) feature (effective July 1) in accordance with its role as a service provider in California per CCPA requirements. This feature requires advertisers to specify when Facebook should process data in accordance with its role as a service provider in California (in the form of an LDU flag) per CCPA requirements.
Note
Facebook will not use the LDU-enabled transaction events for attribution reporting. For more information on this change, see Facebook’s LDU documentation.
Starting July 30th, 2020, all advertisers using this integration must include a “data_processing_options” column at the end of their transaction data files. This column will be the basis for LiveRamp to pass the appropriate LDU flags to the Facebook Conversions API.
Use one of the two allowed values for each row in this column:
Enter the value “LDU” (to indicate that LiveRamp should upload data to Facebook with the LDU mode enabled)
Enter the value “non-ldu” (to indicate that LiveRamp should upload data to Facebook with the LDU mode disabled)
Enter a value of “LDU” (uppercase) if a transaction is tied to where a person in California has opted out of the sale of data or that the business has opted to have Facebook process data as a service provider, as defined by the CCPA. This informs LiveRamp that we are to provide an LDU flag when uploading the event to the Facebook Offline Conversions API. This flag enables LDU, and indicates to Facebook that it should limit its use of personal information for that given event and process the data as a service provider.
Enter a value of “non-ldu” (lowercase) for transactions where you would like LiveRamp to upload the event to the Facebook Offline Conversions API, explicitly indicating that Facebook should not enable LDU.
Caution
This column is not to identify a user as a California user. Instead this column informs LiveRamp how to treat the data under CCPA.
Note
If including this column is not technically feasible or desirable, we are able to send transaction data to Facebook where we will disable LDU mode for all transactions with your express instruction to do so. Please contact us promptly if you’d prefer this option and we can provide a short document for your signature that provides LiveRamp with such express written instruction.
Caution
As your Service Provider, LiveRamp cannot provide any legal advice when it comes to your use of the Data Processing State column.
In the example below, the ACME Company is uploading transaction data informing LiveRamp to pass the transaction event tied to Mary Smith and the transaction event tied to Myra Joe with the LDU feature enabled. This indicates to Facebook that they should limit their use of California personal information for the two given events. The ACME Company is also uploading transaction data informing LiveRamp to pass the transaction event tied to John Doe but explicitly not enable LDU for that consumer.
first_name | last_name | .... | data_processing_options |
|---|---|---|---|
Mary | Smith | LDU | |
John | Doe | non-ldu | |
Myra | Joe | LDU |
All entries for the “data_processing_options” column should be either “LDU” or "non-ldu" (as shown in the example above). Make sure to add the new “data_processing_options” column as the last column in your transaction data file so as not to impact other attribution workflows using the same transaction data file.