Facebook Conversions API
Facebook Conversions allows advertisers to track and access web events.
The Conversions API is designed to create a direct connection between your marketing data and the systems which help optimise ad targeting, decrease cost per action and measure results across Meta technologies. Facebook keeps a set of documentation pages for a deeper dive.
Features
| Feature name | Supported | |
|---|---|---|
| Bulk upload | True | Only on event insert |
Only event insert is currently supported. To request a wider support for Reverse-ETL, please reach out to our team.
π§ Setup Guide - Reverse ETL
Prerequisites
To connect Facebook Conversions to Weld, you need:
- An active Facebook account with permission to access data from accounts you would like to sync.
- The breakdowns and fields you would like to sync.
Step 1 - Destination
- Click on the Reverse ETL item in the sidebar to navigate to the page.
- If this is your first reverse ETL sync the setup guide will automatically start. Otherwise click "Add Reverse ETL Sync" button to start the setup guide.
- Find the Faceboook Conversions connector from the list of destinations and choose an existing connection, if any, or click to create a new connection which you will need to authorize.
Step 2 - Target Details
The Facebook Conversions connection does not have additional configuration - This will be skipped.
Step 3 - Map Data
Define how your source data should sync with your destination
Source
Choose the SQL model that contains the data that you would like to send to Facebook Conversions
- In the connector setup form, enter the source model of your choice then choose your destination object.
- Choose how you want to sync data from your source model to the destination object.
Sync Mode
Choose how you would like to sync your data:
Insert- Inserts new records only
Important notes
Syncs need to be limited to events looking a maximum of 7 days back, due to the structure of the integration allowed from FaceBook.
event_time can be up to 7 days before you send an event to Facebook. If any event_time in data is greater than 7 days in the past, we return an error for the entire request and process no events.
Therefore, remember to limit event_time to 7 days at maximum.
Choose Identifier
Select the unique identifier field to match your record between your source and destination (this is usually the email or ID).
Field Mapping
Configure the field mapping between your source and destination. Map the column from your source model to the property in Facebook Conversions.
Step 4 - Schedule Sync
Decide how often you want your data to sync. Pick a frequency that matches your needs to keep your destination always up-to-date. You can choose to have the sync running on an independent schedule or as part of an orchestration workflow.
- Independent: The sync will run on its own schedule, independent of other syncs.
- Orchestration: The sync will be part of an orchestration workflow, allowing you to run it in conjunction with other tasks.
Step 5 - Finalise and Run
Click "Start Sync" to save your configuration and start the sync process.