X Pixel

Clicks from X are cheap until you count what they bought. Put the X Pixel on your landing page, fire a conversion event on the submit, and X reports leads you can set a cost-per-lead target against.

  • Custom code
  • Landing pages, Quiz funnels

Why connect it

Why X Pixel and LanderLab

  • Leads reported as X conversions

    A conversion event fires on the submit, so X Ads reports leads per campaign and ad, and conversion-optimized campaigns have something real to optimize toward.

  • Email and phone as match keys

    The event code accepts email_address and phone_number, which help X attribute conversions when its cookie alone can't.

  • The twclid kept on the lead

    X adds a twclid to the click's URL. A hidden field saves it, so a CRM record can be tied to the click behind it.

  • Ready for the Conversion API

    If your backend also reports to X's Conversion API, a shared conversion ID lets X count the pixel and server event once.

  • Audiences of visitors who didn't sign up

    Pixel data builds website audiences, so people who read your launch page and left can see a second post.

X Pixel on your landing pages

X sends traffic in bursts: a post takes off, a conversation trends, and clicks arrive faster than you can look at them. Without a conversion event from the landing page, X Ads can only report clicks and engagements, and you're left matching spreadsheets to guess what the campaign produced.

On LanderLab the X Pixel's base code runs from the page's or domain's custom code, and a conversion event fires when the form or quiz is submitted. The event can carry the lead's email and phone so X can match conversions it would otherwise miss, and a hidden field keeps the twclid on every lead.

It fits waitlists and launches, webinar and event registrations, newsletters and lead magnets, and B2B offers aimed at people who follow a topic closely.

X conversion tracking that counts leads

The base code reports visits on every page. The conversion is an event you create in X, fired when the form or quiz is submitted. From then on, X Ads shows conversions next to spend for every campaign and ad.

That's what turns X from a channel you judge by engagement into one you judge by cost per lead.

Match more conversions with email and phone

Cookies don't follow everyone. X's event code takes email_address and phone_number, and X's conversion documentation names the click ID, email and phone as the identifiers it matches conversions on. Passing the lead's email with the event gives X a second way to credit the campaign that brought the visitor.

The twclid from click to CRM

X's documentation asks advertisers to read the twclid from the landing page's query string whenever it's there. A hidden field named twclid does exactly that and saves it with the lead, next to the page, the variant and your UTMs. If your stack later sends sales through X's Conversion API, the click ID is already on the record.

When the landing page links on, Pass Through URL Params carries the twclid and your UTMs to the next page so nothing drops at the handoff.

Launch pages you can test mid-campaign

X campaigns move fast, so the page has to keep up. Split the launch page into two variants, keep the same pixel on both, and read the winner in LanderLab's analytics and by the LL Variant ID on each lead, while the campaign is still live.

Use cases

Ways to use X Pixel on paid traffic

  • 01

    Product launch waitlists

    Promoted posts during a launch week send people to a waitlist page. Each sign-up is an X conversion with the email as a match key, and the campaign optimizes toward sign-ups.

  • 02

    Webinar and event registrations

    A registration form counts every seat as a conversion, and visitors who read the agenda but didn't register see a reminder post.

  • 03

    Newsletter and lead magnet sign-ups

    A short form for a free report on a topic X users follow fires the conversion on submit, and the twclid on each lead lets you trace subscribers back to the posts that brought them.

FAQ

X Pixel integration FAQ

Anything not here, ask us.

X Pixel and LanderLab

Does LanderLab integrate with the X Pixel?

Yes, with X's own pixel in the page's or the domain's custom code, and a conversion event that fires when the form or quiz is submitted.

Is the X Pixel worth adding if I mostly run engagement campaigns?

Yes, as soon as you want to know what those campaigns produce. Without a conversion event X can only report clicks and engagements.

Can X match leads by email?

Yes. The event code accepts email_address and phone_number, which X uses alongside its click ID to match conversions.

Will the twclid reach my CRM?

Yes. A hidden field named twclid saves it from the URL with every lead, and it's delivered with the rest of the lead.

Do I need Zapier?

No. The pixel reports conversions to X, and the leads reach your CRM or sheet through LanderLab's integrations.

Other integrations

Plug in the rest of your stack.

Connect X Pixel and launch your next page.

Build the page, switch X Pixel on and send your ads to it. Free to start, no card.

From one prompt to qualified leads

Watch one prompt become a live solar quote funnel, every lead routed to your buyer, and the leaks flagged before they eat your budget.

0:00
0:59