Matomo

The veteran open-source GA replacement. Heavyweight feature set, GDPR-compliant, self-hostable.

VISIT MATOMO

Key takeaway: Matomo earns its place when the requirement is essentially everything GA4 does, running on infrastructure you control. Ecommerce reporting, goals, funnels, segments, and multi-site rollups are all there and defensible to a regulator. For a content site or a small SaaS it is far more machine than the job needs, and Plausible or Umami are the lighter answers.

Quick facts

  • CategoryOpen-source / self-host
  • PricingOpen source
  • Starts atFree (self-host)
  • LicenseGPL-3.0
  • Created2007
  • GitHub stars19k
  • Script size~22KB
  • CookielessNo
  • Self-hostYes

What it is

Matomo (formerly Piwik) is the original open-source GA alternative, running since 2007. Feature-parity with GA4, events, goals, ecommerce, funnels, A/B test integration. PHP / MySQL stack, heavy by modern standards but battle-tested. GDPR-compliant out of the box; widely used by EU government and enterprise.

Best for

  • Enterprises requiring full GA-replacement feature parity with self-hosting
  • EU government and regulated industries with strict data sovereignty
  • Sites that need ecommerce / funnel analytics and refuse to use GA4

When not to pick it

Skip Matomo if you want a lightweight modern stack, the PHP / MySQL infrastructure is heavy. Skip if you only need basic web analytics; Plausible / Umami are easier.

My take

Matomo is the right pick when you genuinely need GA4 feature-parity without GA4. For typical content sites and SaaS, it is overkill, Plausible / Umami win on simplicity. For regulated EU enterprise, Matomo is often the only acceptable answer.

Feature parity, and the PHP and MySQL weight that pays for it

Matomo has been shipping since 2007 and it shows in both directions. The feature list genuinely rivals GA4: goals, ecommerce revenue attribution, funnels, segments, custom dimensions, multi-site rollups, user flow, plus a plugin marketplace for the rest. Very little a marketing team asks for is missing. The cost is the stack. It is PHP and MySQL, it wants cron for report archiving, and at real traffic that archiving job becomes something you tune rather than something you forget. Nobody deploys Matomo in ten minutes and walks away. If you are staffed to run a PHP application, that is fine, and plenty of European public-sector deployments prove it works at scale. If running a server is not on the table at all, Matomo Cloud is the paid hosted version of the same product.

Cookies, consent, and the configuration that decides it

Matomo is not cookieless by default, which surprises people who file it under privacy-first. It uses first-party cookies to recognise returning visitors, and that is what makes repeat-visit and duration metrics work properly. You can switch to a cookieless configuration and shorten data retention, and many EU deployments do exactly that to avoid a consent gate, at the cost of accuracy on returning users. The reason regulators tend to be comfortable with self-hosted Matomo is not that it collects less than GA4. It is that the data never leaves your infrastructure and no third-party processor is involved. That is a different argument from the one Plausible makes, and it is the stronger one when your compliance team cares about data sovereignty rather than data minimisation.

Frequently asked questions

Is Matomo a good replacement for Google Analytics?

It is the closest like-for-like replacement available. Goals, ecommerce, funnels, segments, and multi-site reporting map onto GA4 concepts, and there is an import path for historical Google data. What you give up is the native Google Ads integration and free hosting at Google's scale. What you gain is owning the data outright and a dashboard people can read.

Does Matomo need cookies?

By default it uses first-party cookies to recognise returning visitors, so it is not cookieless out of the box. You can configure it to run without them, which usually removes the consent-banner requirement in EU reviews, but repeat-visit and session metrics get less accurate. If cookieless is non-negotiable from day one, Plausible or Umami start there instead.

Matomo or Plausible?

Matomo when you need GA4-level features on your own infrastructure: ecommerce revenue, funnels, segments, regulated data sovereignty. Plausible when you need pageviews, sources, and a clean dashboard with nothing to operate. Most content sites and small SaaS products are the second case and end up regretting the Matomo install. Match the tool to the questions you actually ask.

Links

Compare Matomo side-by-side

Similar tools you should also consider

If Matomo is your pick, the next conversation is short

The 30-min call is where your analytics choice becomes a real implementation, an event-tracking plan that fits your product, and a privacy story that does not need a 4-screen cookie banner.