Adblock Is Killing Your Tracking Data — Here's the Fix

You have spent weeks tuning your GA4 reports. Your Google Ads conversion tracking is finally working. Your Meta Pixel is firing correctly. And then you discover that somewhere between a quarter and nearly half of your visitors never fired a single one of those tags — because their adblocker killed them on page load. This is not a hypothetical edge case. It is happening right now, on your site, and it has been happening for years. The question is not whether you are losing data. The question is how much, and what you are going to do about it.

How Much Data Are You Actually Losing?

The numbers vary by industry, audience, and geography, but the pattern is consistent: adblocker adoption keeps climbing. In the UK, between 27% and 42% of desktop users run some form of adblocker, depending on whose survey you use. For mobile, the number is lower — around 10-15% — but rising fast now that Safari on iOS supports content-blocking extensions. Tech-savvy audiences (developers, marketers, IT professionals) run adblockers at 50% or higher. Gaming and tech-news audiences can hit 60%.

What does that mean for your numbers? If 30% of your desktop traffic is adblocked and 60% of your traffic is desktop, you are missing roughly 18% of your total audience. Your GA4 reports show 10,000 monthly users — the real number is closer to 12,000. Your Google Ads reports show 50 conversions — the real number is closer to 60. Your Meta Pixel audience size is 18% smaller than reality, which means your lookalike audiences and retargeting pools are missing a fifth of the people who actually visited your site.

Worse: adblock users are not a random sample. They skew younger, more affluent, and more tech-literate — exactly the audience most businesses want to reach and measure. By ignoring adblockers, you are systematically undercounting your most valuable visitors.

What Adblockers Actually Block

Adblockers work by maintaining blocklists of known tracking domains. When your page loads, the adblocker checks every network request against its blocklist. If the request is going to google-analytics.com, googletagmanager.com, facebook.com/tr, doubleclick.net, or any of thousands of other tracking endpoints, the request is dropped. The tag never fires. The event never reaches the vendor. The user visited your site, read your content, maybe even bought something — and your analytics have no record of any of it.

That is the core of the problem. Your tracking scripts load from third-party domains — google-analytics.com, googletagmanager.com, connect.facebook.net — and adblockers block third-party domains by default. The fix is to stop sending data to third-party domains and start sending it through your own.

The Fix: Server-Side Tracking via Your Own Domain

Server-side tracking changes the architecture of how data flows from your site to your analytics and advertising platforms. Instead of the browser sending data directly to Google, Meta, and everyone else, it sends data to a server you control — running on your own domain, on your own infrastructure. That server receives the event, processes it, and then forwards it to Google, Meta, and your other vendors. From the browser's perspective, the only network request is to your own domain. The adblocker sees a request to data.yoursite.co.uk — which is not on any blocklist — and lets it through.

This is not a hack or a workaround. Google built server-side GTM specifically for this purpose, and it is fully compliant with GDPR and the ICO's expectations — because the server-side container gives you full control over what data leaves your infrastructure and where it goes. You can strip PII before it reaches Google. You can prevent Meta from receiving data for users who did not consent. You are not bypassing consent; you are building a consent-respecting data pipeline that adblockers happen to trust because it uses your domain.

How It Works Technically

1. You deploy a server-side GTM container on a subdomain of your main site — typically ss.yoursite.co.uk or data.yoursite.co.uk. This runs on Google Cloud Run or any Docker-capable hosting. The monthly cost is roughly £40-60 for a typical small-to-medium UK business.
2. Your existing GTM web container sends events to your server-side container instead of directly to Google Analytics. The web container's GA4 tag is reconfigured to point at your server-side endpoint — a one-line change in the tag configuration.
3. The server-side container receives the event, enriches it (adds geolocation, user-agent parsing, bot filtering), applies consent checks, strips any PII, and then forwards clean, compliant data to GA4, Google Ads, Meta, and any other platforms you use.

The result: your tracking data flows through a first-party endpoint that adblockers do not block. Your data quality improves immediately — for the exact same visitors, the exact same pages, the exact same setup. The only thing that changed is the endpoint the browser talks to.

What You Get Back

When you switch to server-side tracking, the improvement shows up in three places:

• GA4 event volume increases by 15-30%: Every adblocked visitor who previously generated zero events now generates events. Your reports become more accurate. Your audience sizes grow.
• Google Ads conversion count increases by 10-25%: Adblocked users who converted were invisible to Google Ads. After the switch, those conversions appear — which means your campaign ROAS numbers become more accurate and Google's bidding algorithms get a fuller signal.
• Meta Pixel audience sizes increase by 15-25%: Your retargeting pools grow. Your lookalike audiences are built from a more complete dataset. Your Meta ad performance improves because the platform has more signal to optimise against.

For a business spending £3,000/month on Google Ads with a 3x ROAS, recovering 15% of lost conversion data means an extra £1,350 in attributable revenue per month — just from measurement accuracy, not from changing a single ad or landing page.

UK-Specific Considerations

UK Data Residency

Post-Brexit, some UK businesses are required to keep personal data within the UK. Server-side GTM on Google Cloud lets you specify a European region for your Cloud Run instance — London (europe-west2) is available and keeps your data within the UK. If your business handles sensitive data or works with public-sector clients, UK data residency is a selling point of the server-side architecture.

ICO Compliance

A server-side container does not bypass consent — it gives you better tools to enforce it. In your server-side GTM container, you can build consent checks that prevent any data from being forwarded to Google or Meta unless the user has explicitly granted consent in your CMP. This is more robust than the client-side approach, where a misconfigured tag can fire before the consent check runs. The ICO has not issued specific guidance on server-side tracking, but the principle is well established: control over personal data is the goal, and server-side containers give you more of it, not less.

Safari ITP and Intelligent Tracking Prevention

Apple's Safari browser uses Intelligent Tracking Prevention (ITP) to limit third-party cookies and cap the lifetime of first-party cookies set via JavaScript. Safari market share in the UK is higher than the global average — around 35-40% of mobile traffic. ITP caps client-side GA4 cookies at 7 days, which inflates your new-user count and breaks attribution for returning visitors. Server-side tracking solves this too: the server-side container sets cookies via HTTP headers (not JavaScript), which ITP treats as first-party cookies with full lifetime. Your user attribution becomes significantly more accurate on Safari.

Is It Worth the Investment?

Server-side GTM costs roughly £40-60 per month for hosting plus the one-time setup effort — typically 1-2 days of configuration for a competent developer or agency. For a UK business spending any money at all on digital marketing, the ROI is almost immediate. The data recovery alone — the 15-30% uplift in measurable events and conversions — pays for the hosting in the first week. The improved attribution, the Safari ITP fix, the consent enforcement, and the cleaner data architecture are all free bonuses on top of that.

At North Digital, we have moved over a dozen UK businesses to server-side tracking. None have gone back. The data quality improvement is visible the day you switch, and it compounds every month as your historical data becomes more reliable.

Ready to Stop Losing Data?

North Digital handles the full server-side GTM migration — from subdomain setup and container deployment to tag reconfiguration, consent integration, and your first week of monitoring. The typical migration takes three working days and your existing tracking continues to work throughout — there is no downtime and no data gap. Get in touch and we will have your server-side tracking live by this time next week.