Hunor.digital
← All writing
Analytics honesty · GA4

Is 100% data accuracy possible? What "close enough" means

No, and anyone promising it is selling something. What accuracy is actually achievable, which decisions each level supports, and how to know your own error margin.

Lázár HunorDigital Fixer
The short answer

No analytics setup reaches 100% accuracy: ad blockers, declined consent, browser privacy features, and plain implementation drift guarantee gaps. Well-maintained tracking gets you into decision-grade territory, where trends and comparisons hold. The goal is a known, stable error margin, not a perfect count, and any tool promising perfection is lying.

There is a sentence I refuse to put on my own website, even though it would convert: "we guarantee 100% data accuracy." I refuse it because it is impossible, everyone technical knows it is impossible, and an industry that keeps saying it anyway is the reason clients arrive at my door suspicious of everything, including me.

So here is the honest version of the accuracy conversation, the one worth having before any tool decision or agency contract.

Why 100% is structurally impossible

Web analytics runs on a script in a browser you do not control, on a network you do not control, governed by a consent choice you do not make. Each layer takes a bite:

Multiply the layers and a flawless count of humans is off the table permanently. Any vendor pitch built on restoring it (several "cookieless, 100% accurate" products lean this way) deserves the follow-up question: measured against what, exactly? To claim 100%, you would need a perfect reference count, and if a perfect reference count existed you would not need the product.

What accuracy is actually achievable

Decision-grade accuracy: a setup where the numbers are consistent with themselves over time, the error is roughly stable, and its size is known. That is genuinely reachable with disciplined implementation, and it is enough for nearly every decision a business makes:

What decision-grade data does not support: treating analytics as accounting. Revenue lives in your shop and your books. Analytics is the instrument panel, not the ledger, and the companies that get this right reconcile the two on purpose instead of discovering the gap in a panic.

"Close enough" has a number, and it is yours

Here is where I depart from most writing on this topic: you do not need an industry statistic about average data loss. Published figures are vendor content with unknowable sampling, and your real number is measurable in an afternoon. Take last month's orders in your shop backend, take GA4's purchase count for the same window, and divide. That ratio is your capture rate. Track it monthly.

A stable capture rate, whatever its level, means your instrument is calibrated: multiply through when you need absolute estimates, and read trends directly. A moving capture rate is a fire alarm with a date on it, and the verification procedure is how you find what changed.

The uncomfortable corollary

Once you accept the gap exists, "our data says X" becomes "our sample suggests X," and some decisions stop being data decisions at all. A 2% difference between two campaigns is noise wearing a percentage sign. The discipline is knowing your margin and refusing to read signals smaller than it. Fewer certainties, held more honestly, beat precise-looking numbers nobody verified.

That reframe, more than any tool, is what separates companies whose analytics earns trust from companies with the five data lies on rotation. And if you do not currently know your capture rate, that is the single highest-value afternoon available to your business this month. It requires no budget, no migration, and no consultant, though if the afternoon turns up a gap that moves around, finding out why is precisely the kind of thing I audit for a living.