-
Shocking to see more publishers implement ad "id solutions" across the board while clearly not understanding what they do. It's not cookie sync any more, most of these are just picking up any form field and scraping whatever looks like an email or phone number as an ID.Permalink On twitter.com
♻️ 4 Retweets
❤️ 36 Favorites
Mood +2 🙂
-
While we can argue over if this is a CAN-SPAM violation or not... you're basically just destroying your own capacity to sell ads on the first party data you are collecting. It's just as bad--maybe worse--data leakage compared to the problem of 3rd party cookies & user unfriendly.On twitter.com
❤️ 9 Favorites
Mood -7 🙁
-
Publishers making all the same old mistakes in all new ways and somehow with *even more* kilobytes of code. It's a nightmarish new reality of even worse user surveillance and even more opportunity to cut publishers off at the knees once each ID scales up enough.Permalink On twitter.com
♻️ 1 Retweets
❤️ 10 Favorites
Mood -4 🙁
-
I may build a browser plugin that just blocks any third party script that has hooked an event listener to a form field. Never have I seen a practice so badly in need of active intervention.Permalink On twitter.com
♻️ 1 Retweets
❤️ 17 Favorites
Mood -3 🙁