Using Conversion Bridge with Google Tag Gateway

Google tag gateway for advertisers (GTG) is Google's first-party tagging product. Instead of loading the Google tag from googletagmanager.com and sending conversion data straight to Google's servers, GTG routes both the tag itself and the measurement requests through a first-party path on your own domain. That path forwards the traffic on to Google in the background.

The benefits are real if your visitors run ad blockers. A meaningful share of conversion tracking gets blocked before it ever reaches Google, and GTG makes those requests look like they're going to your own domain, which a lot of blockers won't touch. You also get a small performance gain from fewer cross-origin connections.

GTG is delivered through CDN partners. Cloudflare is the main one. Akamai joined as a second partner in 2025.

If you're considering Google tag gateway alongside Conversion Bridge, here's what to know.

Does Conversion Bridge work with Google Tag Gateway?

Yes, when you use a partner-managed setup (Cloudflare or Akamai). No changes are needed in Conversion Bridge.

Here's why it works: in partner-managed mode, the CDN automatically rewrites your site's HTML at the edge. Conversion Bridge enqueues gtag.js from googletagmanager.com just like always, and the CDN swaps that URL for the first-party measurement path before the response reaches the browser. From your WordPress site's perspective, nothing changes. From the browser's perspective, everything loads from your own domain.

Conversion Bridge fires Google Analytics 4 and Google Ads events the same way it always has, using the standard gtag() calls. Enhanced Conversions on integrations like WS Form keep working because the customer data handoff happens through the same gtag interface, and consent mode signals propagate normally.

The one case where Conversion Bridge can't currently help is the manual / self-service setup, where GTG is installed without a partner CDN and the site code has to use a hardcoded first-party gtag URL. Conversion Bridge enqueues gtag.js from googletagmanager.com and doesn't yet expose a way to override that URL, so manual GTG setup isn't supported out of the box. If that's your situation, get in touch and I'll look into adding a filter.

What Google Tag Gateway Changes (and What It Doesn't)

What stays the same:

• How Conversion Bridge fires events
• Enhanced Conversions and the customer data (email, phone, name) handoff to Google Ads
• Consent mode signals from your cookie banner
• All of your existing Conversion Bridge settings

What changes:

• The Google tag script and measurement requests load from a first-party path on your own domain instead of Google's domains
• Ad blockers that rely on blocking third-party Google domains can no longer block those requests
• A small performance improvement from fewer cross-origin connections

How to Enable Google Tag Gateway

Setup happens in Google Ads and on your CDN partner's side, not in Conversion Bridge. The high-level flow:

1. Sign in to Google Ads, open your Google tag, and start the Google tag gateway setup
2. Choose your partner (currently Cloudflare or Akamai)
3. Connect your CDN account and pick a domain to enable GTG on
4. Choose a measurement path on your domain (the default is fine for most sites)
5. Let the partner finish provisioning the gateway

For the current step-by-step, Google publishes setup docs at developers.google.com/tag-platform/tag-manager/gateway and Cloudflare publishes its own at developers.cloudflare.com/google-tag-gateway. Both stay current as the product evolves.

If you stick with the partner-managed setup, no changes are needed in your WordPress site or in Conversion Bridge.

Verifying It Works with Conversion Bridge

After you turn on Google tag gateway, test that your tracking still flows correctly:

1. Submit a test conversion on your site, like a form submission or a test purchase
2. Open your browser's developer tools and confirm the gtag script and the measurement requests are loading from your own domain (not googletagmanager.com)
3. Wait a few minutes, then check Google Ads or GA4 to confirm the event arrived
4. For Enhanced Conversions, verify in Google Ads that the customer data parameters are still being received
5. If you want a record of every event Conversion Bridge is firing, enable logging at Settings → Conversion Bridge → Tools

The conversion data should arrive in your Google reporting just like before. If it doesn't, the issue is on the GTG configuration side, not in Conversion Bridge.

What About Cloudflare Zaraz?

Zaraz is a different Cloudflare product that comes up in similar conversations. Unlike GTG, it isn't a transparent rewrite. It replaces the Google tag with its own managed component, and it overlaps with what Conversion Bridge does. If you're weighing both options, the Cloudflare Zaraz doc explains why Conversion Bridge and Zaraz don't combine well.

For most people asking about first-party tracking, Google tag gateway through a CDN partner is the cleaner path. It improves your tracking resilience without requiring changes to Conversion Bridge.