Every link on X goes through t.co
X wraps the links in your posts with its own t.co service. X's developer docs say "All URLs are wrapped with t.co shortener and count as 23 characters." The length of your tagged URL does not change your character count.
So shorten for the reader, not for the limit. A tidy branded link reads better in a post than a long query string, and it tells people where they are going.
t.co is on Google's list of social sources, as are twitter and twitter.com. An untagged click from X can count as social, but it says nothing about which post sent it. Tags give you the post.
Why utm_source should stay twitter after the rename
The rename to X raises a fair question, and Google's source list answers it. twitter, twitter.com and t.co are on the social list. x and x.com are not.
For organic posts this barely matters, because utm_medium=social meets Organic Social through the medium alone. Paid is different. GA4's Paid Social definition needs a source on the social list and a paid medium. utm_source=x fails the first test, so a promoted post tagged that way only meets Paid Other.
If you have used x for a while, you don't need to rewrite history. Switch new paid tags to twitter and note the date of the change, so anyone reading old reports knows why two rows exist.
| Tags | GA4 definition they meet |
|---|---|
utm_source=twitter&utm_medium=social | Organic Social |
utm_source=x&utm_medium=social | Organic Social, through the medium |
utm_source=twitter&utm_medium=paid_social | Paid Social |
utm_source=x&utm_medium=paid_social | Paid Other |
twclid on promoted posts
X adds its own click ID to ad clicks. Its web conversion docs say the click ID "should be parsed out of the query string parameter twclid" when it is present. Advertisers send it back so X can match conversions to the ad.
The same docs say the Conversions API needs at least one identifier, such as the click ID, an email address or a phone number. The click ID is the only one of those that arrives in the landing page URL. Point promoted posts at your real landing page, because TrimLink's redirect does not pass on a twclid added to a short link.
twclid does not name a channel in GA4. Keep UTM tags on every promoted post, with a paid medium and a campaign name that matches the ad campaign.
Tagging threads, replies and the profile link
Use utm_content for where the link sat: bio_link, thread_post_1, reply or pinned_post. If the same link appears in post 1 and post 8 of a thread, tag each one. You will learn fast whether anyone reads that far.
Replies deserve a tag too. A link in a reply to a busy post can pull its own traffic, and utm_content=reply keeps it from merging with the original post. Pinned posts run for weeks, so give them a campaign of their own.
Give the profile link its own campaign. It gathers clicks for months from every post that sent someone to your profile, so mixing it into a launch campaign blurs both.
The builder suggests twitter when the URL you paste is on x.com, twitter.com or t.co. For your own landing page, type it in. Shortening needs a TrimLink account, and UTM reports in TrimLink analytics are on Pro and above.
https://example.com/launch?utm_source=twitter&utm_medium=social&utm_campaign=launch_week&utm_content=thread_post_1