Hacker Newsnew | past | comments | ask | show | jobs | submit | pixeldetracking's commentslogin

Thanks for sharing this! From the IAB, I'm not surprised unfortunately Normalize emails is "best practice" for all the dirty "unique identifiers" players, see ID5 for example https://support.id5.io/portal/en/kb/articles/passing-partner...


Cloudflare Zaraz seems to be an easier option unfortunately https://twitter.com/pixeldetracking/status/14957193559879434...


it will be called differently indeed, it's already there: https://www.simoahava.com/analytics/custom-gtm-loader-server...


you can also change the ressources names: https://www.simoahava.com/analytics/custom-gtm-loader-server... and you can host the container on your own infra: https://developers.google.com/tag-platform/tag-manager/serve...


you can also change the ressources names: https://www.simoahava.com/analytics/custom-gtm-loader-server... and you can host the container on your own infra: https://developers.google.com/tag-platform/tag-manager/serve...



the big difference is that I cannot audit the websites using this new version of GTM (and I don't trust marketers)


This method of the server sharing data with third parties was already possible before.


Sure, just that Google didn't propose it


So far they only propose their server proxy thingie. Is it clear what data they intend to share?


I agree, thought it has to be done properly (and most marketers are not used to that currently)


the "new" thing is that it's been pushed by Google, hence made a lot easier


There is nothing new for the few experts out there (yes Segment has been doing it, yes others also, yes you can do it yourself). But Google proposes it, well, the adoption is not the same...

I agree with you on the legal doctrine


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: