A visitor lands on a five-post blog with no ecommerce, no remarketing campaign, and no ad account running behind it — and still gets a full-screen cookie consent wall before they can read a single sentence, because Google Analytics 4 is installed under the hood. Nobody sat down and decided this site needed cookie-based tracking. It’s just what the setup tutorial said to install.
In most of the sites I review, GA4 got added the same way: it’s the default, it’s free, and skipping it feels like leaving data on the table. What rarely gets asked is whether the site actually uses what GA4 collects — the audience-building, the ads attribution, the cross-device identity stitching — or whether a much lighter tool that skips cookies entirely would answer the same three questions (how many people came, where from, what did they read) without the consent-banner overhead.
This guide compares GA4 against the two privacy-focused alternatives that actually come up in practice, Plausible and Fathom — not as a “switch everything” pitch, but as an honest look at what each one measures, what a cookieless tool genuinely can’t tell you, and which sites are better off with each. If your site currently needs a cookie consent banner purely because of analytics, this is the decision that determines whether it needs one at all.
Quick answer
Google Analytics 4 uses cookies and device identifiers to build individual visitor profiles across sessions, which is why it requires consent under GDPR and needs Google’s Consent Mode v2 wired in if the site also serves Google-delivered ads to EEA, UK, or Swiss visitors. Plausible and Fathom don’t set cookies or store anything that identifies one visitor across visits — they count sessions using a rotating daily hash instead of a persistent ID — so neither one triggers a consent requirement on its own. The trade is depth: both drop GA4’s audience-building, remarketing integration, and BigQuery-level granularity in exchange for a lighter script, a simpler dashboard, and no banner. A site running Google or Meta ad campaigns that depend on remarketing audiences still needs GA4 (often alongside a privacy tool, not instead of it); a content site, portfolio, or small-business brochure site with no ad spend usually doesn’t.
How GA4 actually tracks visitors, and why that requires a banner
GA4 assigns every visitor a client ID, stored in a first-party cookie (_ga), and links that ID to session data, device information, and — if Google Signals is enabled — cross-device activity tied to a signed-in Google account. That persistent identifier is what lets GA4 build audiences, model conversion paths across multiple visits, and feed Google Ads with remarketing lists. It’s also, mechanically, personal data under GDPR the moment it can be linked back to an individual, which is why a GA4 install triggers a genuine consent requirement rather than a cautious default.
The part that catches people out is Consent Mode v2. Since 2024, Google has required it for any site running Google-served ads (including AdSense) to EEA, UK, or Swiss visitors — not just GA4 itself, the ad-serving layer sitting next to it. Without a certified consent management platform reporting consent state to Google, ad personalization and remarketing audiences silently stop building, even if the site never shows an error. This is the actual reason a “just add a cookie banner” fix isn’t optional once ads are involved: the banner isn’t decorating a legal requirement, it’s the thing Google’s own systems are checking for.
What Plausible and Fathom do differently
Both tools start from the same design decision: don’t collect anything that can identify one visitor across sessions, and the consent question disappears on its own rather than needing to be argued through a privacy policy.
Plausible
Plausible doesn’t set cookies and doesn’t store IP addresses or any other persistent identifier — it counts unique visitors using a daily-rotating hash of the site domain, visitor IP, and user agent, which makes the same person on day two mathematically impossible to link back to day one. It’s built and hosted in the EU on its own infrastructure (so EU visitor data never leaves the region), it’s open source and self-hostable if you want to run it yourself, and its tracking script is a small fraction of GA4’s size — a real, measurable difference on Core Web Vitals for a script that loads on every page. It’s paid-only: plans start at $9/month for up to 10,000 monthly pageviews, rising with traffic volume and feature tier (team seats, longer data retention, Stats API access), with a 30-day free trial and no credit card required to start.
Fathom Analytics
Fathom makes the same cookieless, no-persistent-ID commitment and states it’s built to comply with GDPR, CCPA, ePrivacy, and PECR specifically — the broader set of privacy regimes beyond just the EU. Its script is genuinely tiny, around 2KB, and it keeps data indefinitely rather than rolling it off after a fixed retention window, which matters if you actually want to compare this year’s traffic against several years back. Pricing starts at $15/month after a 7-day trial. One practical note if you’re weighing it against Plausible: Fathom’s own affiliate program only opens to active paying customers, not to anyone who wants to recommend it — worth knowing if a referral relationship is part of why you’re evaluating it, not just the analytics itself.
What you actually give up moving off GA4
This is the part most “ditch Google Analytics” posts skip, and it’s the honest reason GA4 isn’t obsolete. Neither Plausible nor Fathom builds remarketing audiences, because doing so would require exactly the persistent cross-session identifier both tools are designed not to collect — so if a site runs Google Ads or Meta campaigns that depend on retargeting people who already visited, GA4 (or the ad platform’s own pixel) isn’t optional, it’s the mechanism the campaign runs on. You also lose GA4’s deeper behavioral tooling: multi-step funnel exploration, cohort analysis, BigQuery export for custom querying, and the kind of granular event and conversion tracking that goes well beyond pageviews and referrers. Both privacy tools answer “how many, from where, reading what” cleanly; neither answers “which specific sequence of pages led to a purchase three visits later” the way GA4’s attribution modeling can.
When each choice actually makes sense
Keep GA4 (or run it alongside a privacy tool) when the site runs paid ad campaigns with remarketing audiences, needs BigQuery-level custom analysis, or genuinely uses GA4’s own reporting for conversion-path work — the free price point stops being the deciding factor once ads depend on the data it collects. Move to Plausible or Fathom when the site’s real question is simpler than GA4’s toolset: a content blog, portfolio, or small-business brochure site that just needs to know what’s getting read and where visitors come from, with no ad spend riding on the answer. In that second case, the consent banner GA4 requires is pure friction with nothing behind it — removing the tracking that triggers it removes the banner along with it.
Common mistakes
The one that comes up constantly: switching the analytics script but leaving the cookie-banner code live, because the banner was never actually scoped to “whatever tracking tool is currently running” — it was set up once, for GA4, and nobody revisited it. If GA4 and any ad pixels are genuinely gone, the consent requirement they created goes with them; check what the banner is still disclosing before assuming it’s still necessary, and update or retire the cookie policy page to match reality rather than leaving it describing a tool that’s no longer installed. The other common mistake runs the opposite direction: assuming a privacy tool’s lack of a consent requirement extends to every tracking script on the page. It doesn’t — a site running Plausible alongside a Meta Pixel or a live chat widget that sets its own cookies still needs consent for those, even with zero GA4 involvement.
Conclusion
GA4 and privacy-focused analytics aren’t really competing on the same question. GA4 is built for sites where advertising depends on the data; Plausible and Fathom are built for sites where a page-load-light answer to “how many, from where, reading what” is the actual requirement, and a consent banner was never buying anything except compliance overhead. The right choice isn’t about which tool is “better” in the abstract — it’s about whether anything on the site actually uses what only GA4 collects. If nothing does, that’s the real signal to switch, not the price tag or the privacy marketing on either side.
Etienne Basson works with website systems, SEO-driven site architecture, and technical implementation. He writes practical guides on building, structuring, and optimizing websites for long-term growth.