One route for all tracking data
Google Analytics, Meta, Google Ads and LinkedIn get their tracking data from Cloudflare instead of straight from your visitors’ browsers.
Web analytics and ad pixels via Cloudflare Zaraz
Server-side tracking that waits for a yes in your cookie banner
I move Google Analytics, Google Ads, the Meta pixel and LinkedIn into Cloudflare Zaraz. If a visitor declines, Google and Meta get nothing, not even an IP address.
By video call. All you need to bring is your website address.
Companies I’ve worked for
The starting point
Every campaign adds another pixel
First Google Analytics, then the Meta pixel, then LinkedIn’s Insight Tag. Often nobody has checked whether your cookie banner holds each one back until someone consents. And even when visitors have consented, some ad blockers stop the request to Google.
I rebuild your tracking in Zaraz, one tool at a time.
Your website no longer loads a single pixel before consent.
Your data protection officer can see in a single list which tool starts when.
Migration
How I migrate your tracking
A custom path
After consent, the tracking data travels through a path on your domain, such as /t. To the browser, the request stays on your website.
Consent comes first
Cloudflare only starts the tools your visitors have agreed to in the cookie banner. I match the banner to your website with a tool I built myself.
Less third-party code
Instead of three scripts from Google, Meta and LinkedIn, the browser loads just one, and it comes from your domain.
How it works
From source code to before-and-after numbers
01
Take stock
I list every tool your site loads and check whether it waits for consent.
02
Put Cloudflare in front
I create the DNS zone at Cloudflare, carry over the email records and plan the switch with your IT team.
03
Move the tools
I set up the tools in Zaraz, each with its own category in the cookie banner, and remove the old scripts.
04
Compare the numbers
We put your web analytics numbers from before and after side by side and work out where any differences come from.
Testimonials
What the teams at Webflow and Sardine say
“We hired Christian recently; he partnered closely with our team to streamline our tag management setup. […] If you're looking for someone for Google Tag Manager/Zaraz architecture/governance and high-performance tracking foundations, I highly recommend him and his services.”
Utkarsh Sengar
CTO at Webflow
Post on LinkedIn“I've had the pleasure of working with Christian twice now on Google Tag Manager implementations, and I'd hire him a third time without hesitation. […] He identified that our consent initialization wasn't working correctly in GTM, caught Meta Pixel firing without consent in our test environment […]”
Taras Melnychenko
Marketing Ops @ Sardine
Recommendation on LinkedIn“Working with Christian was a really great experience and we were able to stay flexible and deliver a new tag management architecture on a tight deadline”
Sierra Lee (Battan)
Engineering Manager at Webflow
Comment on LinkedInFAQ
Questions about moving to Zaraz
What is Cloudflare Zaraz?
Zaraz is Cloudflare’s tag manager: it runs Google Analytics, the Meta pixel and other tools on Cloudflare instead of in the browser. Zaraz is included in every Cloudflare plan and comes with its own cookie banner, where visitors allow tools by category. In my projects, the domain runs through Cloudflare for this. If it’s with another provider today, we move it as part of the project.
Which tools run through Zaraz?
Zaraz comes with ready-made integrations for Google Analytics 4, Google Ads, LinkedIn Insight and the Meta pixel, plus Bing, TikTok, Pinterest, HubSpot and Mixpanel, among others. For Meta, I add an access token for the Conversions API so events reach Meta directly from Cloudflare. I also replace Google Tag Manager in the process: Zaraz can’t speed up the tools inside it or control them through its privacy settings.
Is server-side tracking with Zaraz GDPR compliant?
That depends on the setup: Zaraz on its own doesn’t make any tracking GDPR compliant. In Zaraz, a new tool has no category at first, so it starts without consent. That’s why I check every tool individually before launch. Under § 25 of Germany’s Telecommunications Digital Services Data Protection Act (TDDDG), you need your visitors’ consent before a tool stores or reads anything on their device. Whether your tracking holds up legally is a question for your data protection officer or a law firm.
What changes in Google Analytics after the switch?
Your property and reports stay as they are. The data simply comes through Cloudflare now. Out of the box, Zaraz sends Google Analytics only page views, session starts and first visits. I set up scroll depth, downloads or clicks on external links as custom events. If Google Analytics used to run before consent, you’ll count fewer visitors from now on. That’s not a measurement error: the missing visitors are exactly the ones who didn’t consent. If someone takes a few seconds to consent, Zaraz sends the held-back events afterward.
How much does server-side tracking with Zaraz cost?
That depends on your current setup: how many tools need to move, how many custom events you need and whether your domain already runs through Cloudflare. If you ask for one, I’ll send you a written quote after our free 30-minute check. On the Cloudflare side, every account includes one million Zaraz Events per month free of charge, and each additional million costs US$5 (Cloudflare pricing, as of October 2026). A page view or a tracked click, for example, counts as one Zaraz Event.
Free 30-minute check
Does your tracking really wait for consent?
I’ll show you in the free 30-minute check, and then you decide whether we get started.
Book a free 30-minute check
Prefer email? [email protected]