Prevent tracking based on link decoration via query string or fragment
See original GitHub issueITP 2.2 is reducing the lifetime of cookies set via document.cookie
when the navigation came from a tracking-enabled page and the destination URL includes query string parameters or a fragment: https://webkit.org/blog/8828/intelligent-tracking-prevention-2-2/
We already block the third-party scripts that would be extracting these IDs and setting a first-party tracking cookie, but we could in theory go further by:
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:25 (9 by maintainers)
Top Results From Across the Web
Prevent tracking based on link decoration via query string or ...
We already block the third-party scripts that would be extracting these IDs and setting a first-party tracking cookie, but we could in theory...
Read more >Intelligent Tracking Prevention 2.2 - WebKit
The kind of link decoration described above is being used for cross-site tracking of users. What If My Website Uses Query Strings or...
Read more >How to Use URL Fragments & Query Strings as Custom ...
Either use a simple URL query string or a URL fragment and push them into Google Analytics as a custom dimension. I will...
Read more >Boldly link where no one has linked before: Text Fragments
The fragment directive is a mechanism for URLs to specify instructions directed to the browser rather than the document. It is meant to...
Read more >Apple's ITP 2.2: 1-Day Expiration of Tracking Cookies Set Via ...
The link uses link decoration (it uses query string parameters and/or a fragment identifier). Let's take a closer look at the above three ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for expanding on your use case. I’ve filed https://github.com/brave/brave-browser/issues/13242 to track this. The fact that it’s been requested more than once suggests that many more developers are likely to want this too.
You’ll still see a
msclkid
parameter in links because we don’t rewrite links inside of pages, but if you click on the link, themsclkid
parameter will be removed before the connection to the other server.