pixeldetracking

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...

Sure, just that Google didn't propose it

thanks for the info! maybe it's Jerry: https://info.woolyss.com/

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...

5. use edge computing https://blog.cloudflare.com/zaraz-use-workers-to-make-third-...

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

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

yes, custom names for loader: https://www.simoahava.com/analytics/custom-gtm-loader-server... and even hosted on your own infra: https://developers.google.com/tag-platform/tag-manager/serve...

yes, french article is updated, but this english translation is quite old here it is: https://www.simoahava.com/analytics/custom-gtm-loader-server...

and you can host the container: https://developers.google.com/tag-platform/tag-manager/serve...

yes, i updated the french article but not this translation (no idea who did the translation btw), Google has a guide to host the container on your own infra: https://developers.google.com/tag-platform/tag-manager/serve...

ublock origin has actually an experimental option for this: https://github.com/gorhill/uBlock/wiki/Static-filter-syntax#...

only issue with blocking the proxies is that you can now decide to host the container on your own infra through docker, and it's documented by Google: https://developers.google.com/tag-platform/tag-manager/serve...

I guess this is very interesting for many people, especially in Europe with the "Google Analytics ban"

yes, they would need to get another identifier, and that's what is done with players like Facebook.

Sorry another of my articles in french: https://pixeldetracking.com/fr/les-signaux-resilients-de-fac..., but Facebook is making it easy to integrate their "Conversion API (CAPI)" with GTM Server-Side tagging

your are optimistic, most analytics guys I know are working with clients to transition to GTM server-side tagging

Today, most websites don't user server-side tagging from Google, but the "standard" Google Tag Manager (with 3rd party tags running on the browser)

Apple's Private Relay is great, but it won't help with server-side tracking (which is not based on IPs)

I'm the author, good to see this on HN, raising awareness on the topic

I don't know who made the translation and when it was made, but the original article in french (https://pixeldetracking.com/fr/google-tag-manager-server-sid...) contains more information on recent GTM "improvements"): mainly on how you can easily change JS library names and detailed instructions on how to host your container in other clouds or self-host