- \n
- Google Tag Gateway changes where your Google scripts load from. It's a CDN configuration change that recovers data lost to hostname-based blocking, covers Google products only, and does nothing for Safari's 7-day cookie cap. <\/li>\n\n\n\n
- Server-side GTM changes where events get processed and where cookies get written. It moves the event pipeline off the browser entirely, writes cookies via HTTP headers so ITP doesn't apply, and works with any platform that has a server-side API.<\/li>\n<\/ul>\n\n
If your stack is Google-only and your conversion cycle is short, GTG is a reasonable low-effort win. If either of those isn't true, it won't address your issues.<\/p>\n\n
![\"Vergleich](\"https:\/\/taggrs.io\/wp-content\/uploads\/2026\/05\/google-tag-gateway-vs-server-gtm-setup.svg\" "\\"\\"")
<\/figure>\n\nWas ist Google Tag Gateway?<\/h2>\n\n
Google Tag Gateway is a Google-managed proxy for your Google tags<\/strong>. Instead of loading from\u00a0googletagmanager.com, your Google scripts load from a path on your own domain, something like\u00a0yoursite.com\/metrics. GA4<\/a> data collection shifts from Google's collection endpoint to that same path.<\/p>\n\n
The domain is yours. <\/strong>Google manages the infrastructure behind it. Your CDN or load balancer forwards that path to Google. Cloudflare came first, followed by Akamai and Fastly, then Google Cloud Platform, which reached general availability on 1 June 2026<\/a> using GCP's global external Application Load Balancer. Amazon CloudFront support arrived after that, configured through Tag Assistant. Setup is mostly a CDN configuration change and a container update.<\/p>\n\n
Es gibt noch eine zweite M\u00f6glichkeit, GTG auszuf\u00fchren: Du aktivierst es innerhalb eines bestehenden server-seitigen GTM-Containers. In diesem Fall wird GTG dort ausgef\u00fchrt, wo dein Container l\u00e4uft, in der Regel auf einer Subdomain wie data.yourite.com. <\/p>\n\n
One hard constraint worth naming upfront: GTG covers Google products only<\/strong>. So GA4, Google Ads<\/a>, Floodlight, and Google Tag are included. If you run Meta, TikTok, Klaviyo, or anything outside that ecosystem, GTG doesn't touch those events.<\/p>\n\n
Was wird durch GTG behoben?<\/h3>\n\n
Die meisten Werbeblocker blockieren Anfragen an bekannte Hostnamen von Drittanbietern. googletagmanager.com steht auf jeder wichtigen Blockierliste. GTG umgeht dies, indem es diese Anfragen \u00fcber Ihre Domain leitet, die auf keiner Liste steht. <\/p>\n\n
That's a real improvement. Real-world aggregated data puts the uplift at around 4-6% for Google data that would otherwise get dropped at the script level. For more details, see the comparison data by Niek Schlepers<\/a>.<\/p>\n\n
Google's own launch figure was higher, at around 11% signal uplift. The gap between that and independent measurements isn't necessarily either side being wrong<\/strong>. Google's number reflects setups where the gateway was configured well on sites that previously had no first-party routing at all. Independent tests tend to measure incremental gain on sites that already had some protection in place. Where your site lands depends on how much of your traffic runs blockers that match on hostname only, which is the specific loss GTG addresses.<\/p>\n\n
Zwei Dinge, die GTG nicht behebt<\/h3>\n\n
1. Das Pfadproblem<\/h4>\n\n
Erstens: GTG l\u00f6st das Pfadproblem nicht. GTG \u00e4ndert die Dom\u00e4ne und l\u00e4sst dich ein eigenes Pfadpr\u00e4fix w\u00e4hlen, aber die bekannten Endpunktmuster bleiben in der URL. Eine GA4-Datenerfassungsanfrage trifft immer noch auf \/g\/collect<\/strong> hinter deinem Pr\u00e4fix, etwa so yoursite.com\/metrics\/g\/collect?v=2&tid=G-12345678 <\/strong>. Werbeblocker wie Ghostery und uBlock Origin suchen nicht nur nach dem Hostnamen. Sie filtern auch nach bekannten Pfadsignaturen, und \/g\/collect ist ein gut dokumentiertes Muster in den meisten gro\u00dfen Blockierlisten, unabh\u00e4ngig davon, welche Domain sie bedient. Ausgefeilte Blocker fangen diese Anfragen trotzdem ab, was die M\u00f6glichkeiten von GTG einschr\u00e4nkt. <\/p>\n\n
2. Lebensdauer des Cookies<\/h4>\n\n
Cookies are still set by JavaScript running in the browser. When your GTM container fires client-side, it writes cookies via document.cookie. Safari's Intelligent Tracking Prevention caps those cookies at 7 days. Doesn't matter which domain served the script. The cookie origin is the browser's JavaScript environment. GTG doesn't change that layer.<\/p>\n\n
F\u00fcr jede Attributionsreise, die l\u00e4nger als eine Woche dauert, oder f\u00fcr jeden Besucher, der nach 7 Tagen in Safari zur\u00fcckkommt, um zu konvertieren, gilt weiterhin die 7-Tage-Obergrenze. So wie zuvor. Das Laden des Skripts hat sich verbessert, das Cookie-Problem hat sich nicht verschoben. <\/p>\n\n
Safari has kept tightening this. Safari 27, which shipped in September 2026, added blocking at the network transport layer<\/a> - it now checks the destination IP of outbound connections, not just the domain a script came from. That's worth reading if you're considering GTG specifically, because it's the clearest example of a browser-level change that a first-party domain doesn't solve.<\/p>\n\n
What changed in GTM in August 2026<\/h3>\n\n
Google has been merging Google Tag and Google Tag Manager into a single system. The GTM interface now has a redesigned Overview page, container configuration has moved into a Settings section, and triggers, variables, templates and folders sit under a collapsible Advanced section. Google also added visual tagging, which lets you configure some events by selecting elements directly on the page.<\/p>\n\n
The part relevant here is the architecture. Google says the update allows Tag Manager containers to send data directly to Google destinations. That tightens the integration between GTM, the Google tag and the gateway, and it makes the Google-only path smoother than it was when this comparison was first written.<\/p>\n\n
It doesn't change the two limits above. Cookies are still written by JavaScript, so ITP still applies, and the coverage is still Google products only. But if you're weighing effort as part of the decision, the Google-only route got easier in August.<\/p>\n\n
What is Server-side GTM?<\/h2>\n\n
Serverseitiges GTM nimmt die Ereignisverarbeitung komplett aus dem Browser heraus und verlagert sie auf einen von Ihnen kontrollierten Server.<\/p>\n\n
Your browser sends one event to your server. The server receives it, processes it, and forwards it to each platform via server-to-server API calls. If you use the Enhanced Tracking Script<\/a> along with your server container, the ad blockers have no visibility into those calls. There's nothing running in the browser to block.<\/p>\n\n
Wie funktioniert das serverseitige GTM anders?<\/h3>\n\n
Die Cookie-Situation \u00e4ndert sich erheblich. Dein Server schreibt Cookies mit HTTP Set-Cookie Antwort-Headern. Die 7-Tage-Beschr\u00e4nkung der ITP gilt f\u00fcr Cookies, die von JavaScript geschrieben werden. Cookies, die \u00fcber Header von einem Erstanbieter gesetzt werden, unterliegen dieser Beschr\u00e4nkung nicht. Eine korrekt konfigurierte server-side Einrichtung kann First-Party-Cookies schreiben , die 365 Tage oder l\u00e4nger g\u00fcltig sind<\/strong>. <\/p>\n\n
F\u00fcr Websites, bei denen Kunden Wochen brauchen, um sich zu entscheiden, ist dieser Unterschied in der Cookie-Lebensdauer der Unterschied zwischen einer genauen Zuordnung und einer absichtlich unvollst\u00e4ndigen Zuordnung.<\/p>\n\n
Coverage<\/strong> is another gap server-side GTM fills. The same container can route events to GA4, Google Ads Enhanced Conversions<\/a>, Meta Conversions API, TikTok Events API<\/a>, and most other platforms that offer a server-side API. If cross-channel campaigns<\/strong> are losing signal and it's starting to show up in your retargeting performance, one event pipeline to all platforms is where the structural fix sits.<\/p>\n\n
Der Kompromiss? GTM ben\u00f6tigt Hosting, Konfiguration und GTM-Kenntnisse, um gut zu funktionieren. Es ist nicht einfach umzuschalten. <\/p>\n\n
Google Tag Gateway vs Server-Side GTM: A direct comparison<\/h2>\n\n
![\"\"](\"https:\/\/taggrs.io\/wp-content\/uploads\/2026\/05\/image-3-1024x535.webp\" "\\"\\"")
<\/figure>\n\n