// Uncategorized

Google Analytics alternatives worth a look

Published
Updated
Author
Ben
Filed under
Uncategorized

The best reason to leave Google Analytics has nothing to do with the interface. It is that a script-based analytics tool misses every visitor running a blocker, and on a technical audience that can be a third of them.

If that is your problem, the interface you move to matters less than whether the measurement happens somewhere a blocker cannot reach.

What you actually lose by moving

Ad platform integration. If you run Google Ads, the analytics link supplies conversion data and audiences back to the auction, and replacing that is real work.

Free scale. Google Analytics is free at volumes where paid tools cost real money.

Historical data. Nothing migrates cleanly. You start a new series, and for a year you are comparing across two systems. Run both in parallel during that period, which everyone regrets skipping.

The categories

Privacy-first, cookieless, lightweight. Plausible, Fathom, Simple Analytics and Cloudflare Web Analytics sit here. They give you pages, sources, countries and goals, in one screen. The script is a few kilobytes, and most configurations need no consent banner.

What you give up is depth. There is no funnel exploration, no cohort analysis and no session replay. For a marketing site, that is often the right trade, because nobody was running those reports anyway.

Product analytics. PostHog, Mixpanel, Amplitude. Built around events and users, and not pageviews. That is what you want if the thing you are measuring is a product and not a brochure. PostHog self-hosts, which matters if your data cannot leave your infrastructure.

These are heavier, both in script weight and in the work of defining an event taxonomy. Done badly they produce a thousand events nobody can interpret.

Log-based and server-side. Counting requests at the server or the edge. It sees every request, including the ones from blockers, and a consent banner cannot break it. It knows nothing about what happened inside the page.

The strongest setup is usually a server-side count as the number of record, with a client-side tool for the behaviour questions. And an acceptance that the two will never match.

Matomo is the closest to a like-for-like replacement, self-hostable, with most of the familiar reports. It is also the heaviest of the alternatives, and self-hosting it is a database you now operate.

How to choose in ten minutes

If you need Google Ads conversion data, keep Google Analytics and add something else alongside it.

If you have a marketing site and want to know which pages and sources produce enquiries, take a lightweight privacy-first tool and stop there.

If you are measuring a product with sign-ups and retention, take a product analytics tool and spend the time on the event taxonomy.

If your audience blocks scripts, count server side and treat everything else as a sample.

The part people skip

Whatever you choose, define the one action that matters before you install it. A tool cannot tell you whether the traffic was any good if nobody has said what good means.

We wire measurement as part of conversion work, and the first question is always that one.

Need a MAP policy that actually holds?

Book a strategy call