Do Ad Blockers Block Google Ads Conversion Tracking?
Yes — and this is the answer most Google Ads guides skip. Ad blockers do not just block display ads. They block the tracking scripts that fire when a conversion happens: the Google Ads conversion linker, the Google Analytics 4 measurement tag, the GTM container itself, and every tag inside it.
When a user with uBlock Origin or AdBlock Plus completes a purchase, the thank-you page loads — but the conversion tag never fires. The purchase hits your backend and shows up in your order management system. It does not appear in Google Ads. Smart Bidding never learns from it. Your ROAS calculation excludes it.
This is not a bug. It is the intended behaviour of ad blocking software. The block lists maintained by the major ad blockers include Google Tag Manager, Google Analytics, and the Google Ads global site tag as explicit targets.
What Ad Blockers Actually Block
Ad blockers operate via filter lists — maintained sets of rules that match specific domain requests and script patterns. The major lists (EasyList, uBlock Origin's filter lists, AdGuard Base Filter) explicitly include the following:
Google Tag Manager
googletagmanager.com/gtm.js — the container script itself. Any tag inside GTM is also blocked.
Google Analytics 4
google-analytics.com and analytics.google.com — GA4 measurement tag requests are blocked.
Google Ads Conversion Linker
googleadservices.com — the click ID and conversion event both fail to send.
Meta Pixel
connect.facebook.net — the Facebook/Instagram pixel script is a primary target on most filter lists.
TikTok Pixel
analytics.tiktok.com — the TikTok Events pixel is blocked by most major lists.
The block does not produce an error in your Google Ads interface. The conversion simply does not appear. There is no warning, no gap indicator, no "X conversions may be missing" notice. The missing data is invisible by design.
The Scale
~30%
of global desktop users actively use an ad blocker
~12%
of purchase events blocked in a typical Malaysian e-commerce setup
~8%
of mobile users in MY have browser-level ad blocking enabled
Global ad blocker usage: PageFair / Statista global estimates. Malaysian mobile figure: lower than desktop globally but growing with mobile browser adoption of built-in blocking (Brave, Samsung Internet, Firefox Mobile).
What This Actually Costs You
The revenue impact is not just the 12% of conversions missing from your reports. The secondary effect — the one that compounds over months — is what it does to Smart Bidding.
Google Ads Smart Bidding (Target ROAS, Target CPA, Maximise Conversions) learns from your conversion history. It builds audience models — which users, at which times, from which keywords, convert at what rate. If 12% of your real conversions are invisible to this system, the model is systematically biased.
Specifically: users who have ad blockers installed tend to be more technically sophisticated, higher-income, and more privacy-conscious. They are often exactly the segment that converts at higher rates. When these conversions are invisible, Smart Bidding under-bids for these users and over-bids for lower-converting segments — because the data says so.
A simplified example:
You run RM 50,000/month in Google Ads. Your actual ROAS is 4.0x — but 12% of conversions are invisible. Google Ads sees a ROAS of ~3.5x. Smart Bidding caps your bids to hit the 3.5x target, leaving the 4.0x potential unreached. The gap compounds: as Smart Bidding learns the wrong model, it progressively misallocates budget away from your highest-converting audiences.
Why Malaysian Brands Are Particularly Exposed
Ad blocker impact in Malaysia is compounded by two local factors that global guides do not cover:
1. Mobile-first traffic with built-in blocking
A growing proportion of Malaysian mobile users access the web through Brave browser, Samsung Internet (which has ad blocking built into its Labs settings), and Firefox Mobile with Enhanced Tracking Protection. These block GTM and GA4 tags at the browser level — no extension required. Unlike desktop Chrome users who must actively install uBlock Origin, these users are blocked by default.
2. PDPA consent timing compounding the problem
Malaysia's Personal Data Protection Act creates a consent layer challenge: tags that fire before a user accepts your cookie banner drop events in a compliant implementation. Combine a user who declined consent with a user who also has an ad blocker — and your conversion signal loss compounds beyond any single source alone.
Why You Cannot Fix This With Client-Side GTM
The common workaround attempt — renaming your GTM container, proxying tag requests through a custom domain — provides marginal and temporary improvement. Ad blocker filter lists are maintained by large communities. A custom domain proxy gets identified and added to the filter list within days to weeks of widespread deployment.
The fundamental problem is architectural: client-side tags fire from the user's browser, where ad blockers have complete interception capability. No amount of obfuscation changes this — the block happens at the network request level, before the tag has any ability to reach Google's servers.
The Fix: Server-Side Tracking
Server-Side GTM (sGTM) moves tag firing from the user's browser to a server container you control — deployed on Google Cloud Platform under your own domain. When a purchase happens, the event goes from your site to your GCP container first. Your container then forwards the conversion signal to Google Ads and GA4.
Ad blockers cannot intercept a server-to-server request. The traffic never passes through the user's browser after the initial event. The block list has nothing to target. This is why server-side tracking is not a workaround — it is a structural fix to a structural problem.
Conversion signals that would be blocked by uBlock Origin reach Google Ads
Smart Bidding receives the complete conversion dataset — including high-value ad-blocker users
ROAS reporting reflects actual performance, not browser-filtered performance
The fix is permanent — server-side requests are not on any ad blocker filter list
Across TRAKK deployments in Malaysia and SEA, the shift from client-side to server-side tracking consistently recovers 10–15% of conversion events that were being silently dropped — on top of the signal recovery from ITP and consent timing fixes.
Key Takeaways
Ad blockers explicitly target GTM, GA4, and Google Ads tags — this is intentional, not incidental.
An estimated 12% of purchase events are silently dropped in a standard Malaysian e-commerce setup.
The secondary damage — Smart Bidding learning the wrong audience model — compounds over months.
Client-side workarounds (domain proxying, tag renaming) are temporary and unreliable.
Server-side GTM is the only structural solution — it moves tag firing outside the browser entirely.