X Conversion API: server-side conversions for X (Twitter) ads
Send each order to X from your server with the X click id, and the X Pixel copy with the same conversion id, so X counts it once.
Illustration of the event flow
What you get
X's formats
Phone numbers are hashed in E.164 with the plus sign; IP address and user agent are sent together, as X requires.
Your pixel events
Each canonical event maps to an event you created in X Events Manager; the same events power the X Pixel under Browser tags.
Signed requests
Requests are signed with OAuth 1.0a for your X Ads API app; credentials are encrypted and never shown again.
Where browser-only tracking loses the sale
Pick a situation your shoppers are in and watch one order take both paths.
A shopper from your Facebook ad places an order.
Illustration of what happens on shoppers' devices, not a measurement.
Set up in minutes
- 1Get X Ads API access for your developer app and generate an access token for a user with AD_MANAGER or ACCOUNT_ADMIN.
- 2In X Events Manager, note the pixel id and the id of each event (the last part of tw-pixel-event).
- 3Add the X destination in Trakero with those ids and the four app credentials.
Questions
Do I need X Ads API access?+
Yes. X's Conversion API is part of the Ads API; without approved access, use the X Pixel under Browser tags.
Platform rules from X: Web conversions (Conversion API).