By Enterprise marketers are spending millions — sometimes billions — on digital advertising, only to have browsers silently discard the tracking tags that measure whether any of it is working. Safari, Firefox, and Chrome have each independently moved to restrict or block third-party cookies and trackers, and ad blockers compound the damage further. The result: degraded attribution data, inflated acquisition costs, and a growing gap between what companies spend and what they can actually measure.
The industry has tried patches — consent management platforms, server-side tagging workarounds — but none addressed the root cause. The browser was never the right place to run tag logic in the first place. Akamai’s Google Tag Gateway (GTG) moves that workload to where it belongs: the edge.
The Guest: Atoosa Rezai, Principal Technical Account Manager at Akamai
Key Takeaways
- Safari’s Intelligent Tracking Prevention caps third-party cookies at 7 days; Firefox’s Enhanced Tracking Protection blocks known trackers by default; Chrome’s Privacy Sandbox is actively phasing out third-party cookies — making client-side tagging structurally unreliable.
- Akamai’s Google Tag Gateway, built in partnership with Google’s Data Strength engineering team, converts third-party Google Ads and Analytics tags into first-party tags served from the customer’s own domain via Akamai’s 350,000+ edge servers.
- Studies show up to a 14% uplift in tag efficacy when switching to first-party tags — at enterprise ad spend levels, that recovery can translate to hundreds of millions of dollars.
- The solution integrates directly into existing Akamai CDN configurations — no new infrastructure required — and is available free of charge to all Akamai customers.
- Privacy compliance is built in: all data passes through the Akamai-controlled edge environment before reaching any third-party server, turning compliance from a reactive obligation into a proactive feature.
***
In this exclusive interview with Swapnil Bhartiya at TFiR, Atoosa Rezai, Principal Technical Account Manager at Akamai, explains how the Google Tag Gateway on Akamai’s edge network fundamentally solves the client-side tagging crisis — restoring first-party data accuracy, improving marketing attribution, and eliminating browser-imposed cookie restrictions for enterprise customers.
The Client-Side Tagging Crisis: Why the Browser Was Always the Wrong Place
For years, the tracking tag bore the blame for slow page loads, privacy concerns, and broken analytics. But Atoosa Rezai argues the tag itself was never the problem — the architecture was. Placing tag logic in the browser meant handing control of critical marketing infrastructure to an environment that businesses have no control over, one that is now actively working against the measurement use case.
Q: Tags have a bad reputation for performance and privacy issues. What are businesses actually losing if they stop using them?
Atoosa Rezai: “Our customers are spending millions and in some instances, billions of dollars per year in digital advertising and tags are essential. It’s not optional. Without tags, businesses lose the visibility that they need to measure their marketing return on investment — understanding their customer journey and optimizing the digital experience is really top of mind. In today’s world, the agentic workflow is really big. People using AI within their infrastructure is big. Our customers are spending millions of dollars creating marketing messages about how their AI infrastructure works. So they need to be able to know: is that message effective or not? They need to be able to track the effectiveness as users come onto their sites, and tags are used specifically for that.”
Q: What made browser-based tag management structurally broken?
Atoosa Rezai: “The browser was never the right place to implement the tag logic. Client-side tagging degrades performance, it exposes data, and it relies on an environment that businesses and marketing teams have no control over. Browsers have to process and prioritize so many different JavaScripts and cookies with very limited processing power. Safari has implemented Intelligent Tracking Prevention — it caps third-party cookies at seven days. Firefox has implemented Enhanced Tracking Protection, which automatically blocks known third-party trackers by default based on a disconnect list. Chrome has implemented Privacy Sandbox, which is actively phasing out third-party cookies. And that doesn’t even mention ad blockers.”
How Google Tag Gateway on Akamai Edge Works
Akamai’s answer is architectural: move tag processing from the browser to the edge. The Google Tag Gateway, developed in direct partnership with Google’s Data Strength engineering team, runs on Akamai’s globally distributed infrastructure — over 350,000 edge servers — that enterprise customers are already using to deliver and secure their web properties. The key shift is domain authority: tags are now served from the customer’s own domain, making them first-party by definition.
Q: Walk us through what actually happens when a visitor lands on a site using Google Tag Gateway.
Atoosa Rezai: “Instead of the browser loading dozens of third-party scripts and making separate network calls, it now sends just a very lightweight request to the nearest Akamai Edge server — that is usually within two or three milliseconds from the end user making the request — and then the Akamai Edge server handles and fans out to Google Analytics, Google Ads, and other measurement platforms. The behavior runs on the infrastructure that the customer is already using for delivering and securing their content. There’s no additional footprint to manage. And because this data stream originates from the customer’s own domain, we’ve moved it from third-party to first-party. Now browsers cannot drop the cookies associated with these tags, because now they’re the first party.”
Q: Is this approach becoming a standard?
Atoosa Rezai: “Yes — this is the de facto way of handling tags moving forward.”
Privacy, Compliance, and First-Party Data Control
Beyond performance, the edge-native approach changes the compliance picture. Because all tag data passes through Akamai’s controlled infrastructure before reaching any third-party server, businesses gain a natural enforcement point for data filtering and governance — without requiring additional tooling or process changes.
Q: How does running tag logic at the edge give customers more control over what flows to third parties?
Atoosa Rezai: “With Google Tag Gateway on the Akamai edge, the customer’s data is passing through an Akamai-controlled environment before it ever reaches a third-party server, and inherently the first line of defense is Akamai security. The Google Tag Gateway turns privacy from a liability into a feature on the Akamai platform — by filtering the data at the edge before it even reaches third parties, businesses gain compliance proactively through this implementation.”
The Business Case: Recovering Lost Marketing ROI
Rezai puts concrete numbers on the problem. With studies showing up to 14% of tag events dropped by browser restrictions, the financial impact at enterprise scale is substantial. A company spending $14 billion annually on marketing, with 60% allocated to digital advertising, stands to lose approximately $1 billion per year in untracked conversions and attribution data — simply because browsers are discarding the cookies that make measurement possible.
Q: What does the 14% uplift in tag efficacy actually mean for enterprise marketing teams?
Atoosa Rezai: “Let’s say you are spending $14 billion per year — there are customers doing that in the new agentic workflow. And let’s say 60% of that traffic is your digital advertising. If you’re losing 14% of that because browsers are dropping it, that’s $1 billion a year. By moving from third-party to first-party, now you can recover that lost visibility and your lost marketing dollars.”
Q: What does the setup look like for an existing Akamai CDN customer using Google Tag Manager?
Atoosa Rezai: “This first-party authority basically restores the data accuracy that marketing teams need by serving these tags from the customer’s own domain. Customers get longer cookie lifespans, much better measurement and fidelity of their tags, and they don’t have to rely on third-party infrastructure from browsers that are actively restricting this behavior. We have enabled it as a feature free of charge to all of our customers. It’s basically reducing total blocking time and consolidating dozens of network requests into a single stream. If marketing teams are interested, I would highly recommend they reach out to their Akamai or Google account teams and ask for the Google Tag Gateway behavior.”
