Connect Reverse ETL Source to Facebook Custom Audience

This guide takes you through the steps to connect a Reverse ETL source to the Facebook Custom Audience destination. You can create a new custom audience or use an existing audience to sync the data.

The below steps assume that you have already set up a Reverse ETL source and configured the connection settings for the connected Facebook Custom Audience destination.

You can connect multiple Reverse ETL sources to the Facebook Custom Audience destination.

Mapping settings

In the mapping window, you will see the below two options:

• Create a new Facebook Custom Audience: Use this option to create a new custom audience in Facebook. You can specify the Audience name and Audience description of the new Facebook audience.
• Use an existing Facebook Custom Audience: Use this option if you have an existing custom audience. Choose the audience (automatically prepopulated by RudderStack based on your specified connection settings) from the dropdown.

Then, specify the below settings:

Choose identifier mappings

Map your warehouse columns to specific Facebook Custom Audience fields:

If you have selected the Create a new Facebook Custom Audience option, RudderStack creates a new audience in Facebook with the same Ad Account ID configured in the connection settings.

Schedule settings

RudderStack determines how and when to run a sync based on the sync schedule you set for your Reverse ETL connection.

Sync observability settings

Storing sync logs and snapshot tables may incur additional warehouse costs.

record event structure

The Facebook Custom Audience destination supports only record events.

A sample record event that RudderStack sends to Facebook is shown:

{
  "action": "insert",
  "channel": "sources",
  "context": {
    "sources": {
      "job_id": "2o9EffQ0mAIrGAgRxcLuwxhiXM0",
      "job_run_id": "cskrt1kme831eq0jrafg",
      "task_run_id": "cskrt1sme831eq0jrag0",
      "version": "v1.57.0-rc.1"
    }
  },
  "fields": {},
  "identifiers": {
    "EMAIL": "alex@example.com"
  },
  "messageId": "997b78eb-d06a-4123-b4d6-d3b87b62c3a9",
  "receivedAt": "2024-11-05T06:43:27.176Z",
  "recordId": "1",
  "request_ip": "10.1.17.46",
  "rudderId": "853ae90f-0351-424b-973e-a615e6487517",
  "type": "record"
}

Schema fields mapping

The following table details the schema fields mappings specified in the RudderStack dashboard:

RudderStack modifies the schema names visible in the dashboard to ensure better readability. However, during the event call, the field names must be exactly the same as the schema names specified by Facebook Marketing API, as mentioned in the table above.

Explicit formatting feature

By default, RudderStack formats the data as prescribed by Facebook before sending it to the destination, as shown in the below table:

If you turn on the Disable Format toggle in the RudderStack dashboard, RudderStack does not format the user data in the format prescribed by the Facebook Marketing API.

FAQ

Where can I find the Custom Audience ID?

1. To get your Custom Audience ID, go to the Facebook Ads Manager account. On the left navigation bar, select Audiences and choose the Ad account you have created the custom audience for.

2. Click All Audiences and select the specific custom audience from the list.
3. Finally, click the History tab. Here, you will find the audience ID under the Item Changed column:

Questions? Contact us by email or on Slack