fbclid, gclid, and Friends: What Tracking Parameters Do and How to Remove Them

· 2 min read

Copy a link from almost any app in 2026 and you'll get something like this:

https://example.com/article?fbclid=IwAR2xK9...&utm_source=facebook&utm_medium=social

The article lives at https://example.com/article. Everything after the ? exists to track the click. Here's what each family of parameters actually does, and when you should strip them.

Click IDs: the per-click tracers

Click IDs are unique tokens generated for each individual click on an ad or shared link. They let the platform connect what you do on the destination site back to the specific ad impression you clicked.

Parameter Platform
gclid Google Ads
fbclid Facebook / Meta
ttclid TikTok
msclkid Microsoft Ads
twclid X (Twitter)
yclid Yandex
wbraid / gbraid Google Ads (iOS, post-App Tracking Transparency)

The key property: a click ID identifies the click, not the page. Forward a link with an fbclid intact and everyone who opens it gets attributed to your original click — polluting the advertiser's data and tying the link back to you.

Campaign tags: the aggregate labels

UTM parameters (utm_source, utm_medium, and friends) are campaign labels, not per-click identifiers. They're less invasive — they say "this link came from the March newsletter", not "this is click #8847294" — but they still misattribute everyone you forward the link to, and they still bloat the URL.

Email and session trackers

Email platforms append subscriber-level tokens: Mailchimp's mc_eid, HubSpot's _hsenc, ConvertKit's ck_subscriber_id. These are the most personal of the lot — the token maps directly to your email address in the sender's database. Forwarding an email link with mc_eid intact effectively shares your subscriber identity. Analytics session-stitching parameters like _ga and _gl behave similarly, linking the visit to your session on the referring site.

Why bother removing them?

Privacy — yours and your recipients'. Stripped links break the chain between the platform's ad logs and the people you share with.

Deduplication. The same article shared with three different tracking tails is three different URLs. Chat apps re-unfurl it, browsers re-fetch it, and "already read" detection breaks.

Longevity. Clean URLs are canonical URLs. Tracking-encrusted links look spammy in documents, age badly, and occasionally break — some sites mishandle unknown parameters.

Honesty. When you share a link, you're recommending a page, not volunteering as a data-collection relay.

How to strip them safely

The trap is that not every parameter is tracking. ?page=2, ?q=search-term, ?variant=blue change what the page shows — remove those and the link breaks. So "delete everything after ?" is the wrong rule.

The right approach is a known-tracker list: strip parameters that match known tracking keys (utm_*, the click-ID table above, email tokens) and keep everything else. The query cleaner does exactly this — paste one URL or fifty, and it returns canonical links with a report of what was removed. If you're unsure what a particular parameter does, drop the URL into the parser first and inspect it key by key.