9 ms·
Be careful what you wish for. Ultimately you can't stop publishers from using third-party tracking code in a first-party context. This is just the easiest (lazi
by SheinhardtWigCo 6y ago
Be careful what you wish for. Ultimately you can't stop publishers from using third-party tracking code in a first-party context. This is just the easiest (laziest) way for publishers to do so.
It's not like publishers will give up on integrating third-party tracking code into their tech stacks once this technique is dead. They'll have to do so at a deeper level, e.g. reverse proxies, NPM modules, etc.
Next battle in this war: adtech code becomes indistinguishable; tracking IDs start appearing in all exit links from major publishers; adtech firms & publishers coordinate on the backend to sync those IDs. What then, get rid of URLs?
- gruez 6y ago>Next battle in this war: adtech code becomes indistinguishable; tracking IDs start appearing in all exit links from major publishers; adtech firms & publishers coordinate on the backend to sync those IDs. that can be easily filtered out eg. https://addons.mozilla.org/en-US/firefox/addon/link-cleaner/ https://addons.mozilla.org/en-US/firefox/addon/link-cleaner/
- unlog 6y agoThey mean the link won't work unless it has the id, which could be as mentioned indistinguishable
- SheinhardtWigCo 6y agoIt would be easy to come up with an encoding scheme that evades detection.