X Ads Conversions API

Send web and app conversion events to X via the X Ads Conversions API.

For more detailed information about conversion events and the Conversion API, refer to the official X Ads Conversion API documentation.

Setup Guide

To set up X Ads Conversions API as a destination, you'll need to provide the following:

1. Authentication - Click the "Connect" button in the destination setup form. This will initiate the OAuth authentication flow. Follow the prompts to log in with your X account and grant Extract the required permissions. Make sure the account you authenticate with has AD_MANAGER or ACCOUNT_ADMIN access level for the ad accounts you want to use.

2. Pixel ID - The ID of your Twitter Pixel event source. You can find this in X Ads Manager:

   • Go to ads.twitter.com
   • Navigate to Tools section on the top left and click Events Manager
   • Your Pixel ID is shown in the Twitter Pixel event source (if you don't have one yet, select Add event source on the top right to create it)

3. Event ID - The ID of the specific conversion event you want to track. You can either:

   • Use an existing event: If you're already using an event with the Twitter Pixel, use that same Event ID. This allows you to deduplicate between Pixel and Conversion API events using the conversion_id field.
   • Create a new event: Inside your Twitter Pixel event source in Events Manager, select Add events on the right side, then select Install with Conversion API. The Event ID will be displayed.

Hashing and normalization

• When Apply hashing (SHA256) is enabled, Extract trims and lowercases email identifiers before hashing.
• Phone identifiers are normalized to E.164 before hashing.
• More detail: Identifier Hashing and Normalization.

Data Contract Information

info

Your source dataset must be compatible with the parameter requirements of X Ads Conversions API, as outlined in the X Ads Conversion API documentation. This includes adhering to the expected formats and field types. If your data does not meet these requirements, the sync may fail.

Important Notes:

• At least one identifier (twclid or hashed_email) is required
• Email addresses and phone numbers must be hashed using SHA256 before sending
• Extract can apply the hashing and normalization rules above for this destination when you leave automatic hashing enabled
• The conversion_id field can be used for deduplication between Pixel and Conversion API events within a 48-hour window

Web Conversions

Loading ....

Event Conversions (App Events)

Loading ....