X Ads vs Meta Ads: How Each Counts a Conversion, Compared

The rest is the detail, platform by platform, with what each documents and what it does not.

The parts are the same on both platforms. The rules around them are not.

None of these rows makes one platform better. They make the two dashboards incomparable, which is the point to take into a budget meeting.

Take one person and one purchase to see how far apart the two rules are. They saw an ad on each platform, liked the X post, and three weeks later searched your brand and bought.

• X, default settings

  The like opened a 30-day post-engagement window. The purchase three weeks later is an X conversion.

• Meta, default settings

  No link click, and the view was more than a day earlier. The purchase is not a Meta conversion.

• Your CRM

  One customer, who arrived through a branded search. Neither ad has a click on the record.

Meta moved in the other direction this year: on 3 March 2026 it narrowed click-through to link clicks for website conversions and moved other actions into a separate engage-through credit of 1 day. X's post-engagement window still counts a reply or a follow like a click. Both are legitimate choices. They just answer different questions, and the X one is the more generous of the two.

Both platforms want the browser tag and a server copy of the same event, deduplicated on a shared ID. The differences are in access and in timing.

• AccessX's own guide says a custom integration needs a developer account, Ads API access and OAuth 1.0a tokens. Through server-side Google Tag Manager, an access token generated in Events Manager is enough, with X's official template.
• How late an event may arriveMeta refuses a request containing an event older than 7 days. We found no X page stating a limit on conversion_time; the attribution window still decides whether a late event is credited.
• IdentifiersX matches on twclid, hashed email and hashed phone, with IP address and user agent only alongside one of them. Meta takes the fbclid in _fbc plus hashed customer details.
• PartnersX names Adobe, Tealium, MetaRouter, Datahash and RudderStack as Conversions API partners, and its Shopify app installs the Pixel in one click.

The setup guides for each side: the X Conversions API and the Meta Conversions API for lead generation.

Both platforms append a click ID to the landing page URL on an ad click, and both pixels pick it up by themselves. Everything outside the pixel, the server event and the CRM record, depends on you keeping it.

• twclid on XAppended automatically. The X Pixel passes it from the URL or a first-party cookie, and X recommends always including it in Conversions API requests. Redirects strip it, X says, so link straight to the page.
• fbclid on MetaKept in the _fbc cookie, and Meta documents how to build that value from the fbclid when no cookie exists, so a server event can still carry it.
• On the lead recordNeither CRM sees either ID unless your form hands it over in a hidden field. Without it, nothing downstream can join the deal to the click.

Keep both the same way: save them when the visitor lands, carry them to whichever page holds the form, and store each in a property of its own. The X Ads UTM guide covers the tagging that sits next to them.

For lead generation this is the part that changes cost per customer: telling the platform which leads became qualified leads and deals, so it looks for more of those.

On X, sending a qualified lead back works the way any server event does: send it as Lead (or a won deal as Purchase with its value) with the twclid you kept, and X credits it if it falls inside the event's window. X publishes no stage ladder or volume guidance, so how you map stages to events is your design. The X lead generation guide has two ladders, and sending CRM data back to Meta and Google covers Meta's side.

Both platforms now let a person submit their details without leaving the app. X Lead Gen Ads collect contact information in a native form, pre-filled after the first submission, and the leads come out as JSON, CSV or XLSX exports run by account administrators. Meta's lead ads use instant forms, which tools such as Zapier and LeadsBridge sync into CRMs, and Meta's Conversion Leads integration is built around the lead ID they carry.

The measurement consequence is the same on both: a form inside the app never loads your site, so there is no pixel event and no click ID, and the lead's source is whatever the import sets. HubSpot's ads tool, for example, connects Meta, Google, LinkedIn, Microsoft and TikTok accounts and not X, so an X form lead needs its source set on import by hand or by your own pipe.

X's help center lists Reach, Video Views, Pre-Roll Views, App Installs, Engagement and Website Traffic, plus the Sales objective (formerly website conversions), which needs the Pixel or the Conversions API and at least one conversion event; X recommends Autobid and paying by impressions there, and says there is no minimum campaign spend. Meta's incremental attribution, for comparison, is offered on the Sales, Engagement and Leads objectives. The Ads API's documented objective list on X has no lead objective yet, although the native forms exist.

What this post does not compare: audience targeting, reach and cost. X describes its audience in its own words, Meta in its own, and neither publishes a CPM or CPC benchmark that would let anybody say which is cheaper for your offer. A comparison of costs from somebody else's account says nothing about yours, so the next section is the test that does.

The only comparison that holds is the one in which both platforms are measured by the same rule, outside both dashboards.

1. Track clicks on both, on your own domain. twclid and fbclid on the visitor, UTMs on every ad, no redirects in the ad links. X warns that redirects strip twclid.
2. Join the clicks to the CRM. Every lead carries its click IDs and UTMs; every deal carries its value.
3. Pick one attribution model and apply it to both. First click, last click or a multi-touch model, stated beside the figure.
4. Compare cost per qualified lead and revenue ROAS, not CPA from either dashboard.
5. Read by click cohort once your typical time to close has passed, since both platforms finalise late and deals close later still.

Then send each platform the stages it can learn from, so both optimise on the same definition of a good lead. More in why GA4, Meta and Google never match your CRM and click-through vs view-through conversions.

Once both are measured on the same revenue, the result usually falls into one of a few patterns.

LeadJourney is one script on your site or in your GTM container, live in about 21 minutes, tracking server-side and first-party at 95%+ accuracy. On the first visit it issues the LeadJourney Click ID, its own visitor identifier kept for months, and every session is stored under it, with the platforms' click IDs as properties: twclid from X and fbclid from Meta, next to gclid, gbraid, wbraid, li_fat_id, msclkid and rdt_cid.

The X Ads integration and the Meta Ads integration sign in with OAuth and import campaigns, ad groups or ad sets, ads and daily spend. The lead is followed through HubSpot, Salesforce, Microsoft Dynamics 365, Zoho CRM, Pipedrive, Attio, Close, GoHighLevel, ActiveCampaign or Odoo, or to the Shopify or Stripe order. So cost per qualified lead and revenue ROAS for X and Meta sit on the same rows, under the same model, with no attribution window on our side.

The stages you map go back to each platform through its own Conversions API as they change: to X with twclid, hashed email and phone and a conversion_id that deduplicates against the X Pixel, to Meta with its click and customer data. The limits, plainly: we count clicks and visits, not likes, follows or views, and a lead from either platform's native form never visited your site. Tracking respects consent. Every plan starts with a 14-day free trial.

• X Ads conversion tracking and are X Ads worth it.
• X lead generation ads and the X Conversions API.
• Meta Conversions API for lead generation and Meta's incremental attribution setting.
• Click-through vs view-through conversions.
• Product: the X Ads integration, the Meta Ads integration and lead quality by channel.
• Definitions: view-through conversion, conversions API and click ID.