-
How do publishers keep making the same exact mistakes with ad tech over and over again? This didn't need to happen! duncanwc/1574339931635593217Permalink On twitter.com
♻️ 16 Retweets
❤️ 63 Favorites
Mood -2 🙁
-
First: any system that promises to generate IDs automatically with just a script is just using 3p cookies anyway and has no plan.Permalink On twitter.com
♻️ 1 Retweets
❤️ 14 Favorites
Mood 0
-
Second: the ones dependent on being on page to do fingerprinting are relying on a technique that does not work and is in the process of actively having browsers apply countermeasures.Permalink On twitter.com
♻️ 1 Retweets
❤️ 8 Favorites
Mood 0
-
Third: the ID scripts that are harvesting ID information automatically from form fields are only capturing new users and are likely, existing cases, to be considered illegal wiretapping for using that technique!On twitter.com
❤️ 13 Favorites
Mood -3 🙁
-
*existing cases consideredPermalink On twitter.com
Mood 0
-
So the only ID systems that could possibly be effective (maybe!?) are the ones where publishers actively are sending user emails from logins. If you're doing that then you don't need an on page script! You should be generating those IDs server-side. No heavy scripts needed!Permalink On twitter.com
♻️ 1 Retweets
❤️ 13 Favorites
Mood +1 🙂
-
Should you be doing IDs at all & is it a sustainable approach is a whole other question, but putting that aside, if you're going to do ID systems as a publisher, freaking think your approach through and don't just dump more scripts on the page. Don't make the same mistakes again!Permalink On twitter.com
♻️ 1 Retweets
❤️ 7 Favorites
Mood -1 🙁