Feature 03 — Ad-Blocker Proof

One in three users
is invisible to your pixel.

Ad blocker usage sits around 32% on desktop in the US — higher in tech, finance, and legal verticals. Every one of those users is a blind spot in your conversion data. They click your ad, land on your page, fill out your form — and nothing fires. As far as Google knows, it never happened.

See It in Action → View Live Dashboard
32%
Desktop ad blocker usage in the US — higher in B2B and professional verticals
0%
Impact on HashVex — server-side capture is immune to browser-based blocking
100%
Of landing page visits captured regardless of browser extensions or ITP settings

Why pixels fail

Google's gtag and Meta's pixel are JavaScript files loaded in the browser. Ad blockers operate at the browser level — they see these scripts and block them before they execute. ITP (Intelligent Tracking Prevention) in Safari further limits cookie-based tracking to 7 days. These aren't edge cases. They're the default behavior for a significant portion of your audience.

Why server-side wins

HashVex captures the click ID from the URL the moment a user lands on your page — on the server, not in the browser. No JavaScript runs at the click stage. No cookies are read. The data exists in your server's request log before the page even finishes loading. An ad blocker cannot interfere with an HTTP request your server is already handling.

How the capture works

01

User clicks your ad

Google, Meta, or LinkedIn appends a click ID to the URL. For Google: ?gclid=ABC123. This happens on the ad platform's side — before the user's browser is involved.

02

Server receives the request

Your server receives the HTTP GET request with the click ID in the URL query string. HashVex's endpoint reads it instantly. No JavaScript. No cookies. No browser involvement whatsoever.

03

Click context stored

The click timestamp and platform ID are stored server-side. When the user submits your form, the conversion proof is generated against this stored context — regardless of what browser extensions they're running.

04

Conversion verified and recorded

The ZK proof is generated, verified, and written to your dashboard. The ad blocker user's conversion is counted just like any other. The gap between your actual leads and your reported conversions gets smaller.

The business case

If you're spending $20,000/month on paid search and ad blockers are hiding 30% of your conversions, you're making budget decisions based on data that's 30% incomplete. That means underfunding campaigns that are actually working, because the attribution data doesn't reflect reality. Server-side capture is not a technical nicety — it's a budget accuracy issue.

Count every
conversion.

The leads are real. The conversions are happening. HashVex makes sure they're counted — even when a browser extension is trying to make sure they're not.