X Ads
SyncBeacon reports your store purchases to X from the server using the X Ads conversion API. Matching rests on hashed email and phone, and setup needs a few things from X that other platforms don't ask for.
Works with
Shopify · WooCommerce · Shopware
Connects to
OpenAI Ads · Meta Ads · Google Ads · Microsoft Ads · Pinterest · Snapchat · X ads · TikTok (upcoming) · GA4 (coming soon)
Built for modern ecommerce
Simple to set up · EU-hosted · GDPR-ready · Secure event processing
Conversion events we support
PageView · ViewContent · Search · AddToCart · InitiateCheckout · AddPaymentInfo · Purchase
Also supported
OrderCancelled · Lead · CompleteRegistration
Last updated:
The X Ads Conversions API lets a server tell X that a purchase happened, so X can attribute it to an ad engagement without a browser tag doing the work. If you still search for it under its former name, Twitter Ads conversion tracking is the same product with a new brand: the ad platform now called X.
SyncBeacon takes the order from your store, applies the consent rules and posts the conversion to X. You don't configure any tag or container. The wider concept is covered in our server-side tracking guide.
| Signal | Sent to X | Notes |
|---|---|---|
| Hashed email | Yes | SHA-256 |
| Hashed phone | Yes | SHA-256, when present |
| IP address and user agent | Yes | Only when both exist on the event |
| Event ID (conversion_id) | Yes | Used for deduplication |
| twclid click ID | No | Not captured by the tracker script |
The practical consequence: X conversions are matched mainly on hashed email and phone. The SyncBeacon tracker script doesn't capture the X click ID (twclid), so there is no click-level fallback if the email or phone doesn't match an X account. That is a real limit, and it will vary by audience. We'd rather you know it up front than wonder later why X shows fewer conversions than Meta.
X isn't connected with a browser sign-in. You paste OAuth 1.0a keys and tokens from an X developer app, and that app needs Ads API access. You also need a Purchase Event ID, which you create yourself in X Events Manager. This takes longer than a one-click connection, so allow time, especially if Ads API access has to be requested.
Connect your store
Shopify, WooCommerce or Shopware.
Create a Purchase event in X Events Manager
Copy the Purchase Event ID. SyncBeacon needs it to know which conversion to credit.
Get X developer app credentials
Use a developer app with Ads API access, and have its OAuth 1.0a keys and tokens ready.
Enter them in Integrations and test
Paste the keys and the Purchase Event ID, place a test order, and check the Conversions page for the delivery status.
Any of the three launch sources. Shopify purchases come from order webhooks after an OAuth install, WooCommerce through the free plugin, and Shopware through the Admin API with an integration key, polled about every two minutes. Because the purchase comes from the store rather than the browser, it doesn't depend on the checkout theme, ad blockers or the shopper staying on the thank-you page. Store pages: Shopify, WooCommerce, Shopware.
X has the heaviest setup of the six launch destinations, so it's worth checking three things before you open Integrations:
If the setup feels heavy for the traffic you expect from X, start with Meta or Google Ads and add X later. The Pilot covers one ad platform, and all platforms are included on paid plans.
With no click ID, the quality of the hashed identifiers is what decides how many X conversions get credited. You can influence that in a few practical ways:
Compare what the Conversions page shows as delivered against X's own reporting. A gap there reflects matching and X's attribution, not a failed upload. If you need strong click-level measurement on X, say so in your own evaluation: this integration is built around hashed email and phone.
Related destination pages: Snapchat, Pinterest, Meta, Google Ads and OpenAI Ads. The Pilot includes one ad platform for 14 days, and paid plans include all of them, see pricing. SyncBeacon is not an official X partner.
Supported today
Stores: Shopify · WooCommerce · Shopware
Ad platforms: OpenAI Ads · Meta Ads · Google Ads · Microsoft Ads · Pinterest · Snapchat · X ads
FAQ
Yes, it is the same ad platform under its current name. SyncBeacon sends purchases to X through its Ads conversion API.
OAuth 1.0a keys and tokens from an X developer app with Ads API access, plus a Purchase Event ID created in X Events Manager. It isn't a one-click login.
A hashed email, a hashed phone number when present, IP address and user agent when both exist, and an event ID for deduplication.
Not in practice. The tracker script doesn't capture twclid, so X matching depends on hashed email and phone.
Yes, if you map the product to its X line item. SyncBeacon can pause the linked line item when stock reaches zero and resume it when stock returns. See the out-of-stock ad pause page for how stock changes are detected on each store platform.
X matches on hashed email and phone without a click ID, so visitors it can't match are missed. Denied consent and X's own attribution rules also reduce the count, and refunds aren't subtracted.
Get started in minutes. No developer required for Shopify, WooCommerce, or Shopware setup.
Solutions
Compare
Learn