X Conversions API
Server-side conversions to your X (Twitter) pixel with the twclid click id and hashed email and phone.
X (formerly Twitter) conversions are delivered server-to-server to your X pixel. The integration uses the Conversion API access token from Events Manager — the same route X's own server-side Google Tag Manager template takes — so you do not need an Ads API application or OAuth keys.
Credentials
| Field | Where to find it |
|---|---|
| Pixel ID | X Ads → Tools → Events Manager → your pixel. |
| Conversion API access token | Events Manager → Install pixel → Manual → Conversion API → Generate access token. Stored encrypted. |
| Event IDs (optional) | Events Manager → the event you created (Purchase, Lead, …) → its id, tw-<pixel>-<event> or the short form. |
Connect under Integrations → X Conversions API.
How events are named
X attaches a server event to an event you created in Events Manager. Paste the id of
your Purchase, Lead, Add-to-cart, Checkout, Content-view or Sign-up events and PixelFox
sends each conversion to the matching one. For a conversion with no id pasted, the
event is sent under the names X's own GTM template uses (gtm_purchase,
gtm_generate_lead, gtm_add_to_cart, …), which X resolves on its side.
Matching and deduplication
X requires at least one of the twclid click id, a hashed email or a hashed
phone (E.164); IP and user agent alone do not count, so an event with none of the
three is skipped rather than sent to be rejected. twclid is captured from X ad landings
and from the _twclid cookie the X pixel writes.
The event uuid is sent as conversion_id. An X pixel on the page firing the same
conversion with the same conversion_id is counted once.