Ad Blockers, Consent and Cookies | TrueROAS Learn
trueRoas-logotrueRoas-text-logo
Learn

·

5 min read

·

By Rasmus, founder of TrueROAS

Ad Blockers, Consent and Cookies

How much data you lose by region and device.

We launched in Germany and the Meta purchases for Germany were a third of what Sweden showed, at the same spend. Same ads, same creative, same product. The German customers were buying at the same rate. They were also declining cookies at twice the rate and running ad blockers on every desktop in the country.

The one-sentence version

Between consent banners, ad blockers, iOS opt-outs and Safari's cookie cap, a large share of purchases never reach a browser-based pixel. How large depends on where your customers are and what they browse on.

The setup

Your market, your devices

Try it: your market, your customers

How much does the pixel never see?

Where are most customers?

What do they browse on?

Consent declined

35%

Ad blocker

17%

iOS opt-out

39%

Safari cookie cap

11%

70%

About 70 of every 100 purchases never reach a browser pixel

Each loss compounds on the rest. Server-side capture on your own domain recovers the blocker, cookie and most of the iOS loss. Consent declines are the one you should not recover, which is why the survey exists. (Illustrative rates, in line with published opt-in and blocker studies.)

Your German customers are fine. The pixel is not.

The four leaks

What each one is

Consent declined

In the EU and UK, a click on 'reject' means the standard tags do not run. Google may model some of it back; Meta mostly does not. This one is a choice and should be respected.

Ad blocker

The pixel script never loads. No page view, no add to cart, no purchase event. The visit is invisible to the ad platform and to GA4.

iOS opt-out

The click happened inside Instagram; the purchase happened in Safari. Without the identifier, the two never meet.

Safari cookie cap

The click was recorded, but the cookie carrying it expires in 7 days or less. Buy on day 9 and the purchase belongs to nobody.

Why it matters

Losses are not random

The people you lose skew iPhone, European, privacy-aware and often higher income. Your reporting is biased toward the customers who are easiest to track, not the ones who buy most. Meta then optimises toward the easy-to-track ones, because those are the purchases it saw.

We nearly pulled out of Germany. It became our second biggest market once the tracking was fixed and the numbers caught up with reality.

The fix

Move the record off the browser

Store the click on your own domain server-side, receive the order from Shopify server-to-server, join them by session or by customer at checkout, and send the verified event to Meta and Google with real match keys. Blockers and cookie caps cannot touch any of that. Consent still applies, and the post-purchase survey covers the people who chose not to be tracked. That is the TrueROAS setup on every plan.

Honest footnote

Where it barely matters

A US-only store with an Android-heavy audience and same-day purchases loses far less. Run the calculator above with your own mix before you decide it is urgent.

Questions people actually ask

Straight answers

No, and it should not. It respects the store's consent settings. What it avoids is the accidental loss: cookies deleted by Safari, scripts blocked, sessions dropped at checkout. Those are not consent decisions, they are technical failures.

Google's way of running its tags in a reduced mode when someone declines. Conversions from declined users are modeled if you have enough volume. Below the threshold they vanish.

Roughly a quarter to a third of desktop users in Europe and North America, lower on mobile. They stop the pixel script from loading, so the platform never hears about the visit.

Because it is the default browser on every iPhone and Mac. Its Intelligent Tracking Prevention caps first-party cookies set by scripts at 7 days, sometimes 24 hours, so a click on Monday cannot be tied to a purchase next Tuesday.

See your own numbers, verified against your orders.

Free under $10k/month in revenue. 14-day trial above that. Nothing changes in your ad accounts. You will know within a week which platform has been telling stories.

★★★★★4.7Shopify App Store · 82 reviews★★★★★5.0Trustpilot · 12 reviews
Start Free Trial

14-day free trial · Setup in 3 minutes · Nothing changes in your ad accounts · Cancel anytime

Rasmus Arvidsson, founder of TrueROAS

"I built this because I was making $50k-a-month decisions on numbers I knew were wrong. If TrueROAS does not show you something Meta or Google got wrong in the first two weeks, tell me and I will help you cancel."

Rasmus Arvidsson

Founder, TrueROAS. Answers support himself.

Keep going

Next up