X (Twitter) Server-Side Tracking on Shopify
If you've set up server-side tracking for Meta or TikTok and are wondering whether X (Twitter) offers something similar, the short answer is that Pixel Tracker doesn't support it for X today. X does have its own server-side and API-based conversion options in some form, but they are less standardized and less consistently documented than Meta's Conversions API or TikTok's Events API, largely a byproduct of how much the platform's ad tooling has changed since the Twitter to X rebrand.
This page explains what server-side tracking would actually do for your X campaigns, why it's a lower priority for most Shopify merchants right now, and what your realistic options are given where Pixel Tracker's support stands today. For the full picture of what Pixel Tracker does support for X, see the X (Twitter) Pixel overview.
What Pixel Tracker supports for X today
Pixel Tracker connects X (Twitter) through a client-side, browser-based pixel only. It sends PageView, ViewContent, AddToCart, and Purchase events directly from the customer's browser via a Shopify ScriptTag, the same installation method used for the other six platforms Pixel Tracker supports. There is no server-side or API-based component to this connection, and Pixel Tracker does not set up, manage, or maintain any such integration for X.
What server-side tracking would mean for X
Server-side tracking sends event data from your server, or a middle layer, directly to the ad platform, instead of relying only on the customer's browser. For platforms like Meta and TikTok, this recovers events lost to ad blockers, Safari's and Firefox's tracking protections, and iOS privacy restrictions, often a meaningful percentage of total conversions. In principle, the same benefit would apply to X: more complete conversion data, especially since X's client-side tag is commonly blocked. In practice, X's server-side options are less mature and less standardized than Meta's or TikTok's, which makes building and maintaining a reliable integration harder to justify right now. For more on how server-side tracking works generally and why Meta and TikTok are the two platforms Pixel Tracker supports, see Pixel Tracker's server-side tracking guide.
Why this is a lower priority for most Shopify merchants
For most Shopify stores, X (Twitter) is a smaller share of ad spend and conversions than Meta or TikTok, and its tracking documentation and product surface have changed enough since the rebrand that building against it carries more risk of breaking without notice. Pixel Tracker has prioritized server-side support for Meta and TikTok because those integrations, Conversions API and Events API respectively, are well documented, stable, and used by the largest share of merchants running paid ads on Shopify. X may get equivalent support in the future if its own tooling stabilizes, but there's no committed timeline for that today.
Your realistic options right now
For X specifically, the practical options are to run the client-side pixel as-is and accept some data loss from blockers and browser privacy settings, or to reduce reliance on X's own attribution by looking at your actual Shopify order data alongside pixel numbers. If accurate cross-channel measurement matters more than any single platform's own reporting, Pixel Tracker's multi-channel attribution guide covers how to do that without needing server-side tracking on every platform. Pixel Tracker's server-side tracking is available today for Meta and TikTok; both are covered in detail on their own server-side pages, linked below.
Frequently asked questions
Does Pixel Tracker support server-side tracking for X (Twitter)?
No. Pixel Tracker's X connection is a client-side browser pixel only. Server-side tracking is available today for Meta and TikTok, not for X.
Does X (Twitter) itself offer server-side conversion tracking?
X has some form of server-side and API-based conversion tracking, but it is less standardized and less consistently documented than Meta's Conversions API or TikTok's Events API, and it isn't something Pixel Tracker sets up or manages.
Will Pixel Tracker add X server-side tracking in the future?
It's possible if X's ad tooling and documentation stabilize, but there's no committed timeline. Meta and TikTok were prioritized because their server-side APIs are stable and widely used.
How much conversion data am I actually losing without server-side tracking on X?
It varies by store, but client-side-only tracking on X tends to lose more to ad blockers and browser privacy protections than Meta or TikTok do, since X's tracking domain is more commonly blocked.
What should I do instead if X server-side tracking matters to me?
Compare your actual Shopify order totals against what X Ads Manager reports to gauge the real gap, and consider Pixel Tracker's multi-channel attribution guide for a more complete view across all your ad channels, not just X.