Google Tag Manager proxy / server-side container #4321
Unanswered
Ultrabenosaurus
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I recently came across this article discussing a new version of Google Tag Manager, which i find extremely worrying as it seems that no conventional adblockers such as ABP or uBO would be able to help at all. Would AGH be able to detect and block this "proxy" subdomain setup? Can it already?
https://chromium.woolyss.com/f/HTML-Google-Tag-Manager-the-new-anti-adblock-weapon.html
tl;dr
GTM currently executes within the user's browser, collecting data, then sending it directly to Google and various other 3rd parties. All of this can pretty much be detected and blocked by current browser privacy settings and adblockers.
The new version will have website owners use A/AAAA records to point one of their subdomains directly to Google's IP addresses, use a single generic self-hosted script to pass the collected data to the "1st party" subdomain proxy, and then Google's service distributes the data to whatever 3rd parties the client chooses.
Much fewer scripts to load and process for the user, so mild benefits there for people not already blocking such things. However, it totally kills all transparency, the possibility for user consent, and the ability for browser privacy settings and traditional adblockers from detecting and blocking the process.
Beta Was this translation helpful? Give feedback.
All reactions