Facebook Conversions Connector Setup Guide
This article describes how to set up the Facebook Conversions connector in your account.
The Facebook Conversions connector requires the client-side Facebook Pixel tag to be running in the web browser. Learn more in the Facebook Help Center.
For the Facebook Pixel to work with the Facebook Conversions connector, enable the Tealium partner integration in your Facebook Ads account settings as follows:
- Log into your Facebook Ads Manager account and click Events Manager from the menu.
- In the menu, select Data Sources, then select the Pixel and click the Settings tab.
- Scroll down to the Server-Side API section.
- In the Partner Integration section, click Choose a Partner.
- Select Authorize Tealium Connection, and click Continue to enable Tealium.
If you do not see the option to toggle a partner integration, contact your Tealium Account Manager for support.
The Facebook Pixel tag automatically hashes user data. This pixel functionality cannot be changed.
This connector uses the following vendor API:
- API Name: Facebook Graph API - Facebook Pixel
- API Version: v12.0
- API Endpoint:
|Send Lead Event||✗||✓|
Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.
After adding the connector, configure the following settings:
- For your Facebook Pixel to work, ensure that you have followed the steps outlined in the Facebook Server-Side Events Connector Setup Guide to enable the partner integration for your Facebook pixel.
- For additional information, see the Facebook Pixel Setup Guide.
- If your pixel has been whitelisted and enabled for Tealium, a TealiumTestConnector event is tracked on your pixel. Click Test Connection to send a test event named TealiumConnectorTest.
- Check the Facebook Events Manager Pixel Overview to confirm the event was received.
- If your test fails, double-check the steps described in the Facebook Server-Side Events Connector Setup Guide.
Action Settings - Parameters and Options
Click Next or click the Actions tab. You configure connector actions in the Actions tab.
This section describes how to set up parameters and options for each action.
Deduplication for Facebook Pixel and Facebook Conversions API for Web Events
To configure this connector action to receive event IDs from the Facebook Pixel tag in your iQ Tag Management account, look for event attributes using the following naming convention:
fb_event_id_<Facebook Event>_<Tag UID>
IDs were previously generated as
fb_event_id_<Facebook Event>. These IDs continue to be generated but are considered legacy. The new IDs allow for use with multiple Facebook tags firing on a single page and offer a stronger tie back to the related tag. If you are using the legacy version, you must change the connector to the new ID.
Use a separate action for each type of event ID. Map the event-specific event ID attribute to Event ID with the matching event name mapped to Event Name. For example:
|Tealium Attribute/Value||Facebook Parameter|
|“Purchase” (Custom Text)||Event Name|
See the Facebook Pixel Tag Setup Guide.
When the Automatic Deduplication value is populated, the connector will look for the corresponding variable within the UDO object. You are no longer required to add an Event ID if this section is populated and you are using Tealium iQ. However, the following approach may still be needed when using EventStream without TealiumiQ.
The connector uses the following order of operations:
- If Automatic Deduplication is populated, and the value is found in the data layer, (for example,
fb_event_id_ViewContent_30) this value supersedes anything mapped in Event ID.
- If Automatic Deduplication is populated, but it can’t find the tag ID version, but can find the legacy version (with no ID attached), that value is used (for example,
- If Automatic Deduplication is populated, but the valie isn’t found, the mapped Event ID is used, if it is populated.
Tealium recommends using the Facebook Conversions connector for offline conversions instead of the Facebook Offline Conversions connector for new integrations.
To process offline and store events through the Facebook Conversions connector, set the
action_source parameter to
Action - Send Event
For User Data parameters, the following table notes the level of importance for some parameters. The importance level describes the parameter’s influence on your event match quality. For example, Email (em) has an importance level of Highest while Phone Number (ph) has an importance level of High.
|Event Source URL||
|Test Event Code||
|Data Processing Options||
|Pixel ID Override||
|Data Processing Options Country||
|Data Processing Options State||
|FB Login ID||
|Client User Agent (ua)||
|Client IP Address (ip)||
|Last Name (ln)||
|First Name (fn)||
|Browser ID (fpb)||
|Date of Birth||
|Click ID (fbc)||
|User Data is already hashed||
|Number of Items||
|Predicted Lifetime Value||
|JSON Template Variables||
Action - Send Lead Event
This action uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following thresholds is met:
- Max number of requests: 1000
- Max time since oldest request: 10 minutes
- Max size of requests: 1 MB
|Lead ID||(Required) The Facebook-generated 15 or 16 digit
|Event Name||(Required) Capture the lead stages you use in your CRM. The
|Event Time||A Unix timestamp in seconds indicating when the lead stage update event is updated by your CRM. The timestamp must occur after the lead generation time or the event may be discarded. If this field is not mapped, it will be initialized with the current timestamp.|
|Test Event Code||You can verify that your server events are received correctly by Facebook by using the Test Events feature in Events Manager. To find the tool, navigate to Events Manager > Data Sources > Your Pixel > Test Events.|
There are several options available to setup and manage Tealium’s server-side API partner integration with Facebook.
- The Facebook Partner Integration Gallery
- The Pixel Settings tab via the Choose Partner button:
- The web signal setup flow and Server-side API guidance card:
After sending your events, verify that Facebook has received them in the overview and breakdown views:
- Go to Business Manager > Pixels.
- Click on the pixel corresponding to the
In the Overview tab, change the view from All to Server to see the number of events you have successfully sent.
The Breakdown tab displays the breakdown of successfully sent events. Dropped events do not appear in the
Server Events Received column.
You can verify events within 20 minutes after sending them from your server.
For validation, use Facebook’s Payload Helper with your data parameter fields to see how structure your payload when it’s sent to Facebook from your server. See Facebook’s Support page for troubleshooting issues.
Learn more at Facebook’s Using the Conversions API.
Thank you for your feedback!
This page was last updated: August 11, 2022