TL;DR
X (formerly Twitter) has both a browser pixel and a server-side Conversion API. Shopify has no native X sales channel, so the install path is Custom Pixels for the browser pixel or a GTM server container for the Conversion API. Most third-party Shopify tracking apps, including WeltPixel Conversion Tracking, do not support X today. For stores spending under $500/month on X ads, the browser pixel is enough. Above $3K/month, a GTM workaround or manual upload starts to make sense. If you are running Magento 2 instead of Shopify, our Magento extension catalog does include an X / Twitter Ads Server-Side Add-on.
Key Takeaways
- X's Conversion API [1] is the server-side counterpart to the X Pixel and accepts events like purchase, add-to-cart, page view, and lead.
- Shopify has no native X sales channel. Browser X Pixel must be installed via Custom Pixels in Shopify Admin [3].
- Most third-party Shopify tracking apps, including WeltPixel Conversion Tracking, do not support X. Plan accordingly.
- For X ad spend under $500/month, the browser pixel via Custom Pixels is sufficient. Above $3K/month, a GTM server container or manual upload becomes worth evaluating.
- If you are on Magento 2, our X / Twitter Ads Server-Side Add-on handles the X Conversion API natively. Shopify support is not on WCT today.
Does Shopify support X / Twitter server-side conversion tracking?
No, not natively for server-side. The browser pixel can be installed via Shopify's Custom Pixels editor [3], but X / Twitter is not in Shopify's list of native sales channels alongside Google, Meta, TikTok, and Pinterest.
For browser-side coverage, the path is Custom Pixels: copy the X Pixel JavaScript snippet from X Ads Manager [2] and paste it into a new Custom Pixel in Shopify Admin under Settings → Customer events. Shopify injects it on storefront pages and forwards Customer Events to it.
For server-side coverage via the X Conversion API [1], Shopify offers no native bridge. You need a GTM server container with an X tag template, a manual upload workflow that pushes conversions in batch from your order export, or a third-party app that supports X (and most do not, including ours).
The short version: X conversion tracking on Shopify is a DIY install today, whether you are running browser-only or browser + server.
Note on the Twitter / X rebrand
X Corp rebranded from Twitter in July 2023. The advertising platform was renamed from Twitter Ads to X Ads, the Twitter Pixel was renamed to X Pixel, and the Twitter Conversion API was renamed to the X Conversion API. The API endpoints, documentation, and event schema are functionally the same. We use "X" throughout this article; if you are searching for older documentation, both names will return relevant results.
How can I track X / Twitter conversions on Shopify in 2026?
There are four realistic paths, plus a fifth that involves waiting for native app support.
Option 1: Custom Pixel X Pixel install (browser-side only). The lowest-effort path. Copy the X Pixel JavaScript from X Ads Manager [2] and paste it into a new Custom Pixel in Shopify Admin. Configure it to fire on the standard events you care about: page view, purchase, content view, add to cart. This gets you browser-side coverage with no server infrastructure.
Option 2: GTM server container with X tag template. If you already run a server-side GTM container for Meta or Google Ads, you can add an X Conversion API tag to the same container. The X Conversion API [1] accepts the same event taxonomy as the browser pixel, so the tag template handles the schema translation. This only makes sense economically if the GTM container is already running for other channels, since standing one up just for X at sub-$5K/month spend rarely pencils out. If you are evaluating sGTM more broadly, this sGTM vs. native Shopify comparison covers the tradeoffs.
Option 3: Manual conversion uploads via X Ads Manager. X Ads Manager supports offline conversion uploads in CSV format. This is viable for high-volume stores that already export clean order data on a weekly cadence. It is tedious for ongoing use but works without any additional infrastructure. Access it under Conversion tracking → Upload conversions in X Ads Manager.
Option 4: Conversion tracking via Aggregated Measurement. For stores running X Ads campaigns targeting iOS users specifically, X also supports Aggregated Measurement (similar in concept to Apple's SKAdNetwork for app ads). This is more relevant for app-install campaigns than for Shopify storefront conversions, but worth knowing exists.
Option 5: Wait for a third-party app that supports X Conversion API. Most Shopify tracking apps do not support X today. This pattern mirrors other smaller-share channels like Pinterest, where a real CAPI exists but third-party Shopify apps deprioritize it because the merchant base needing it is a niche. For now, options 1-4 are your only paths.
When is X / Twitter server-side worth the effort?
The decision is straightforward once you put a spend number on it.
Under $500/month on X Ads: Install the X Pixel via Custom Pixels and move on. The signal loss from browser-only tracking at this spend level does not justify a GTM server container or manual upload workflow.
$500 to $3K/month: Verify that your Custom Pixel X Pixel is firing reliably. Use X Ads Manager's Events Manager to confirm events are landing. At this spend level, the browser pixel is usually sufficient as long as it is wired correctly. If you are seeing conversion mismatches between Shopify Analytics and X Ads Manager, revisit Option 1 above and check for ad-blocker or iOS Safari signal loss.
$3K+/month: Browser signal degradation starts affecting X's auction algorithms in noticeable ways. If you already have a GTM server container running for Meta or Google Ads, adding the X Conversion API tag is a reasonable afternoon of work. If you do not have sGTM set up yet, the cost-benefit on a dedicated container just for X usually does not work. The manual upload route (Option 3) is a more realistic answer at this spend level.
Rule of thumb: X Conversion API is worth dedicated infrastructure once your X spend is high enough that improved conversion signal would change campaign decisions. For most Shopify merchants running X Ads, that threshold is somewhere north of $5K/month, and even then only if a GTM server is already running for other channels.
Does WeltPixel Conversion Tracking support X / Twitter?
No, not today.
WeltPixel Conversion Tracking handles server-side event forwarding with deduplication for GA4, Meta, TikTok, and Google Ads. Those four channels represent where the majority of Shopify ad spend sits. X / Twitter is a smaller share of Shopify merchants' paid social budgets, which is why third-party Shopify tracking apps deprioritize it.
For now, the practical recommendation is: install the X Pixel via Shopify Custom Pixels for browser-side coverage, evaluate whether your X spend justifies a GTM server container or manual upload workflow, and install WeltPixel Conversion Tracking for the four channels where it has complete server-side coverage today.
If you are running Magento 2 instead of Shopify, our X / Twitter Ads Server-Side Add-on ships native X Conversion API integration. The gap above does not apply on the Magento side.
FAQ
Does X / Twitter have a Conversion API like Meta?
Yes. The X Conversion API [1] accepts server-side events including purchase, add-to-cart, page view, content view, and lead. It works similarly to Meta CAPI in that you send events from your server with a matching event ID to deduplicate against browser-side pixel events. The official documentation is at developer.x.com/en/docs/x-ads-api/measurement/web-conversions/conversion-api.
Does Shopify have a native X / Twitter sales channel?
No. Unlike Google, Meta, TikTok, and Pinterest, X does not have a first-party Shopify sales channel. Browser X Pixel installation is via Custom Pixels [3], and any server-side coverage requires DIY infrastructure.
Is the X Conversion API the same as the old Twitter Conversion API?
Yes. Twitter renamed to X in July 2023, and the Conversion API was renamed accordingly. The endpoints, event schema, and integration patterns are the same as the pre-2023 Twitter Conversion API. If you find older documentation referring to "Twitter Pixel" or "Twitter Conversion API," it applies to the current X products.
Can I use a GTM server container for X Conversion API on Shopify?
Yes, if you already have a server-side GTM container deployed. X Conversion API accepts events from sGTM via a custom tag template. This only makes sense economically if the GTM server container is already running for other channels like Meta or Google Ads. Standing up a container just for X is rarely cost-effective.
Why don't more Shopify tracking apps support X / Twitter?
X's share of Shopify merchants' paid social budgets is smaller than Meta or TikTok, so third-party apps prioritize higher-volume channels first. The pattern is similar to Pinterest and Microsoft Ads: a real Conversion API exists, but the merchant base running enough X spend to need server-side tracking is a niche. Expect this to change as X's ad business evolves.
What is the quickest way to check if my X tracking is broken?
In X Ads Manager, go to Tools → Events Manager and check the event log for your X Pixel. Recent events with non-zero counts mean browser tracking is firing. Zero recent events within 24 hours of a purchase means the pixel is misconfigured. For server-side, check whether events are tagged as "API" versus "Pixel" in the event source column.
What WeltPixel Conversion Tracking Does Cover
WeltPixel Conversion Tracking handles server-side event forwarding with shared event_id deduplication for GA4, Meta, TikTok, and Google Ads, which is where most Shopify stores have concentrated ad spend. If those four channels are where your budget lives, WCT eliminates the browser signal loss that degrades Meta's Advantage+ audience signals and Google's Smart Bidding.
X / Twitter is not on WCT today. Until it ships, the practical recommendation is: install the X Pixel via Custom Pixels for browser coverage, and use WCT for the four channels it handles today.
If you are on Magento 2, the X / Twitter Ads Server-Side Add-on handles the X Conversion API natively.
Install WeltPixel Conversion Tracking
Sources
- X Developers. "X Ads API: Web Conversions Conversion API." https://developer.x.com/en/docs/x-ads-api/measurement/web-conversions/conversion-api
- X Business. "Conversion tracking for websites." https://business.x.com/en/help/campaign-measurement-and-analytics/conversion-tracking-for-websites.html
- Shopify Help Center. "Custom Pixels." https://help.shopify.com/en/manual/promoting-marketing/pixels/custom-pixels
- WeltPixel. "X / Twitter Ads Server-Side Add-on for Magento 2." https://www.weltpixel.com/products/x-twitter-ads-server-side-addon