X Ads UTM Parameters: twclid, Naming and the GA4 Setup

The rest of this guide is the detail behind each sentence of that paragraph, in the order you would set it up.

Two different things end up in the query string, and they answer different systems. One is X's, added by X. The other is yours, and it only exists if you put it there.

• twclid, X's click ID

  Appended automatically to the landing page URL on a website click-through. It identifies the click for X's own conversion matching. Your analytics tool does not use it to name the source.

• UTM parameters, yours

  Whatever you typed into the URL. They tell GA4, your CRM and every other tool that the visit came from X, and from which campaign and ad.

• Macros, not documented

  X documents no placeholders that it fills in at click time. Third-party guides say there are none; X itself says nothing either way.

Keep the two apart in your head. Removing or renaming twclid costs you conversion matching in X; leaving out UTMs costs you the channel in your analytics. Neither replaces the other.

X's help center describes it as "a unique identifier that is automatically appended in the URL to help improve our ability to attribute site actions." There is nothing to switch on, and X documents no setting to switch it off. It is the identifier that ties a conversion to one specific click.

• The X Pixel reads it by itselfX says the Pixel passes twclid "from URL or first-party cookie". Nothing to do, as long as the parameter is still in the URL when the page with the Pixel loads.
• The Conversions API needs it storedA server event cannot read the URL. X's guide says to parse the twclid from the query string, store it with the form data, and always include it in the request.
• Or in a server GTM cookieX's official server-side GTM template, with first-party cookies on (the default), writes the click ID into a _twclid cookie on your domain for about 390 days.

So a redirect that drops the query string does double damage: it takes your UTMs and X's click ID in one go, and the Pixel on the final page never sees either. How the server side stores and sends the click ID is in the X Conversions API guide; the concept across platforms is in the click ID entry.

An X ad sends people to your site in one of two ways: a Website Card, the image or video with a website button, or a link written into the post copy. X's API is explicit that a Website Clicks post has "either a website card or a website link (not both)". Either way there is one URL, and that is where the UTMs go, as static values.

1. Build the URL with your naming convention (below) and a UTM builder, so nobody types a parameter by hand.
2. Paste it as the website URL of the card, or as the link in the post. Not a shortened link that redirects, and not a URL behind a tracking redirect.
3. Publish, then click the live ad once yourself. It is a real click, so do it once.
4. Check the landing page URL: it should be the URL you entered, with every UTM still present and a twclid appended.

https://www.example.com/demo?utm_source=x&utm_medium=paid_social&utm_campaign=<CAMPAIGN_NAME>&utm_content=<AD_GROUP>__<AD_NAME>

https://www.example.com/demo?utm_source=x&utm_medium=paid_social&utm_campaign=<CAMPAIGN_NAME>&utm_content=<AD_GROUP>__<AD_NAME>&twclid=<TWCLID>

The placeholders here are values you type, not macros X replaces. Since every ad carries its own static values, the URL is part of the ad's build, not an afterthought: name the campaign and the ad group in X first, then copy those exact strings into the URL.

Reddit, for one, documents macros in a few specific places. X documents none. Its conversion tracking pages name one parameter it appends, twclid, and no X help page or API reference we read describes a placeholder such as {{campaign_id}} that X would replace in a destination URL, or a setting that adds UTMs for you.

• Do not paste a placeholder and hopeIf X does not replace it, your reports fill up with the literal text, and a campaign called {{campaign_id}} groups every ad you ran into one row.
• Write the values per adThe campaign, the ad group and the ad, typed into each URL from the names you gave them in X. A spreadsheet that builds the URLs from the names keeps them identical.
• Let the click ID carry the restThe twclid identifies the exact click. A tool that keeps it on the visitor can tie a lead to the ad without any macro.

That last point is the practical answer to the missing macros. UTMs tell your analytics the channel and the campaign you named; the click ID, kept server-side, is what lets a system that knows X's ad IDs join the lead to the ad that was clicked.

Static values only work if they are consistent, and Google is strict about it: "Parameter values are case sensitive, e.g. utm_source=google is different from utm_source=Google." X adds a problem of its own, because the platform changed its name: some of your history says twitter, the new campaigns may say x. Pick one value, lowercase, and never vary it. This is the convention we recommend:

Two rules keep it clean. One medium for all paid X traffic. And keep organic X apart: a link in your own post or your bio gets utm_medium=social, which GA4 files under Organic Social, so the paid numbers are not flattered by traffic nobody paid for. More on the parameters themselves in UTM parameters explained.

X's own article on common analytics discrepancies and its campaign setup guide name most of the causes, and most of them are about the URL.

• Redirects strip the parametersX's words: "Do not use redirects in your URLs as these will strip the twclid off the URL." A redirect that drops the query string takes the UTMs with it.
• Shortened links in post copyA link shortener is a redirect. If the post links through one, check that the final URL still carries every parameter, or link the full URL.
• Clicks are not visitsX logs a link click when it happens; the page may never load. Slow pages, closed tabs and blocked scripts widen the gap before any tagging question arises.
• Different date rangesX Ads Manager opens on the last seven days. Compare the same dates in both tools, or a campaign that looks fine in one looks broken in the other.

A visit that arrives with no UTMs and no referrer matches GA4's definition of Direct, (direct) / (none), which is why untagged paid traffic so often ends up there. Stripped UTMs are also the most common reason a form loses its source on the way into the CRM.

GA4 decides the channel from source and medium with fixed rules, and Google publishes them. Paid Social needs two things: a source on Google's list of social sites and a medium matching ^(.*cp.*|ppc|retargeting|paid.*)$. Whether a given spelling of X is on that list is Google's decision, and the list changes, so check rather than assume: send one tagged test visit and look at the session default channel group in GA4.

X documents no Google Analytics integration of its own, so X's spend does not arrive in GA4 by itself. With the tagging in place, GA4 can report sessions and its own key events by the X campaign and ad you typed. Two things it still does not have: X's cost, and any idea what happened after the form, in your CRM.

A UTM can only describe a click: no click, no URL, no UTM. X's website conversion reporting counts more than clicks. Its post-engagement window credits a conversion after "likes, reposts, follows, replies, or URL clicks", for 30 days by default, and a post-view window credits one after an impression, for one day by default.

Neither report is wrong. X answers "what did these ads touch", the UTM report answers "which visit converted". The windows are set per event in Events Manager, and X recalculates existing data when one changes, so set them once and write the setting down. X's export of "Website conversions by tag" splits post-view from post-engagement conversions if you need to see how much of the count came without a click. The full account of windows and reporting is in X Ads conversion tracking.

A UTM describes the visit it arrived with, and nothing else. People rarely buy on the click from a feed. They read the post, click through, look around and leave. When they come back to buy, it is through a Google search for your brand, an answer in ChatGPT or your URL typed from memory. Each of those visits carries its own source, and none of them says X.

The hidden form field, the standard fix for UTMs in a CRM, records the visit that happened to end in a form. Last click in GA4 hands the lead to Organic Search. X may still count the conversion in Ads Manager, inside its window, but that number never reaches your CRM, where the lead now says organic. The X click that opened the journey survives only if something stores every session under one visitor from the first visit on, and keeps that record long enough for a sales cycle.

That record is what multi-touch attribution runs on. With it, the lead above shows X as first touch, ChatGPT in the middle and branded search as last touch, and multi-touch attribution can split the credit instead of guessing. The reporting consequences are in Are X Ads worth it?.

1. Every website URL is built from one convention: one lowercase source, one paid medium, a campaign name that matches the X campaign.
2. No URL redirects, and no shortened link in the post copy that drops the query string.
3. Click the live ad once, on a phone in the X app as well as on a desktop, and follow it through.
4. The landing page URL equals the URL you entered, all UTMs present, twclid appended. If not, find the redirect.
5. GA4's realtime report shows the visit with your source and medium, and the session lands in Paid Social.
6. The X Pixel Helper shows the Pixel firing once per event, and Events Manager's Recent Activity Log shows the hit with its parameters.
7. Submit the form and open the new record in your CRM: the source fields and the twclid are on it.

The Pixel side of the check (which events fire, and with what) is in the X Pixel setup guide.

LeadJourney is one script on your site or in your GTM container, live in about 21 minutes without a developer, tracking server-side and first-party at 95%+ accuracy, with the visitor's consent respected. On every visit it reads the UTMs, the landing page and the referrer, and on an X click the twclid, captured server-side on your own domain. It reports AI search engines such as ChatGPT, Gemini, Claude, Copilot and Perplexity as sources of their own, so the middle of the journey above is not filed as a referral.

What makes the X click survive is the LeadJourney Click ID: LeadJourney's own visitor identifier, issued on the first visit and kept in the browser for months. Every session is stored under it, and the platforms' click IDs, gclid, gbraid, wbraid, fbclid, li_fat_id, msclkid, rdt_cid and now twclid, are stored on it as properties of the session they arrived with. When the buyer from the table above fills in the form on Thursday, the Monday X session is already on the journey, and it stays there through the CRM to closed won, with no attribution window on LeadJourney's side.

The X Ads integration adds the other half. It signs into your X Ads account with OAuth, imports campaigns, ad groups, ads and daily spend with their history and keeps spend in sync every two hours, so the spend sits next to the leads and revenue your CRM reports, without a single macro. It follows each lead through the CRM and sends the stages you map back through the X Conversions API with the value, the currency, the twclid, hashed email and phone, and a conversion_id that deduplicates against a running X Pixel. The journey can be read under first click, last click, linear, position based and time decay without re-tracking.

Read verified reviews on Trustpilot, G2 and leadjourney.io/testimonials.

• The X Conversions API: setup, deduplication and CRM events
• X Ads conversion tracking: the Pixel, the Conversions API and CRM events
• X Pixel setup with Google Tag Manager, Shopify or the base code
• Are X Ads worth it?, X Lead Generation Ads and X Ads vs Meta Ads
• Reddit Ads UTM parameters, UTM parameters explained and the GCLID guide
• UTM parameters, click ID and first-party data in the glossary
• The X Ads integration, UTM and click ID tracking and AI search engine tracking