Using Conversion Bridge with Cloudflare Zaraz

Cloudflare Zaraz is a tag manager that moves third-party scripts to Cloudflare's edge instead of running them in the browser. It comes up in the same conversations as Google tag gateway because both promise server-side benefits, but they're different products that solve different problems.

If you use Conversion Bridge for Google Ads, GA4, or Meta tracking, here's the honest answer on running Zaraz alongside it.

Short Answer

Don't enable Zaraz's GA4, Google Ads, or Meta managed components on a site that uses Conversion Bridge for those platforms. They overlap, and the result is usually either duplicate tracking or broken Enhanced Conversions.

Pick one tool to own each platform. For most Conversion Bridge users, that means letting Conversion Bridge stay in charge of the analytics and ad platforms it already handles.

Why Conversion Bridge and Zaraz Overlap

With Google tag gateway, your gtag() calls keep working the same way. Cloudflare rewrites your site's HTML at the edge to load the Google tag from a first-party path on your domain, and your site code doesn't change. Zaraz works differently. It replaces each platform's tag with its own managed component and expects events to flow through zaraz.track() instead of gtag() or fbq().

That creates two problems for a Conversion Bridge site:

1. Conversion Bridge fires events via gtag() and fbq(). If Zaraz has replaced those tags with its own managed components, the events fire into a context that no longer connects to your Google Ads or Meta account the way you expect.
2. For Enhanced Conversions specifically, Conversion Bridge hands off customer data (email, phone, name) through Google's standard user_data parameter. Zaraz's Google Ads managed component has historically had limited support for that parameter, so even when events do flow through, the customer data piece can silently fall off.

The result is usually one of two things: tracking that looks like it works but loses match quality, or tracking that doesn't flow at all.

Where Zaraz Can Coexist with Conversion Bridge

Zaraz is a legitimate tool, and it does plenty of useful work outside of conversion tracking. If you want to use it for things like:

• Chat widgets (Intercom, Drift, Crisp)
• A/B testingA method of comparing two versions of a webpage, email, or element to see which one performs better based on user behavior or conversion rates. tools
• Other third-party scripts that aren't part of your conversion tracking

That's fine. Just leave the GA4, Google Ads, and Meta managed components in Zaraz disabled, and let Conversion Bridge keep owning those platforms.

If You Want the Server-Side Experience

Most people who ask about Zaraz are really asking for two things: ad-blocker resilience and a small performance gain. Both are available through Google tag gateway when set up through a CDN partner like Cloudflare. It works with Conversion Bridge without any code or settings changes on the WordPress side.

GTG is the cleaner answer for the first-party experience without the conflict.

Verifying Nothing Is Broken

If you've already enabled Zaraz with the GA4, Google Ads, or Meta managed components active, here's how to check whether your Conversion Bridge tracking is still flowing:

1. Submit a test conversion on your site
2. Check the Network panel in your browser's developer tools for requests going out to google-analytics.com, googleadservices.com, or facebook.com
3. Wait a few minutes, then confirm the event arrived in Google Ads, GA4, or Meta Events Manager
4. For Enhanced Conversions, verify in Google Ads that the customer data parameters are still being received
5. Enable logging at Settings → Conversion Bridge → Tools to see a record of every event Conversion Bridge fires

If conversion events aren't reaching your platforms, or your Enhanced Conversions match rate has dropped after enabling Zaraz, disable Zaraz's overlapping managed components and let Conversion Bridge handle those platforms instead.