How Do You Track Conversions on X (Twitter) Ads?

X (formerly Twitter) Ads conversions are tracked with the browser-based X Pixel for on-site events, plus the server-side X Conversions API (CAPI) for events that ad blockers or browser privacy restrictions would otherwise hide — the current recommended setup runs both together rather than relying on either one alone.

Installing the X Pixel

The X Pixel is a JavaScript snippet installed in two parts: base code placed across every page of the site, which initializes the pixel and tracks general site visits, and event code placed only on specific action pages — a purchase confirmation page, a lead form thank-you page — that fires after the base code has already loaded. The Pixel ID needed to generate this code is found in X Ads Manager under Tools, then Events Manager, then X (Twitter) Pixel.

Adding the Conversions API

The X Conversions API is a server-to-server integration that sends conversion data directly from a business's own server to X's ad platform, bypassing the visitor's browser entirely. Unlike the Pixel, which depends on JavaScript successfully firing in the user's browser, CAPI keeps working even when ad blockers, iOS privacy restrictions, or cookie consent opt-outs would otherwise prevent tracking. CAPI supports two categories of events: Web Events, such as page views, add-to-cart actions, purchases, and lead form submissions, and Offline Events, such as in-store transactions, call center bookings, and CRM-recorded sales.

Why both together, not one or the other

The Pixel alone misses every visitor blocked by an ad blocker or restricted by iOS or browser privacy settings — a growing share of traffic on most sites. CAPI alone misses the real-time browser-side signals that feed X's optimization algorithm during a campaign's early delivery. Running both together, with events deduplicated so the same real-world action isn't reported twice, is the setup that captures the broadest and most reliable conversion data.

What Offline Events cover that the Pixel can't

Because the X Pixel and CAPI's Web Events both depend on an on-site action to trigger, neither one can see a conversion that closes somewhere other than a website — a phone call booked through a call center, an in-store purchase, or a deal closed and recorded in a CRM well after the original ad click. The Offline Events category exists specifically to close that gap, letting a business upload or stream those later-stage, off-site conversions back to X so the campaign that originally drove the click still gets credit for the sale, even when the sale itself happened somewhere the Pixel was never present to observe.

Getting the event data right before scaling spend

Because CAPI events are sent from a business's own server rather than fired automatically by a browser, the event names, timestamps, and identifiers in each server call have to match what X's system expects, or events will silently fail to attribute rather than throwing a visible error. It's worth validating a small batch of test events against Ads Manager's reporting before scaling budget on the assumption that server-side tracking is working correctly — a mismatch here looks identical, from the advertiser's side, to a campaign that's simply converting poorly.

Bottom Line

Install the X Pixel's base code sitewide and event code on key action pages first, then add the Conversions API as a server-side layer on top rather than a replacement — that combination, not the Pixel by itself, is what keeps conversion tracking accurate as more traffic gets blocked at the browser level.