A privacy-first alternative to GA4

Almost nobody looks for a privacy-first alternative to GA4 because they woke up caring about privacy in the abstract. They look because something concrete has gone wrong: a data protection officer has asked a question nobody can answer, a consent banner is visibly costing traffic, the reports that took two clicks in Universal Analytics now take a custom exploration, or a client has asked where their visitors' data goes and the honest answer is Google.

The useful news is that the replacement problem is smaller than it looks. Once you accept that you are not going to rebuild GA4's full surface, and that you probably never used most of it, the decision comes down to three questions: do you need a consent banner, do you need behaviour tooling, and do you need the data on your own hardware.

What privacy-first actually means here

The phrase is used loosely, so it is worth pinning down. In this market it means a tool that does not set a cookie, does not store an IP address, and cannot link the same visitor across days. That third property is the one that matters legally and the one most vendors are vaguest about.

The mechanism the better tools use is a daily rotating salt. An arriving request is hashed together with a secret that changes every day, and the IP and user agent that went into the hash are discarded before the response is sent. What is kept is an opaque token scoped to one site for one day. Because yesterday's salt cannot be recomputed, yesterday's visitors cannot be joined to today's. Cross-day tracking is not switched off by a setting, it is arithmetically unavailable.

That is the standard to hold vendors to. A tool that merely anonymises the last octet of an IP address, or that offers a cookieless mode you have to remember to switch on, is doing something weaker and you should score it accordingly.

The consent banner is the whole point

Under GDPR and the UK equivalent, analytics that set cookies or store identifiers need consent. GA4 does both, so it needs a banner, and a meaningful share of your visitors decline. Those visitors are not estimated, modelled or partially counted. They are absent.

This is the single largest accuracy problem in most GA4 deployments and almost nobody has measured it on their own site. GA4 is also the most blocked script on the web, so ad blockers remove another slice before consent is even asked, and thresholding then hides low-volume rows in the reports that survive. The number in the dashboard is a filtered projection of your traffic, and the filtering is invisible.

A cookieless tool needs no prompt, so it counts the visitors who would have declined one. Expect your traffic to look larger after switching, not smaller, and expect the difference to be big enough to change which pages you think are working. Run both for a month before you cancel anything: the gap between them is the most useful thing you will learn all year.

What you actually give up

Being straight about this is what makes the rest of the advice worth reading.

You lose Google Ads conversion bidding. This is real, it is exclusive, and if you spend meaningful money on Google Ads you should keep GA4 running for that purpose alone. The right move is not to switch but to add: keep GA4 feeding the ad platform, and run a light cookieless tool as the dashboard you actually open. A 1,270-byte second script costs you nothing you will notice.

You lose BigQuery export and the Looker Studio ecosystem, unless you pick a tool with a proper Stats API. You lose cross-device identity stitching, which is the point of a privacy-first tool rather than an oversight. And you lose the enormous configurability of GA4, which for most sites is a relief rather than a loss.

Picking by why you are leaving

If you left because of the consent banner and you want behaviour tooling as well, the cookieless tools that bundle heatmaps are the only option that does not put the banner straight back. Adding Hotjar or Microsoft Clarity to a cookieless setup reintroduces cookies and the consent requirement, which undoes the reason you switched.

If you left because GA4 became too complicated, take the tool with the clearest single screen and stop optimising. If you left because a regulator or a client asked where the data lives, you want either a vendor that lets you choose the storage jurisdiction, or a self-hosted tool where the question does not arise.

And if you left because of cost, note that GA4 is free of charge and never was free of cost. You were paying in consent friction, in data handed to an advertising company, and in the specialist time needed to get answers out of it.

The rest of the field

Common questions

Related guides