Set Up Privacy Analytics in an Afternoon

Plenty of people read the case for privacy-friendly analytics, nod, and never switch — because it sounds like a project. It isn't. It's paste one small line, delete a bigger one, and lose the cookie banner you no longer need. Here's the whole switch, with the fear taken out.

Plenty of people read the case for privacy-friendly analytics, nod, and then never switch — because it sounds like a project. It isn't. Replacing surveillance analytics with a privacy-respecting tool is genuinely an afternoon's work, often less, and the modern tools are simpler to use than what you're leaving. Here's the whole move, start to finish, with the fear taken out of it.

What you're trading away is real but small: the privacy tools show you the things that actually matter — how many people came, where from, which pages they read — without cookies, without consent banners, and without shipping your visitors' behavior to an advertising company. What you gain, besides your visitors' privacy, is a lighter, faster site and numbers you can actually understand. (A pleasant surprise: these tools are often more accurate, because the ad-blockers that now block Google don't block them.)

Before you start: a couple of decisions

Decide these and you're ready

Hosted or self-hosted? Hosted (a small monthly fee) is the afternoon version — sign up, paste a snippet, done. Self-hosted (free, on your own server) is more sovereign but more setup. Either is fine; pick honestly for your time.
Which tool. A few well-regarded, cookieless options: Plausible (tiny, simple, hosted or self-host), Fathom (simple, hosted), Umami and GoatCounter (free, self-hostable; GoatCounter is a single small program), Matomo (fuller-featured, has a cookieless mode). Any of these respects your visitors.
Access to edit your site's pages — specifically to paste one small snippet, and to remove your old tracker.
An afternoon, or honestly less. The hosted path is often twenty minutes.

The switch you've been putting off as a project is, in practice, paste one small line and delete a bigger one. The hard part was only ever deciding to.

The switch, in five steps

Choose

Pick your tool and open an account

From the shortlist above, pick one — for most small sites, the simplest hosted option is the right call. Sign up (or, if self-hosting, install it; the single-binary ones are genuinely quick). Don't overthink this; they all do the core job well, and you can change later. Add your website's address when it asks.

Install

Add the one small snippet

The tool gives you a short line of code — a single small script tag. Paste it into your site's pages, typically just before the closing </head>. One line, every page. That's the entire installation. No cookie banner to configure, because there are no cookies to consent to.

Verify

Confirm it's actually counting

Open your own site in a browser, then look at the tool's dashboard — you should see a visit appear (often in real time). Click around a couple of pages and watch them register. If you see yourself, it's working. If not, re-check that the snippet is on the page and saved — that's nearly always the fix.

The point of it

Remove the old surveillance tracker

This step is the whole reason you're here, so don't skip it. Find and delete your old analytics code — the Google Analytics / gtag snippet, or whatever tracker was there. Switching isn't done until the old spy is gone, not just the new one added. Search your pages for "gtag", "analytics", or "googletagmanager" and remove those blocks.

Tidy up

Drop the cookie banner you no longer need

Here's the reward. If that cookie-consent banner existed only because of tracking analytics, you can now remove it — there's nothing left to consent to. A faster page, a cleaner first impression, and no nagging pop-up. (Check it wasn't also covering other trackers first — but often it wasn't.)

If the numbers look different from before: don't panic — they often look lower, and that's usually because the new tool isn't inflating or, more often, because it's finally honest. You're also no longer losing the 20–40% of visitors who declined the old cookie banner. The picture you get now is cleaner and truer, even when the headline number is smaller. Different isn't worse.

Why this is the easy win it is

Most privacy improvements ask you to give something up. This one barely does: you keep the insight that actually helps you run your site, you lose the surveillance and the consent banner, your pages get lighter, and your visitors stop being silently sold. It's the rare change where the ethical choice and the easy, better-performing choice are the same choice.

And it's the doing behind the principle the field guide keeps returning to — you were never choosing between "know your traffic" and "respect your visitors." That was always a false trade. This afternoon is how you stop making it.

▲ The why This is the doing of "Measure traffic without surveilling people" That guide argues you can count visits without spying. This is how you actually switch — in an afternoon. Read it →

When you're ready

Want it set up properly, the first time?

I set up privacy-respecting analytics as part of every clean build — cookieless, banner-free, the old surveillance tracker fully removed, the numbers that matter kept. You get the insight without selling your visitors, on a site that's lighter for losing the spyware.

See privacy & hardening services →

The Field Manual · the doing, step by step

01How to actually leave a platform 02Make your forms keyboard-accessible 03Set up privacy analytics in an afternoon 04Get your domain into your own hands