How does the tracking loss calculator work?

It combines three independent signal-loss sources, iOS Safari with ITP, ad-blocker share, and consent decline, and estimates the true revenue your ad platforms are missing because their client-side pixels never fire. The recovery figure assumes a clean server-side GTM plus Meta CAPI plus Google Enhanced Conversions setup, which typically restores 60 to 80 percent of lost signal. We use 65 percent as a conservative default.

Is this tracking loss calculator free?

Yes. No sign-up, no email gate, no paywall. Enter your spend, reported ROAS, and traffic-mix numbers and the calculator returns the lost-signal percentage, hidden monthly revenue, and recoverable revenue instantly.

How much revenue am I losing from iOS 14 and ITP?

For a typical DTC store with 55 percent iOS traffic, iOS ITP alone drops around 22 percent of client-side purchase events after seven days. Combined with a 15 percent ad-blocker share and 20 percent consent decline, most stores lose 40 to 55 percent of pixel-attributed conversions. The calculator gives you the exact number for your traffic mix.

Does server-side GTM and Meta CAPI actually recover lost conversions?

Yes. A clean sGTM plus Meta CAPI plus Google Enhanced Conversions build typically restores 60 to 80 percent of the signal lost to iOS, ad-blockers, and consent decline. The recovery is highest for logged-in checkout flows where you can send hashed email and phone as advanced matching parameters.

What are realistic input ranges?

For most DTC and B2B SaaS traffic in 2026: iOS share sits between 40 and 65 percent depending on geography, ad-blocker share is 10 to 25 percent on desktop-heavy audiences, consent decline is 15 to 35 percent under GDPR and 5 to 15 percent outside the EU. Check your GA4 device and browser reports and your CMP dashboard for exact numbers.

Is 65 percent recovery a promise?

No. It is a planning figure grounded in what a well-built server-side stack recovers on average. Real recovery depends on how much of your checkout is server-authoritative, whether you can send hashed emails and phone numbers with events, how tight your dedup keys are, and how strictly your CMP is configured. An audit gives you the number for your specific stack.

Why is my true ROAS different from platform ROAS?

Platform ROAS reports what the pixel saw. If the pixel fires on 70 percent of purchases, platform ROAS understates true return by roughly 43 percent. The optimisation cost is worse than the reporting cost. Meta and Google train on the events they receive, so a broken pixel produces worse targeting, not just worse dashboards.

What does the payback figure assume?

It assumes an all-in sGTM cost of about 300 USD per month (managed host plus amortised build in year one) and a 20 percent net contribution margin on recovered revenue. Adjust downward if you run your own Google Cloud Run and upward if the recovered revenue carries lower margin.

Does this work for Shopify, WooCommerce, or headless stores?

Yes. The model is platform-agnostic. Shopify stores usually recover more signal because the checkout is server-authoritative, so a sGTM plus CAPI build can reach the upper end of the 60 to 80 percent recovery band. Headless and custom checkouts vary more; the calculator's 65 percent default is a safe planning midpoint.

Free tool

Tracking Loss Calculator

Model the revenue your ad platforms cannot see because iOS, ad-blockers and consent decline break the pixel. Then see what a clean server-side GTM plus CAPI setup recovers.

Your inputs

Monthly ad spend

Blended Meta + Google + LinkedInReported blended ROAS

What your platform dashboards sayiOS / Safari traffic share

GA4 → Tech → BrowserAd-blocker traffic share

10 to 25% typical for B2B; 5 to 12% DTCConsent decline rate

From your CMP dashboard

Signal lost

46.0%

Share of conversions your pixels never see

Hidden monthly revenue

$21,317

True revenue est. $46,317

Recoverable with sGTM + CAPI

$13,856

Recovered blended ROAS ~ 3.89x

Payback on a server-side build

At a blended sGTM cost of about $300 per month (managed host + amortised year-one build) and a 20% net contribution on recovered revenue, this stack pays for itself in Under 1 month. Full pricing breakdown by request volume in the sGTM cost guide.

Want the number for your actual stack?

The calculator uses conservative industry defaults. A two-day tracking audit gives you the real loss figure, pulled from your GA4, CMP, and platform reports, plus the fix list ranked by revenue impact.

Book the tracking audit See tracking services Meta CAPI setup

How the model works

Each source of signal loss is applied to its own share of traffic and then combined as independent events so overlapping causes do not double-count. iOS Safari with ITP loses roughly 40% of client-side conversions after seven days. Ad-blockers strip about 90% of pixel requests on the sessions they touch. Consent decline strips 100% of client tags on those sessions.

True revenue is back-solved from your reported revenue and the combined loss share. The recovery figure assumes a clean server-side GTM plus Meta CAPI plus Google Enhanced Conversions build, which typically closes 60 to 80% of the gap. I use 65% as a planning default.

This is a planning tool, not an audit. Use it to size the opportunity and to decide whether a server-side project earns its place on the roadmap this quarter.

Free pixel loss calculator for Meta Ads and Google Ads

Server-side GTM and Meta CAPI ROI calculator