I thought 200 people visited my site. It was 11.

Azaan Ali Raza — Tue, 23 Jun 2026 11:00:59 +0000

3 AM. Launch night.

Google Analytics said 200 visitors. 12 signups. I was buzzing.

Then my co-founder messaged me:

"Bro your site isn't loading any scripts on my work laptop."

I checked. uBlock Origin — blocks GA. Privacy Badger — blocks GA. His company firewall — blocks GA.

I wasn't reading my traffic. I was reading the survivors.

I pulled the real number the next morning.

11 people.

Not 200. Eleven.

I had spent 6 hours that week A/B testing headline copy. Rearranging buttons. Tweaking CTA colors. All of it — based on data that was missing 95% of my actual visitors.

That's when I stopped using Google Analytics. And started building AmazeMatrix.

The idea was simple: analytics that can't be blocked.

No cookies. No third-party domain. Script loads from your domain as a first-party request. Blockers don't see it. Firewalls don't flag it. Under 2KB so it doesn't slow anything down.

First week of running it on a real site?

Actual traffic was less than half of what GA reported. Gone. Invisible. Making decisions off ghost data.

Building it wasn't clean either.

My "active visitors" counter hit 47 on a page with 8 real sessions. Bounce rate was firing before the page finished loading. Three beta testers churned silently — a CSP header was eating my script and nobody told me.

Every bug made me angrier at GA for normalising bad data.

I fixed all of it. Session expiry. SPA route tracking. A CSP handshake so you know the script fired before you trust a single number.

The tagline wrote itself:

Know more. Track less.

If you're building something and quietly suspect your analytics are lying to you — they probably are.

Early access is open → amazematrix.com

Drop your current analytics stack in the comments. Genuinely curious how many people have caught GA lying.

DEV Community: Azaan Ali Raza

I thought 200 people visited my site. It was 11.