What stands out in the release notes
I've been reading the GTM release notes every month since roughly 2018. Most of it is small stuff. A UI improvement here, a new variable type there, occasionally a bugfix wave. Rarely does something happen where I think: ok, this changes how we build.
2026 is different.
If you lay the four release notes from January to May next to each other, they form a picture that Google did not announce in a keynote. No marketing splash, no PR wave. Just four sober entries on a docs page. And yet what's happening is the biggest structural change to Tag Manager I can remember.
The keyword is Google tag gateway for advertisers. Sounds clunky, so let me unpack: first-party measurement infrastructure straight from Google.
Tag Gateway, what it actually is
Imagine you run a web shop. So far it worked like this: your browser loads a tag from googletagmanager.com that sends data to google-analytics.com. Both are Google domains. Safari blocks them partially under ITP. uBlock and Brave block them too. You lose signal.
Tag Gateway does something different. Instead of going to Google directly, traffic routes through your own domain. Cookies get set first-party. Browser blockers have nothing to block, because technically the requests come from your brand. Only behind the scenes are they relayed to Google.
# Before (third-party, blockable by ITP)
Browser → googletagmanager.com/gtm.js
→ google-analytics.com/g/collect
# With Tag Gateway (first-party via your domain)
Browser → your-domain.com/_/gtag/js
→ (relayed internally)
→ google-analytics.com/g/collectflowThis is essentially Server-Side GTM, but more deeply integrated. Where you previously needed a lot of manual Cloud Run configuration, Google now offers a ready-made solution right inside Tag Manager.
What's new here: Google isn't doing this through a new tool. Google integrates directly into the infrastructure you already have. Your CDN, in other words.
January 2026: GCP beta
The first step in January was Google Cloud Platform. From the January 5 release note:
This release introduces a new workflow for Google tag gateway for advertisers, allowing you to leverage Google Cloud Platform's Global external Application Load Balancer. This "one-click" integration directly in GTM and Google tag settings, streamlines deployment and configures your Google tag and tag containers to send data through your first-party web infrastructure before it is relayed to Google.
What technically happens: GTM gets a switch that, on click, provisions a Global Application Load Balancer in your GCP setup. The Load Balancer takes traffic from your own domain and relays Google signals (tag containers, analytics requests) cleanly to Google.
For GCP customers this is a "one-click" comfort upgrade. For everyone not on GCP, more like a test balloon to watch. It was the early step.
February 2026: More event data from Google Ads
Four weeks later, on February 4, came this almost unassuming update:
Google Ads will help advertisers measure more effectively and gain deeper insights with less manual configuration, by automatically collecting a broader range of event data from their websites. Advertisers may notice additional network requests to Google domains when these events are transmitted.
On the surface a marketing line. But between the lines something interesting happens. Google Ads is automatically collecting more event data from your site. You no longer need to configure for that.
What this means in practice: conversions you previously had to track manually, like clicks on "Add to Cart" or scroll depth or form interactions, get partly auto-detected. Auto-tagging becomes more powerful.
Sounds convenient. It is. But it comes with a price: you give up control. What Google collects from your site and how those signals are interpreted now runs partly under the hood. That can be good (if the algorithms are smart) or problematic (if your data structure has specifics).
My take: if you use standard GA4 events cleanly, you benefit. If you build custom tracking and care about granularity, watch the first weeks more closely.
January 2026: Akamai goes live
End of January, right after GCP, Akamai joined in.
This release introduces a new option to configure Google tag gateway for advertisers using Akamai as your content delivery network (CDN). This integration gives you greater control over your data, improving the accuracy of your Google Analytics reporting and driving conversions uplift.
Akamai is one of the largest CDN providers worldwide. Anyone running big shops often rides on Akamai or Cloudflare or Fastly.
This first Akamai integration was still rather manual. You had to set up routing rules in the Akamai console yourself, which is non-trivial. But: it was possible at all. Google had set the door open.
May 2026: Akamai and Fastly automated
Then May came. In my view, this is the release note that represents the actual update:
This release introduces a streamlined integration to configure Google tag gateway for advertisers using Akamai or Fastly as your content delivery network (CDN). You can now authorize Google to automatically detect your CDN zones and inject routing rules directly from the Google tag interface, eliminating the need for manual configuration in the Akamai Control Center or Fastly dashboard.
Let's read that again carefully. "Automatically detect your CDN zones and inject routing rules directly from the Google tag interface."
Meaning: you log into GTM, authorize Google to read and write your Akamai or Fastly settings, and Google configures your CDN routing rules itself. From the GTM UI.
For illustration, what happens behind the scenes at Fastly (simplified):
# Auto-injected by Google into Fastly VCL
sub vcl_recv {
if (req.url ~ "^/_/gtag/") {
set req.backend = F_googletagmanager;
set req.http.X-Forwarded-Host = req.http.host;
return(pass);
}
}fastly · vclPreviously you had to maintain this routing manually, in the Fastly dashboard between 10 other backend rules. Now Google writes it for you, and you only see it as "configured" in GTM.
That was unthinkable in January. In May, it's one click.
And Fastly comes along with it. Fastly is the CDN player running in many modern tech stacks (Vercel, some Shopify Plus setups, plenty of headless architectures). Meaning: Google now covers the three biggest players. GCP, Akamai, Fastly.
What this means together
Lay the four release notes on top of each other and you see a strategy.
First, Google is making first-party measurement the standard architecture. No longer an option for tech-heavy setups, but what everyone should be using.
Second, Google integrates directly into infrastructure you already have. CDN is not something you buy fresh. If you run a shop, you have one. If it's Akamai, Fastly or GCP, you can now activate Tag Gateway.
Third, the effort drops drastically. In January, the setup was still a project for a senior. In May, it's a self-service function.
Fourth, data quality goes up. That's not my claim, it's what Google writes themselves: "improving the accuracy of your Google Analytics reporting, and drive conversion uplift through enhanced signal recovery." Conversion uplift is business-relevant. If you're in the performance marketing game, that's felt.
My gut feeling on this: whoever takes the step now gains 6 to 12 months ahead of competitors who'll tackle this in 2027. Not because it's so complicated, but because it's communicated so quietly that it gets easily overlooked.
Who benefits
Very different depending on the setup. Here's an honest cut:
Massively relevant. You lose between 10 and 30 percent of your signals to browser blockers, depending on audience. Tag Gateway recovers a big chunk of that. Conversion uplift in the single-digit percent range is realistic.
Little direct benefit. You've already solved these problems, maybe with your own Cloud Run or GTM server container. But at some point you'll want to replace that setup, because Tag Gateway needs less maintenance.
Indirectly relevant. Tag Gateway helps with initial lead capture. What happens after (CRM, pipeline) is untouched.
Very high impact. Safari ITP otherwise eats a lot of signal. Tag Gateway bypasses that almost entirely.
Nothing here yet. An official Cloudflare integration isn't available as far as I know. I wouldn't be surprised if that lands late 2026. Until then, Cloudflare Workers as a DIY solution.
What I'd do in your place
First, check which CDN you actually use. Many don't know exactly because it often comes bundled with hosting. If you're on managed hosting like Cloudways, Kinsta or WP Engine, ask support. On AWS it's usually CloudFront, which isn't covered by Tag Gateway either.
Quick check from the terminal:
# Reveals your CDN provider
curl -sI https://your-domain.com | grep -iE 'server|x-served-by|cf-ray|x-cache|x-akamai'bashAnswers like "cf-ray:" → Cloudflare. "x-served-by:" → usually Fastly. "x-akamai-...:" → Akamai. "x-cache: cloudfront" → CloudFront. None of these headers → probably direct hosting without CDN, then you have different things to clarify.
Second, if you're on Akamai, Fastly or GCP, look at the Tag Gateway setup docs. It's no longer a massive project.
Third, before you activate: check your privacy docs and consent management. Tag Gateway changes how data technically flows, which touches your privacy policy. Not trivial, but solvable.
Fourth, plan a before/after comparison. Look at conversion volume and data quality in the first two to four weeks after activation. Pull baseline reports beforehand. Otherwise you won't know later what the actual uplift was.
Closing thought
I find it fascinating how quietly major updates sometimes come. Compared to GA4 migrations, which arrived with all the fanfare, Tag Gateway comes as a series of sober release notes. That's exactly what makes it quietly underrated.
Anyone who takes it seriously builds themselves a data foundation in 2026 that most competitors won't hear about until 2027 or 2028. Provided you take the two hours to check whether it works for you.