← All posts

Blog

Ad BlockersROASServer-Side Tracking

Ad Blocker Conversion Tracking: Why Conversions Are Lost and What It Does to Your ROAS

22 November 20265 min readSyncBeacon Team

Ad blocker conversion tracking is a measurement problem before it is a marketing problem. When a visitor runs a blocker, the browser pixel on your store often cannot report the purchase. The sale still happened. The ad platform just does not know it came from your ad.

This post explains how ad blockers cause missing conversions, why that distorts ROAS and automated bidding, which numbers are actually sourced and which are not, how to measure your own gap, and what server-side tracking can and cannot recover. We are deliberately careful with figures here. Many articles on this topic repeat percentages that no one can trace back to a primary source.


Why conversions are lost

A conversion pixel is a script that loads from an ad platform's domain and then sends the purchase back to it. Ad blockers work from filter lists of known advertising and tracking endpoints. If the script or its requests are on a list, the blocker stops them. The shop page loads normally, the shopper buys, and nothing is reported.

Missing conversions have several browser-side causes. Blockers are one of them, and it helps to keep them apart:

CauseWhat happensFixable on the server?
Ad blockersPixel script or its requests are blockedYes, for the purchase
Browser tracking preventionCookies and storage written by scripts expire soonerPartly. See the Safari ITP post.
Declined consentMarketing pixels are not allowed to runNo. A declined visitor stays declined.
Closed tab or off-site paymentShopper never reaches the thank-you pageYes

What the sourced data says

The most useful primary source we could verify is the 2023 eyeo Ad-Filtering Report, the successor to the PageFair Adblock Report, now published through Blockthrough. Here is what it states, and what it does not.

Read those numbers with care. The rates come from anonymised traffic on ad-supported sites, and the detection works by checking whether requests to bait URLs are interrupted. A webshop's audience differs from a publisher's audience. A blocked ad is also not the same as a blocked conversion pixel, since not every blocker rule set targets the same endpoints. The figures show that ad blocking is common. They do not tell you how many of your purchases went unreported.

Sources: 2023 eyeo Ad-Filtering Report (PDF) and the Blockthrough report page. We do not quote a blanket "percent of conversions lost" figure, because we have not found a primary source that supports one for e-commerce purchases.

Three assumptions worth dropping

Ad blockers ROAS impact: the mechanics

ROAS is conversion value divided by ad spend. Ad blockers act on the top of that fraction. When purchases go unreported, the platform sees less value for the same spend, and the reported ROAS drops.

A purely hypothetical example, to show the arithmetic and not a benchmark: say a campaign drives 100 orders worth 50 each, for a spend of 2,500. The true ROAS is 2.0. If the platform only receives 80 of those purchases, it reports a ROAS of 1.6. Nothing about the ads changed.

There is a second effect. Automated bidding learns from the conversions it sees. If it sees only part of the picture, and that part is skewed toward visitors who do not run blockers, it optimises for that audience. That may not match the people who actually buy from you.

Key takeaway: ad blockers do not make your ads worse. They make your reporting and bidding data smaller and biased. The fix is to report the purchase from somewhere a blocker cannot reach, then measure what is left.

Measure your own gap

Do not rely on an industry figure to size your own problem. You can estimate it from your own data in under an hour.

  1. Pick a recent period of at least a few weeks, with stable campaigns.
  2. Export orders from your store. Exclude test orders and cancelled orders.
  3. Export purchases the ad platform reports for the same period, using the same attribution setting.
  4. Run a test purchase in a clean browser and another with an ad blocker enabled. If only the first reaches the platform, you have confirmed the leak on your own pixel.

The remaining difference includes more than blockers. Attribution windows, view-through credit and orders from other channels all widen it. The post on why Meta shows fewer conversions than Shopify walks through separating those causes. For a quick look at which tags your storefront loads, use the free tracking audit.

If the gap turns out to be small, you have your answer and can move on to other work. If it is large, treat that as a measurement project, not a campaign problem: fix the data first, then judge the ads.

What server-side tracking fixes, and what it does not

With server-side tracking, the purchase is sent from your store's order data to the ad platform through a relay, so a blocker in the shopper's browser has nothing to block. SyncBeacon does this for Shopify, WooCommerce and Shopware orders, then forwards to Meta, Google Ads and the other launch destinations.

What it recovers

What it does not recover

Destination detail: Meta Conversions API and Google Ads Enhanced Conversions. If you want the longer argument on how this looks for Google Ads, see our Google Ads conversions post.


Get started

Close your conversion gap today

Connect Meta CAPI, Google Enhanced Conversions, and more - in one setup, no developer required.

Get started

Figures are quoted from the cited report and describe ad-supported websites, not your store. The ROAS example is hypothetical arithmetic. Not legal advice.