This page is about the **Facebook Conversions API** destination. For documentation on other Facebook destinations, including Facebook Pixel, see the pages linked below.

| **[Facebook Offline Conversions](/docs/connections/destinations/catalog/facebook-offline-conversions/)** | Yes |

| **[Facebook Pixel](/docs/connections/destinations/catalog/facebook-pixel/)** | No |

{% include content/connection-modes.md %}

Next, set up your Pixel to work with the Facebook Conversions API destination. You can use an existing Facebook Pixel that you already have set up, or create a new one. If you don't already have a Facebook Pixel configured, follow the "New Pixel" instructions below to create one.

2. Choose Web, App, or Offline and then click **Get Started**.

3. Select "Conversions API" and then click **Connect**.

4. Choose "Segment" from the list of partners.

1. From the Destinations catalog page in the Segment App, click **Add Destination**.

2. Search for "Facebook Conversions API" in the Destinations Catalog, and select the "Facebook Conversions API" destination.

3. Choose which Source should send data to the "Facebook Conversions API" destination.

5. Enter the "Pixel ID" in the "Facebook Conversions API" destination settings in Segment.

For this option to work best, pass the same `external_id` from the browser and the server. To achieve this, go to the Facebook Pixel destination settings in Segment and enable the **Enable Advanced Matching** and **Use User ID or Anonymous ID as External ID** settings. By default, the Facebook Conversions API destination uses the `userId` (or `anonymousId` if not present) to set the `external_id`, so when you configure Facebook Pixel to use the same settings, Facebook matches users by those IDs.

If you use Facebook Conversions API as a stand-alone without certain data fields collected from the browser, the match rate might not be as high as if you included them.

For more information about Track calls, see the [Track method](/docs/connections/spec/track/) in the Segment Spec.

| Server Event Parameter | Requirement | Implementation p |

| ---------------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |

`event_source_url` is set by including `context.page.url` in the track event. The value used should be the browser URL where the conversion event occurred. If you're using a server library, set `event_source_url` manually. If you're using the Segment web library, `event_source_url` is set automatically.

If `action_source` is set to 'website', the `context.userAgent` and the `context.page.url` fields are required. Segment server-side libraries do not collect `context.userAgent` or `context.page.url` by default. This data must be retrieved manually from the client and passed to the server.

});

| Segment E-commerce Event | Facebook Standard Event |

| ------------------------ | ----------------------- |

To map any of your Segment Events (not listed in the table above) to a Facebook _Standard event_, use the Segment destination setting labeled **Map Your Events to Standard FB Events**. Then, when Segment receives an event that appears in that mapping, the event is sent to Facebook as the standard event you specified. All properties included in the event are sent as event properties.

| **Segment Property** | **Pixel Property** | **Notes** |

| ----------------------------------- | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- |

analytics.track("Clicked Email", {

});

Any properties you send that aren't listed above are sent in the `custom_data` part of the Segment payload to Facebook.

By default, Segment sends the `userId` as `external_id`, and if `userId` is absent falls back to `anonymousId`. To use a different field in your payload as the `external_id`, use the **Alternative External ID Field** setting. An example value for this setting would be `properties.externalId`.

For most events Segment sends revenue for the Pixel value field, but for

the pre-purchase events `Product Viewed` and `Product Added`, Segment

uses the value of the **Value Field Identifier** setting to determine which

property to use for the `value` field. This field defaults to

`price`.

{% include content/facebook-ldu-intro.md %}

})

After you start sending events, you should start seeing them in twenty

minutes. You can confirm that Facebook received them: