Companies like to talk about optimizing advertising budgets. ROAS, algorithm changes, lowering Customer Acquisition Cost (CAC), and campaign scaling are usually on the agenda. These are important conversations because they are about oxygen: profitable sales.
But there is another conversation that many avoid: what to do when up to several dozen percent of conversion data is lost along the way due to AdBlockers and browser restrictions, such as ITP in Safari. In practice, this topic is just as important as margins or churn, because if advertising systems cannot see what the customer is doing, your campaigns start burning through your budget.
In our work with clients at Casbeg, we often see this moment. A company spends tens of thousands of zlotys on marketing, website traffic grows, but analytics are empty, and Google or Meta algorithms lose their fuel for optimization. For a long time, the default prescription for this was sGTM (server-side Google Tag Manager)—a powerful but expensive and demanding tool. Recently, however, Google released an alternative: Google Tag Gateway (GTG).
What exactly does “first-party routing” mean and how does GTG work?
Usually, a user’s browser sends behavioral data directly to external servers (e.g., google.com/gtm.js). Privacy protection systems and blocking plugins treat this as requests to third parties and mercilessly cut off communication.
Google Tag Gateway allows you to solve this problem at its root. The tool makes tracking codes load from your own domain, most often using the so-called Same Origin (e.g., yourcompany.com/scripts). The browser interprets such traffic as internal (first-party), necessary for the website to function, and allows it to flow freely.
Unlike full sGTM, Gateway does not process data on the server and does not require complex infrastructure. It is simply an intelligent “tunnel”—often implemented using a CDN (e.g., Cloudflare)—that masks requests as internal and then, without deep interference with tag logic, forwards them to the Google ecosystem. The entire burden of enforcing rules remains in the client’s browser.
GTG or sGTM – where lies the difference?
In mature companies, technological decisions are based on the analysis of costs, implementation time, and data protection, rather than chasing novelties. The choice between these two solutions is like deciding whether you just need a detour on a blocked road or your own highway network.
- Complexity and implementation time: GTG can be implemented in a few hours, relying on the already existing tag ecosystem. You do not need to map variables from scratch. Server-side GTM often means weeks of work for developers and analysts.
- Data recovery: Google Tag Gateway is able to “rescue” 70-85% of lost signals with minimal effort. In turn, sGTM allows for a recovery rate of 90-95%, but this requires a radical change in the way events are processed.
- Privacy control: If you operate in a regulated industry (e.g., finance, medicine) and must absolutely anonymize data and remove PII (personally identifiable information) before sending it to external corporations, sGTM gives you a full server environment to do so. GTG simply passes the data forward, so it does not protect you from accidentally leaking a customer’s email to Google or Facebook.
- Costs: A tag gateway using a CDN is a very cheap solution (or even free if you already have a package with your provider). Full sGTM means having to pay for cloud machines (most often Google Cloud Platform), the maintenance of which grows in proportion to the traffic generated on the website.
When to choose which solution?
If your marketing costs oscillate around several to tens of thousands of zlotys, and your only goal is to recover lost data for algorithms without building a separate IT department—GTG is the obvious choice. This is a classic low-hanging fruit scenario where the payback period on the investment is measured in days.
If, on the other hand, you run a massive e-commerce business, work with dozens of affiliate partners, integrate advanced CRM data with advertising pixels, and your lawyers tremble at the thought of GDPR violations—sGTM is the only right path. In that case, the additional cost of servers is a fraction of the risks and lost margins.
Summary
When campaign numbers stop adding up and advertising systems lack conversions, organizations often panic. Instead of looking for holes in the marketing narrative or cutting budgets to zero, it is worth fixing the “analytical plumbing” first. Google Tag Gateway proves that not every technological problem requires the implementation of a massive system. Switching tracking to first-party routing restores campaign visibility, strengthens optimization algorithms, and protects brand capital from being burned, all without generating enterprise-level burdens. Before you pay the bill for sGTM servers, make sure a simple change in your CDN isn’t enough.
FAQ
Does Google Tag Gateway completely replace sGTM?
No. GTG works on the routing layer, but it does not process or clean data like a server-side tag manager does. It is a lighter alternative for companies that simply want to bypass basic browser restrictions.
How fast can GTG be implemented?
In most cases (especially when using automated configurations, e.g., in Cloudflare), implementation takes only a few hours of work from an analytics specialist and a network administrator.
Is implementing first-party routing legally compliant (GDPR)?
First-party routing does not exempt you from the obligation to have appropriate user consents (Consent Mode). It only changes the technical method of data transmission, not the legal framework for collecting it. You still have to ask the user for permission to track them for advertising purposes.
Sources: