X (Twitter) Conversion API

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.

Start freeDestination: availableIntegrations
  • Browser SDK
  • Your server
  • WooCommerce
Trakero
  • X

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.

Today's deliveries

Purchase #1043

Chrome, ad blocker on · Meta CAPI · 0.4 s

The ad blocker stops the browser Pixel on its way to facebook.com. The same purchase leaves your server, reaches Meta through the Conversions API and is counted.

Sample deliveries. Pick a row to watch its route.

Shopper, Sent to, Took

Set up in minutes

  1. Get X Ads API access for your developer app and generate an access token for a user with AD_MANAGER or ACCOUNT_ADMIN.
  2. In X Events Manager, note the pixel id and the id of each event (the last part of tw-pixel-event).
  3. Add the X destination in Trakero with those ids and the four app credentials.
track.yourstore.comTrakero

Your store → your domain → Meta, Google, TikTok

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.

Start counting every order today

Create a free account, connect your store and watch a test order arrive in Meta Events Manager.

Free plan · No card needed · Set up in one afternoon