3 ms·
I've done something like that some years ago to ensure that the tracking we were using on our website worked even if a user had an AdBlock. (it wasn't a tracker
by 01acheru 7y ago
I've done something like that some years ago to ensure that the tracking we were using on our website worked even if a user had an AdBlock. (it wasn't a tracker as in ad tracker, but a tracker nontheless)
It was fairly trivial: instead of asking for the tracking script directly I put a small service of ours in front of it, so our website asked for foo.mycompany.com/stats.js that fetched the correct script and changed all URLs inside of it from mycomp.mytrack.com to foo.mycompany.com. Our service than acted as a proxy to mycomp.mytrack.com.
A simple solution that worked out for a while, lost by now, in a server, somewhere in Ireland...
- Valmar 7y agoEvil, but clever.
- 01acheru 7y agoThanks for the cleverness! As for the evil, it was a tracker whose data wasn't shared with 3rd parties, we needed to gather as much data about our users as possible since we are incredibly understaffed (one handles the business, one sells the product and I do the tech)... it helped us a lot with support requests and customer acquisition
- kingartur44 7y agoIn this way, you are opening a lot of things of your site to the advertizer. They can grab your users session cookies or even intercept everything they send to you
- 01acheru 7y agoJust to clarify, as I said it was not an ad tracker, all data was ours and ours only. It was 1st party tracking using a 3rd party service that was blocked by ad blockers. Anyway we don't use cookies for *.mycompany.com, and it was a session-less website.