Every few months a client asks some version of the same question: do we actually need Google Analytics? It is free, it is the default, and almost every guide to running a website assumes you have it installed. It is also, for a lot of small businesses, a tool that gets set up once and never opened again.

Why the question keeps coming up

Google Analytics 4 can measure a great deal, and it costs nothing to use. It is built for marketing teams running campaigns across several channels, with budgets to justify and people whose job it is to interpret the numbers. That is who the interface is designed for. A small business owner logs in expecting to see how many people visited last week, meets a screen organised around events, parameters, explorations and audiences, and quietly closes the tab. Nothing is broken. The tool is simply answering questions that nobody in a two-person business is asking.

There is a second reason the question comes up. Google Analytics sets tracking identifiers in your visitors' browsers, and that brings consent obligations for European visitors. In practice it means a cookie banner, a consent mechanism that genuinely works, and some thought about what should happen when someone declines. For a small site, that is a noticeable amount of effort attached to a report you may never read.

What a small business actually needs from analytics

It helps to be honest about the questions you are really trying to answer. For most small businesses, the list is short:

  • How many people visited, and whether that number is going up or down
  • Which pages they looked at
  • Where they came from: a search engine, social media, a link on another site, or straight to your address
  • Whether they were on a phone or a desktop
  • Which pages tend to lead to an enquiry

That is close to the whole list. At this scale, almost everything else is noise. It is interesting to look at once, but not something you will ever change a decision over. If a report cannot plausibly lead to an action, it is costing you attention rather than earning it.

What privacy-first tools do differently

Privacy-first analytics tools take a different starting position. As a rule they set no cookies and store no personal identifiers for individual visitors. Instead of following one person across visits, they count activity in aggregate: this many visits, to these pages, from these sources, on these sorts of devices.

That design choice has three practical consequences. Because no identifiers are stored, these tools commonly fall outside cookie consent requirements, which can mean no banner at all. Because they collect less, their tracking scripts are a fraction of the size, so they add almost nothing to how quickly your pages load. And because there is simply less to show, the dashboard usually fits on a single page: visits, top pages, sources, devices, and a graph. You can read it in about thirty seconds.

Info

Falling outside consent requirements is a common outcome with privacy-first analytics, not an automatic guarantee. It depends on how the tool is configured and on what else your site loads. If you are planning to remove a cookie banner entirely, it is worth a quick check with someone qualified first.

The main options

A handful of names come up repeatedly. I am not endorsing one over another, and the right answer depends on what you need from it.

  • Plausible is lightweight and open source, with a single-page dashboard that is about as simple as this category gets.
  • Fathom Analytics is similarly simple to read, with a strong emphasis on compliance and keeping you out of consent territory.
  • Simple Analytics leans furthest into minimalism and privacy, and deliberately shows you very little.
  • Matomo is the most full-featured of the group and comes closest to Google Analytics in capability. It can be self-hosted, which means the data sits entirely under your control. That suits organisations with stricter requirements, but self-hosting is a commitment: updates, backups and a server to look after.

Most of these are paid subscriptions. The cost is usually modest and priced by how much traffic you get, so a small site sits at the bottom of the scale. That is the honest trade at the heart of this decision. You pay a small amount of money instead of paying with your visitors' data.

What you give up

The losses are real and worth stating plainly. The biggest is the deep integration between Google Analytics and Google Ads, along with the conversion tracking that comes with it. If you are spending money on paid campaigns, that connection is how you find out which spend is working.

You also lose the demographic and interest data Google infers about visitors, the advanced funnel and path analysis that lets you trace routes through a large site, and the sheer size of the ecosystem around Google Analytics. Every question you might have has already been answered somewhere, and there is no shortage of people who know the tool inside out. The alternatives have documentation and support, but nothing at that scale.

Warning

If paid advertising is a meaningful part of how you win customers, Google Analytics remains the pragmatic choice. The link with Google Ads is the one thing the privacy-first alternatives cannot replace.

The middle path worth considering

For most of the small businesses I work with, the sensible setup is rarely a straight swap of one analytics tool for another. Use a privacy-first tool as the everyday dashboard, chosen on the basis that you will genuinely open it, and pair it with Google Search Console.

Search Console is free, entirely separate from Google Analytics, and answers the search questions that neither analytics tool covers fully: which queries are bringing people to your site, where you appear in results, how often those listings are clicked, and whether Google is having trouble reading any of your pages. Put the two together and you have a readable picture of what is happening and a clear view of how search is treating you. For a lot of small businesses, that combination is more useful in practice than Google Analytics on its own.

If you decide to switch

One practical detail catches people out. Historical data generally does not transfer between analytics platforms. Your new tool starts counting from the day you install it, with nothing to compare against. The simplest way around this is to run both side by side for a few months, so you build up history in the new tool while the old one still covers the year-on-year comparisons. Before you turn anything off, export whatever is worth keeping from the existing setup, even if it is only an annual summary of visits and top pages.

The part that matters more than the tool

Analytics you never open has no value, however capable it is. A tool that captures everything and intimidates you into ignoring it is worth less than a plain dashboard you glance at once a month and actually act on, by writing another page about the service that keeps drawing enquiries, or fixing the page everyone leaves from.

So choose for usability rather than feature lists. If Google Analytics is already installed and you read it happily, there is no reason to change. If it has sat untouched for a year, the alternatives are worth half an hour of your time. They show you less, and that is why you might finally look at them.

When I set up analytics for a site, I start from the handful of questions you actually want answered and choose the lightest tool that answers them. Send the project brief with your current setup and what you want to measure.