Connect Reverse ETL Source to Bing Ads Offline Conversions

This guide takes you through the steps to connect a Reverse ETL source to the Bing Ads Offline Conversions destination.

Set up connection

The Reverse ETL feature supports only source-driven pipeline configuration.

Make sure you have set up a RETL source and connected it to your Bing Ads Offline Conversions destination before following the below steps.

1. Confirm the connection settings for Bing Ads Offline Conversions destination and click Continue.
2. In the Data Mapping section, select the Object.
3. Specify the Sync mode to specify how RudderStack should sync the data to Bing Ads.
4. In Choose identifier, specify the warehouse column that RudderStack uses to identify your records.

You can map this warehouse column to any of the following Bing Ads fields:

• EMAIL
• MICROSOFT_CLICK_ID
• PHONE

5. Map the other warehouse columns to specific Bing Ads fields using the Map fields setting.

Supported mappings

RudderStack automatically maps the following schema fields to the corresponding Bing Ads properties depending on the type of operation:

Create

For any field x of type record:

Update

For any field x of type record:

Delete

For any field x of type record:

Mapping considerations

• conversionName must exactly match the goal’s Name in Microsoft Advertising. The payload does not include a goal ID — linkage is by name only, so a mismatch silently drops the conversion.
• conversionTime must fall within the goal’s conversion window measured from the click time, and you should express it in the ad account’s timezone (not UTC).
• conversionTime must be later than the recorded click time.

record event structure

The Bing Ads Offline Conversions destination supports only record events.

A sample record event that RudderStack sends to Bing Ads Offline Conversions is shown:

{
  "action": "insert",
  "context": {
    "sources": {
      "job_run_id": "<job_run_id>",
      "task_run_id": "<task_run_id>",
      "job_id": "<job_id>",
      "version": "<version>"
    }
  },
  "recordId": "2",
  "rudderId": "2",
  "fields": {
    "microsoftClickId": "<microsoft_clickid>",
    "conversionTime": "2006-01-02T15:04:05Z",
    "conversionName": "<conversion_name>",
    "conversionValue": 100,
    "externalAttributionCredit": "0.5",
    "externalAttributionModel": "<goal_name>",
    "email": "<email>",
    "phone": "<phone>"
  },
  "identifiers": {
    "Email": "alex@example.com"
  },
  "type": "record"
}

FAQ

Why can’t I add a Reverse ETL source from the destination page?

The Reverse ETL feature supports only source-driven pipeline configuration. It means that you must configure a Reverse ETL source in RudderStack and then connect it to a new or existing destination. Note that this destination should not be connected to any other source.

See Reverse ETL FAQ for more information.