.jpg)
If you've noticed your Google Analytics 4 numbers looking a bit lighter than expected, you're not alone. Ad blockers, browser extensions, and privacy features like Safari's Intelligent Tracking Prevention are quietly eating away at your data accuracy.
For Australian businesses running Google Ads and GA4, this means making marketing decisions with incomplete information. Your retargeting campaigns aren't reaching their full potential, your conversion attribution is skewed, and your Google Ads optimisation is working with one hand tied behind its back.
The good news? Google has released a free solution that takes about 10 minutes to set up and can recover up to 11% of your lost tracking signals. It's called Google Tag Gateway. If you're not using server-side Google Tag Manager, this is one of the quickest wins you can implement for your digital marketing stack.
In a standard Google Analytics or Google Ads setup, your website loads tags directly from Google's domains (like googletagmanager.com or google-analytics.com). When an ad blocker or privacy-focused browser extension sees these requests, it blocks them. The result? Lost data and incomplete tracking.
Google Tag Gateway changes how this works. Instead of loading tags from Google's domains, it routes everything through your own first-party domain. Your website loads the Google Tag from yourdomain.com/metrics (or whatever path you choose) instead of from Google's servers.
To ad blockers and browsers, this looks like legitimate first-party traffic from your own website, which means they're significantly less likely to block it. This approach sits between full server-side tagging and standard client-side tracking, offering many of the benefits of the former without the complexity or ongoing costs.
Google's own data shows that advertisers who configured Tag Gateway saw an 11% uplift in measurement signals. That's not a marginal improvement. That's real conversion data you're currently missing.
When your tracking is incomplete, the impact cascades through your entire marketing operation:
Google Ads Performance: Smart Bidding and automated strategies rely on complete conversion data to optimise effectively. Missing 11% of your signals means the algorithms are optimising with gaps in their understanding of what's actually converting.
Attribution Accuracy: When conversions aren't tracked properly, you can't accurately attribute value to different touchpoints in your customer journey. This leads to undervaluing certain campaigns and potentially cutting budget from channels that are actually driving results.
Audience Building: Remarketing lists and similar audiences are built on user behaviour data. Incomplete tracking means smaller, less accurate audiences for your campaigns to target.
Campaign Optimisation: Making strategic decisions about keyword bids, ad creative performance, or budget allocation becomes significantly harder when you're working with incomplete data sets.
The bottom line? Better tracking leads to better optimisation, which leads to lower cost per acquisition and higher return on ad spend.
If your website is already running through Cloudflare's CDN (and there are plenty of good reasons why it should be), implementing Google Tag Gateway is genuinely straightforward.
Cloudflare has a native integration with Google Tag Gateway. The setup process connects Google Tag Manager directly to your Cloudflare account with a few clicks. Once configured, Cloudflare automatically handles the injection of your GTM container through your first-party domain path.
There are no servers to configure, no ongoing hosting costs, and no technical expertise required beyond following a setup wizard. For Cloudflare users, this is about as close to a "set it and forget it" improvement as you'll find in digital marketing.
Many of our clients at Bang Digital already use Cloudflare for its performance and security benefits. Adding Google Tag Gateway on top of that existing infrastructure takes minutes and immediately improves measurement accuracy.
If you've already implemented server-side Google Tag Manager with proper custom loaders and first-party cookie handling, Google Tag Gateway won't add significant value. Your server-side setup is already solving the tracking limitations that Tag Gateway addresses.
However, most businesses haven't made the jump to full server-side tagging yet. Server-side GTM requires technical implementation, ongoing server costs (typically $100+ per month), and ongoing maintenance. For many organisations, that investment hasn't been justified yet.
Google Tag Gateway bridges this gap. It delivers many of the tracking resilience benefits of server-side tagging without the complexity or cost. Think of it as getting 80% of the benefit with 5% of the effort.
The implementation process is refreshingly simple, especially if you're already using Cloudflare. Here's the step-by-step process:
Step 1: Access Google Tag Gateway in GTM
Open your Google Tag Manager account and navigate to the Admin section. Under your container settings, you'll find the Google Tag Gateway option. If it hasn't been set up yet, it will show as "Not set up."
Step 2: Start the Setup Wizard
Click through to begin the configuration process. Google provides a clear explanation of what Tag Gateway does and how it benefits your tracking setup.
Step 3: Configure Your Measurement Path
Google will suggest a measurement path (typically /metrics or similar). This is the subfolder on your domain that will route your analytics requests. Unless you have a specific technical reason to change it or the path conflicts with existing routes on your website, we recommend sticking with Google's suggested path.
Step 4: Connect to Cloudflare
Click the option to sign in to Cloudflare. You'll be prompted to authorise the connection between Google Tag Manager and your Cloudflare account. Click "Allow" to complete this integration.
Step 5: Complete Setup
Click "Complete Setup" and you're done. Cloudflare will now automatically inject your GTM container through your first-party domain whenever it serves your website.
Step 6: Verify the Implementation
To confirm everything is working correctly, visit your website and open the browser's developer tools (right-click anywhere on the page and select "Inspect"). Navigate to the Network tab and search for your measurement path (e.g., /metrics).
Refresh the page and you should see all your GTM, GA4, and Google Ads requests routing through your domain instead of Google's. This confirms that Google Tag Gateway is active and working as intended.
If you've already got a Google Tag Manager container snippet on your website, don't worry about conflicts. The Cloudflare injection recognises and respects your existing GTM setup.
Your existing snippet will continue to function, and Cloudflare ensures that all requests still use the first-party measurement path you've configured in Google Tag Gateway. You get the tracking benefits without needing to modify your existing implementation.
To verify this is working correctly, check the Network tab in your browser's developer tools. You should see the same number of requests as before (no duplicates), but now they're routing through your first-party domain path instead of directly to Google.
Google Tag Gateway isn't limited to GTM users. If you've implemented Google Analytics 4 directly via the gtag snippet in your website code, you can still enable Tag Gateway.
Navigate to your GA4 property and go to Admin > Data Collection and Modification > Data Streams. Select your website data stream, then scroll down to "Configure Tag Settings."
In the configuration popup, open the Admin tab and find Google Tag Gateway. The setup process from here mirrors the GTM workflow we outlined above.
It's important to understand that Google Tag Gateway doesn't introduce new data collection or bypass consent requirements. It works within your existing consent framework.
Whatever consent preferences you've captured through your Consent Management Platform (CMP) or privacy setup, Tag Gateway enforces them. Only approved tags that have user consent will fire. You're not circumventing privacy regulations. You're making your legitimate, consented tracking more resilient against browser restrictions and ad blockers.
This distinction matters for compliance. Tag Gateway is about improving the reliability of data collection you're already entitled to collect, not about sneaking around privacy controls.
For most Australian businesses running Google Ads or GA4 without server-side tagging, the answer is yes.
The implementation is quick (10-15 minutes for Cloudflare users), there's no ongoing cost, and the data accuracy improvement is measurable. An 11% increase in tracked signals can have a meaningful impact on campaign performance and optimisation capabilities.
If you're already using Cloudflare, this is particularly straightforward. The native integration means minimal technical complexity and immediate benefits.
However, if you've already implemented server-side Google Tag Manager with custom domain configuration and proper cookie handling, Tag Gateway probably won't add much value. Your server-side setup is already providing these benefits in a more comprehensive way.
For those interested in the technical implementation, here's what's happening under the hood:
When you enable Google Tag Gateway with Cloudflare, you're creating a proxy path on your domain. Cloudflare's CDN sits between your visitors and your website, so when it serves your HTML, it can inject the GTM container script that points to your first-party measurement path.
When tags fire, measurement requests are sent to your domain (e.g., yourdomain.com/metrics/...) instead of directly to Google's domains. Cloudflare then forwards these requests to Google's services on the backend.
To the user's browser and any ad blockers they're running, this looks like first-party traffic from your website. Since it's not obviously a third-party tracking request to a known analytics domain, it's less likely to be blocked.
The actual data collection and processing still happens through Google's services. Tag Gateway doesn't change what data is collected or how Google processes it. It simply changes the route that data takes from the user's browser to Google's servers.
At Bang Digital, we're implementing Google Tag Gateway for clients where it makes sense as part of their overall measurement strategy. For businesses already on Cloudflare with Google Ads or GA4, it's one of the quickest wins we can deliver for improved data accuracy.
If you're unsure whether Google Tag Gateway is right for your setup, or if you'd like help implementing it alongside other measurement improvements, we're here to help. As Perth's most awarded Google Premier Partner agency, we work with businesses across Australia to build robust, accurate measurement systems that drive better marketing decisions.
Getting your tracking right is fundamental to effective digital marketing. When you can't accurately measure what's working, you can't optimise effectively. Google Tag Gateway is a straightforward way to close some of those measurement gaps without a major technical investment.
Awards aren't everything. But we are pretty proud to be Perth's most awarded Google Premier Partner agency. Over the years we have been recognised by both Telstra and Google in their award categories, which are highly competitive. Here's a few of our PPC advertising accolades we are particularly proud of.
