If set to Custom Audience:
•Facebook users are sourced from the RPI data warehouse.
•If the offer’s Mode of operation is set to Create new list, users are added to a new custom audience. If the name of the new custom audience already exists, a new audience is not created.
•If the offer’s Mode of operation is set to Append to existing list, users are added to the existing custom audience.
•If the offer’s Mode of operation is set to Delete from existing list, users are deleted from the existing custom audience.
Note that it may take a number of days for Facebook to complete matching for the uploaded custom audience.
If set to Offline Event:
•On execution of a Facebook Offline Event offer, if Use existing is unchecked at the Facebook Offline Event offer, a new offline event is only created when a matching event does not already exist.
•When Assign to Ad account is checked at the offer, the event is updated to assign tracking and read permissions to the Ad Account specified at channel configuration.
•Users are then added to the specified event.
•Note that a Facebook Offline Event channel’s User ID property is not required if executing a Facebook Offline Event offer using a queue activity.
•If using Limited Data Use mode, the following data processing options parameters are added to the event data uploaded to Facebook:
o "data_processing_options": ["LDU"],
o "data_processing_options_country": 1,
o "data_processing_options_state": [Equivalent US states data processing code]
If not, the following parameter is uploaded:
o "data_processing_options": []
Note that any temporary files generated during execution are written to the folder defined by system configuration setting FileOutputDirectory.
Note also that RPI will only hash data when uploading data to Facebook when the channel's Pre-hashed data option is unchecked.