Click ID and query parameter stripping
Browsers remove known tracking parameters from URLs before the site sees them, in some modes.
In one line
Can remove known tracking codes from links before the site sees them, in some modes
Browsers remove known tracking parameters from URLs before the site sees them, in some modes.
Controls whether a site can read the ad click ID at all. Safari strips in Private, Mail and Messages; Firefox in ETP Strict and Private; Brave in all modes by default; Chrome does not strip. Measurement teams lose attribution where stripping applies.
What it can and can't do
What the user does: You open a link with a tracking code while using a browser privacy mode
It can
- Strip known tracking codes from a web address
- Block the code from reaching the site
- Work in Firefox and Safari in some privacy modes
It cannot
- Remove codes it does not know about
- Run in Chrome, Edge or Samsung Internet by default
- Hide a code if you share the link before it is cleaned
- Stop trackers that use other methods like cookies or fingerprints
How it differs between platforms: Firefox in strict or private mode and Safari in private browsing strip codes. Chrome and Edge do not.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Not supported | Not available | Not listed | No stripping |
| Edge | Not supported | Not available | Not listed | Tracking prevention does not strip params |
| Firefox | Partial | 102 | 2022-06-28 | ETP Strict and Private only in release |
| Safari | Partial | 17 | 2023-09-18 | Private Browsing, Mail and Messages |
| Safari on iPhone | Partial | 17 | 2023-09-18 | None |
| Chrome on Android | Not supported | Not available | Not listed | None |
| Samsung Internet | Not supported | Not available | Not listed | None |
How a site asks for it
| API | Browser feature (no site API); site sees URL without the parameter |
| How access is granted | settings |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Applies per navigation |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Data you get
What comes back: Parameters removed from URL
Shape: none
How often: per navigation
No individual data fields. The signal is the access itself.
Technical limits
- Works from a maintained list: unknown parameters pass through
- Does not touch UTM keys
- Safari 27 beta adds Threads (xmt), YouTube (si) and X (twclid, cn, cxt) per a July 2026 code review; verify at release
- Server side tagging with first-party capture before stripping can still record it only if the parameter reached the server
The story
What it is
Some browsers remove known tracking codes from web addresses before the site can read them.
For you
You click a link with a long tail of letters and nothing seems different. The browser quietly cuts off the tracking part, so the site never sees it. You may notice your ad gets less personal.
For makers
Makers lose the click ID they use to prove an ad worked. They respond with server side tagging and other IDs. Browser makers use stripping to sell privacy, and ad teams must plan for it.
Where you see it
| Type | Example | Apps |
|---|---|---|
| ads | A shopper uses Brave and clicks an ad. The click ID is stripped, so the sale cannot be tied to the ad. | Brave, Google Ads |
| analytics | A marketing team sees traffic from Safari as direct visits and cannot credit the right campaign. | Google Analytics |
| social | A shared link with fbclid is cleaned in Messages, so the sender's tracking tail does not reach the friend. | Messages, Meta |
| shopping | A coupon site loses the code that proves a sale, and so gets less money from partners. | Honey, RetailMeNot |
| games | A game ad campaign cannot see which ads brought logged out players when the browser strips the click ID. | None named |
| security | A phishing link often hides a tracking tail. Stripping it removes one way to tell which target clicked. | None named |
Risks
- Not in every browser
- Sites work around it with other IDs
What the platform says
- Mozilla: Query parameter stripping. Firefox says it strips known tracking parameters in Strict mode and Private windows so sites cannot follow you by link.
- Apple: Link Tracking Protection. Apple says Safari removes tracking parts of links in Private Browsing, Mail and Messages.
Good uses and abuse
Legitimate uses
- User privacy protection
Known abuse
- Not applicable; site side counter is dropping parameters into cookies earlier or using first-party redirects
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 1 of 5 | How useful it is to honest apps |
| Friction | 3 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2022-06, Firefox 102: Query Parameter Stripping launched in ETP Strict and Private windows
- 2023-09, Safari 17: Link Tracking Protection stripping for Private Browsing, Mail, Messages
- 2025-09, Safari 26: AFP on by default in regular browsing; classified scripts lose query parameters and referrer (reports disagree whether Link Tracking Protection itself widened)
- 2026-07, Safari 27 beta: More platforms added to the strip list per TAGGRS code review (secondary source)
Related capabilities
Related
- Ad click IDs (gclid, fbclid, msclkid and more). Can tag your ad click so a later purchase links back to that exact ad
- Safari 27 IP based tracker blocking (beta). Can block requests to known ad tracker servers by their IP address in Safari 27 beta
Sources
- Firefox Query Parameter Stripping docs
- WebKit features in Safari 17.0
- PPC Land on Safari 27 tracker changes (Jul 2026)
How well checked: Based on official documentation.