Christian Heilmann

Removing UTM data from URLs automatically for cleaner bookmarks

Monday, August 9th, 2010 at 11:39 am

One of my real annoyances right now is that when you open a link from Google reader and some other systems you get the link followed by tracking data. Take for example the following tweet from Sam:

tweet

If you click the bit.ly link it expands to this abomination:

http://google-chrome-browser.com/test-your-browsers-html5-prowess-html5-test?
utm_source=feedburner&utm_medium=twitter
&utm_campaign=Feed%3A+Google-Chrome-Browser+%28Google+Chrome%29&utm_content=Twitter

I’ve come across lots of delicious bookmarks that still have all that campaign monitoring stuff in them, which is annoying. To work around that I’ve just written myself a tiny GreaseMonkey script:

Install un-UTM for GreaseMonkey

If the browser now opens a link that has UTM data in it, it removes the information and reloads the page without it to make for a cleaner URL.

Here’s the source of the script for the paranoid:

var loc = window.location.toString();
if(loc.indexOf('utm_source')!==-1){
  window.location = loc.replace(/\?utm_source.*/,'');
}

Tags: , , , ,

Share on Mastodon (needs instance)

Share on BlueSky

Newsletter

Check out the Dev Digest Newsletter I write every week for WeAreDevelopers. Latest issues:

Don't stop thinking, AI Slop vs. OSS Security, rolling your own S3 Despite AI you still need to think, Bitter lessons from building AI products,  AI Slop vs. OSS security and pointer pointer…
200: Building for the web, what's left after rm -rf & 🌊🐴 vs AI What remains after you do a rm -rf? Why do LLMs know about a seahorse emoji? What image formats should you use? How private is your car?
Word is Doomed, Flawed LLM benchmarks, hard sorting and CSS mistakes Spot LLM benchmark flaws, learn why sorting is hard, how to run Doom in Word and how to say "no" like a manager.
30 years of JS, Browser AI, how attackers use GenAI, whistling code Learn how to use AI in your browser and not on the cloud, why AI makes different mistakes than humans and go and whistle up some code!
197: Dunning-Kruger steroids, state of cloud security, puppies>beer

My other work: