Ad blockers are hiding 11% of your data, but Google’s newest free solution changes the rules. Google Tag Gateway uses your domain to bypass detection, bridging the gap to full server-side tracking. Here is what you need to know.
Key takeaways
- Google Tag Gateway lets you serve Google tags from your own domain, reducing data loss caused by ad blockers — for free.
- It's easier to implement than server-side tracking but only supports Google tags (GA4, Google Ads).
- If you need cross-platform tracking or cookie lifetime extension, you'll still need a full sGTM setup.
Are you using Google Analytics and Google Ads but still not happy with the quality of your data?
If server-side tracking feels out of reach because of budget or complexity, it’s easy to assume there’s nothing you can do.
Good news: that’s not the case.
Google Tag Gateway is a new solution from Google released in 2025. It’s a response to the growing use of ad blockers and offers a low-cost way to improve data quality.
So what does it actually do?
Google Tag Gateway allows you to deploy Google scripts using your own domain. Google Tag Gateway loads the tags from your domain and sends measurement events to your domain, from where they are then forwarded to Google. This solution is designed for Cloudflare users - including those on the free plan.
Until now, the only way to achieve similar results was to use server-side tracking. Unfortunately, server-side tracking is not free, requires technical knowledge to implement, and involves ongoing monthly server maintenance costs.
Google Tag Gateway can be a great option for anyone without the budget for server-side tracking who still wants better data quality.
Before going further, a quick note on Cloudflare. It’s a content delivery network (CDN) that sits between your website visitors and your hosting server. In this case, it also acts as the middleman that forwards tracking requests to Google.
How Google Tag Gateway works
- A user visits your website where your GTM container is installed.
- GTM doesn’t send data directly to Google Analytics tools. Instead, it sends requests to a subfolder on your own domain, e.g. Yourdomainyourdomain.com/gtm.
- Ad blockers see an internal request to your domain.
- Cloudflare is responsible for forwarding the requests to Google analytics tools.
With this approach, Google reports that the average number of recorded conversions can increase by 11%. However, it’s important to remember that this is not a perfect solution - some ad blockers may still block requests.
Advantages of Google Tag Gateway
- Requests are harder for ad blockers to block, so you can see more data
- No monthly server maintenance costs
- Much easier to implement than server-side tracking
Disadvantages of Google Tag Gateway
- Some ad blockers may still block requests
- It does not extend cookie lifetime - only a full sGTM implementation can do that
- Only Google tags are supported (GA4, Google Ads)
- You must use a content delivery network (CDN)
Who Google Tag Gateway is for
- Anyone who wants to lose less data due to ad blockers and have more reliable analytics
Who Google Tag Gateway is not for
- Those who already have server-side tracking implemented
- Those who need high-quality data not only from Google but also from Meta, TikTok, LinkedIn, etc.
- Websites with many subdomains where changes should not apply to all of them (Cloudflare automatically applies changes across all subdomains, which can be problematic)
Comparing Google Tag Gateway vs. Stape Gateway vs. GTM Server-side
| Feature | Google Tag Gateway | Stape Gateway | GTM Server-side |
|---|---|---|---|
| Configuration | Very simple | Simple | More complex and requires technical knowledge |
| Maintenance costs | None | Moderate | Potentially high |
| Customization | Limited | Limited | Full |
| Support for non-Google tags | No | No | Yes |
| Protection against ad blockers | Moderately high | Very high | Very high |
