X Ads attribution and tracking, from the click to the closed deal

It can run alongside it or instead of it. X deduplicates a pixel event and a Conversions API event when both carry the same event and the same conversion ID. LeadJourney's tracking is server-side, so it does not depend on the pixel, and its events reach X through the Conversions API with a conversion ID, so a conversion the pixel also reports is counted once.

The Conversions API is a pipe: it moves events you already have. The hard part is having the right events. X recommends sending the twclid with every conversion and asks you to read it from the landing page URL and store it with the form or order yourself, and a custom integration needs a developer account, Ads API access and OAuth 1.0a. LeadJourney captures the click and the twclid server-side, follows the lead through your CRM, enriches the event with the value and hashed match keys from the record, and sends it as the stage changes. A hand-built setup only ever knows what your website knows, which is still just the sign up.

Because X counts differently, not wrongly. X credits a website conversion after any engagement with the ad, so a like, a repost, a follow or a reply counts as well as a click, inside a 30-day post-engagement window by default, plus a 1-day post-view window. Your CRM only knows the people who arrived and became leads. LeadJourney shows both: X's conversions where you buy, and the revenue that X clicks actually produced, measured on its own.

Yes, that is the point of tracking server-side. The click, the twclid and the visit are recorded on your own domain before an ad blocker, Safari or a declined banner can remove them, at 95%+ accuracy. Ads Manager keeps reporting what the pixel can see; LeadJourney shows you the measured numbers.

In LeadJourney, yes. The X click is stored on the visitor's LeadJourney Click ID, so when the same person comes back through Google brand search, a ChatGPT answer or a typed URL and converts, X is still part of that journey. Multi-touch models then share the revenue between X and the channel that closed, instead of handing all of it to the search.

Yes. X Ads is the ad platform formerly called Twitter Ads, the X Pixel is the former Twitter pixel, and the click ID is still twclid. Everything on this page applies to an account you opened as a Twitter Ads account.

Any CRM stage or paid order you map: marketing qualified, sales qualified, deal won, a Shopify or Stripe purchase, or all of them. Each event carries the value and currency, so the campaign is judged on revenue rather than a flat lead value.

X's Lead Gen Ads collect contact details in a native form on X, so the lead never visits your site and there is no twclid to capture. An account administrator exports the leads as JSON, CSV or XLSX, and from there they have to reach your CRM. Once they are there with their campaign, LeadJourney follows them to the deal like any other lead. For campaigns that send people to a form on your own site, the click, the twclid and the form fill are tracked server-side by default.

X's app installs the X Pixel in one click, and X does not document server-side events through it. LeadJourney reads the paid order from Shopify and sends it to X server-side with its value, so an order the pixel missed still reaches X, and the same order is attributed next to Meta, Google and email in one model.

Not natively. HubSpot's ads tool connects Meta, Google, LinkedIn, Microsoft and TikTok ad accounts, and X is not on that list. LeadJourney records the X click itself, follows each lead into HubSpot to the deal next to every other channel, and sends the qualified leads and won deals back through the X Conversions API.

No. X's MCP server manages the ad account: it reads and creates campaigns and manages event tags. LeadJourney's MCP server answers with your attribution data, so a question about which X campaigns started the deals you closed is answered from your CRM revenue, next to every other channel.

In LeadJourney, yes: the journey has no window, so the deal is credited to the campaign that started it regardless of the cycle length. X credits a conversion only inside its post-engagement window, 30 days at most, so for a long cycle map an early stage that predicts revenue, such as the qualified lead, as the event delivery learns from. The report that matches the late revenue to the ad lives in LeadJourney.

Identifiers are hashed before they leave, you control which stages and which fields are used for matching, and nothing is sent that you have not mapped. LeadJourney itself processes and stores data in the EU, signs a data processing agreement, and tracks first-party and server-side, so consent decisions are respected rather than worked around.

No. Connecting X Ads is a sign in, the CRM connection is the same, and mapping stages to conversions is a settings screen. Most accounts are live in about 21 minutes, and our team will do the setup with you on a call if you prefer.

The X Ads integration is part of the platform rather than a paid add on. Plans are priced by the marketing spend you track, not by seats, so your whole team can share one workspace, and every plan starts with a 14 day free trial without a credit card.