Category: Industry insight | Reading time: 4 min
Ad blockers get discussed as a nuisance. They’re actually a structural problem for digital marketing measurement – and the numbers are more confronting than the industry tends to acknowledge.
How many people are using ad blockers?
Global ad blocker usage has been climbing steadily. Depending on the market and device type, estimates consistently show that 25–40% of desktop users and a growing share of mobile users browse with some form of content blocking enabled. In younger demographics and among technical audiences, that figure is often higher.
Beyond traditional ad blockers like uBlock Origin, a significant amount of blocking now happens at the browser level. Safari’s Intelligent Tracking Prevention (ITP) and Firefox’s Enhanced Tracking Protection (ETP) are built-in by default and affect all users of those browsers – whether they’ve installed anything extra or not.
Combined, these browser populations represent a significant portion of web traffic. In some industries – tech, finance, media – the impact is even more pronounced because these audiences skew heavily toward privacy-conscious users.
What specifically gets blocked?
It’s worth being precise about what blocking actually intercepts.
Standard ad blockers target tracking pixels and analytics scripts based on known domain lists. When a tracking pixel for Meta or Google Analytics is included on a page, ad blockers identify it by its source domain and prevent it from loading. The event never fires. The platform never receives the signal. The conversion goes uncounted.
Cookie restrictions work differently. Safari’s ITP limits how long first-party cookies can persist when set by JavaScript (as opposed to server-set cookies) – down to 7 days. For any customer with a purchase or conversion journey longer than a week, attribution breaks down. The original click that drove them to your site gets wiped from their cookie before they convert.
iOS privacy features add another layer. Since Apple’s App Tracking Transparency rollout, the identifier for advertisers (IDFA) that Meta and others relied on for audience matching is effectively unavailable for most users. Combined with browser restrictions, iOS attribution has become significantly more difficult.
What this means for ad platform optimization
This is the part that’s most underappreciated.
Modern ad platforms – Google Ads Smart Bidding, Meta Advantage+ and their equivalents – are machine learning systems. They require conversion signal to operate effectively. When you set a target CPA or target ROAS, the algorithm is continuously learning from every conversion that fires, adjusting bids in real time based on that feedback.
If 30% of your conversions are being silently lost to ad blockers and browser restrictions, the algorithm is making decisions based on an incomplete dataset. It’s not a passive problem – the miscounting actively degrades bidding performance. Campaigns that would perform well with accurate data underperform because the algorithm doesn’t have the signal it needs to bid aggressively on the right users.
Why the problem has grown
A few years ago, the scale of data loss from ad blockers was meaningful but manageable. Ad blockers were mostly a power-user behaviour and most ad platforms had enough signal to optimize effectively.
The landscape has shifted. Ad blocker adoption has grown YoY. Browser manufacturers – Apple, Mozilla, even Google to some extent – have embedded increasingly aggressive tracking protections into their default browser behaviour. Regulatory pressure under GDPR, CCPA and similar frameworks has increased consent friction across the board.
The direction of travel is clear: client-side tracking will become progressively less reliable. The question for businesses isn’t whether to adapt – it’s when.
Server-side tracking as the structural fix
Server-side tracking addresses the ad blocker problem at the infrastructure level, not the symptom level. By moving event collection off the browser and onto your own server, tracking bypasses the browser-level interception points entirely. Ad blockers can’t block a server-to-server API call. Browser cookie restrictions don’t apply to server-set cookies.
The result is more complete data – consistently, not just occasionally.
Tiide is built to make that transition as straightforward as possible. Setup takes minutes and the data improvement is visible immediately.
