Why Cookieless Analytics Is Becoming a Topic Now
Two developments are colliding. First, banner fatigue: cookie-consent banners lower the acceptance rate, and what a user doesn't confirm, classic analytics doesn't even measure — the data gap grows. Second, the ongoing GDPR uncertainty around US-based analytics services, which unsettles many clients in the DACH region.
The result: more and more agency clients ask for alternatives that work without cookies and process data in a privacy-friendly way. Cookieless, often self-hostable tools like Rybbit, Plausible, and Umami are built for exactly this. Important as a framing upfront: we're a reporting provider, not legal counsel. Whether a specific setup works without consent at your clients depends on the configuration and the applicable law — that belongs with a data protection expert, not decided by a blog post.
What These Tools Have in Common
Rybbit, Plausible, Umami, Matomo, Pirsch, and Fathom share the same basic idea: lightweight, privacy-friendly web analytics that treat personal data as sparingly as possible. Most work entirely without cookies; Matomo does set first-party cookies by default but can likewise be run GDPR-compliant and cookieless. Instead of tracking individual users across sessions and devices, they count aggregated events — page views, referrers, countries, device classes.
For agency clients this has three practical advantages: the consent topic eases up (depending on the setup), the tracking script is tiny and barely slows the website, and the dashboards are so simple that clients understand them without training. The price for that is less depth: anyone who needs granular audience analysis or complex attribution models across many touchpoints deliberately won't find those in these tools. For the question "how many people are coming, from where, to which pages?" they're completely sufficient.
The Six Cookieless Tools in Brief
The six tools differ less in their basic principle than in maturity, feature scope, and operating model. A rough overview for orientation — the exact details are best checked on the respective project pages:
- Plausible: the most established of these tools, open source, either hosted or self-hosted. Known for a very tidy single-page dashboard and a large user base.
- Umami: also open source and popular for self-hosting, lean and quick to set up. Solid base metrics, often used by technically inclined teams.
- Rybbit: the newest addition, also built around privacy and simplicity. A smaller but growing footprint than the two established players.
- Matomo: the largest open-source analytics solution, either self-hosted or as an EU cloud. Its strength is full data ownership — the data belongs to you, not Google. It sets first-party cookies by default but can be configured cookieless if you want.
- Pirsch: cookieless and made in Germany, hosted at Hetzner in Germany. For clients with high privacy demands, the German hosting is often the deciding argument.
- Fathom: a lean, cookieless cloud solution (a Canadian company) with optional EU data isolation. No self-hosting, but quick to set up.
- In common: a privacy-friendly base approach, a lightweight script, simple dashboards, a focus on aggregated rather than personal data.
Which Tool When? The API Question Before You Decide
Before you recommend one of the tools to a client, it's worth looking at an inconspicuous but practical question: what does the API access cost through which a reporting tool later fetches the numbers? With the three self-hostable classics — Plausible, Rybbit, and Umami — programmatic access partly depends on the cloud plan; with Matomo (self-hosted for free, otherwise its own cloud), Pirsch (API access included in every cloud plan), and Fathom (just an account needed) it's easier to get. For the three classics in detail:
- Plausible: the Stats API is a Business-plan feature on Plausible Cloud. On self-hosted Plausible CE (from version 2.1.2), by contrast, it's included at no extra charge.
- Rybbit: API keys require a Standard plan on Rybbit Cloud. Run Rybbit self-hosted and that requirement disappears entirely.
- Umami: self-hosting is free, API access included. Only Umami Cloud may require a plan of its own.
- Rule of thumb: self-hosting is the free route to API access with all three — in the cloud, you need the Business plan at Plausible and the Standard plan at Rybbit. (Plan details as of July 2026, no guarantee — check the vendors' current pricing pages.)
The Reporting Problem With Privacy Tools
As good as these tools are individually, a practical problem arises in day-to-day agency work. Your clients use different solutions: client A has Plausible, client B has Umami self-hosted, client C just switched to Rybbit, and in between some still run GA4. Each tool has its own dashboard, its own login, its own presentation.
For you that means several interfaces to log into, no unified view, and in the worst case a different path to the same metric for each client. This is exactly where a reporting tool that's provider-agnostic comes in — one that ties in the web-analytics source no matter which one it is.
How MetricDash Ties in All Six
MetricDash supports all six cookieless tools — Rybbit, Plausible, Umami, Matomo, Pirsch, and Fathom — plus GA4. The website-analytics area is deliberately built provider-agnostic: you connect the source your client uses, and the numbers appear in the same normalized view as for every other client. A client with Plausible and one with GA4 see the same tidy structure at your place.
This solves the multi-tool problem without forcing your clients to switch: anyone who wants to stay on self-hosted Umami stays there — the data still comes together at your end. And because MetricDash charges per client account, it costs nothing extra whether a client has just one web-analytics source or, alongside it, Google Ads, Meta Ads, and Search Console. An honest note: web analytics lives in the dashboard and client portal in MetricDash, not in the sent report emails — those contain Google Ads, Meta Ads, Microsoft Advertising, Search Console, and leads.
How to Connect Them: Per Client via Key or Token
Unlike Google Ads, Meta, or GA4, the cookieless tools don't run via an interactive OAuth login but are connected per client individually. For Plausible, you enter the API key and the client's domain (e.g. example.com); for Rybbit, the API key and the numeric site ID from the tracking snippet. Umami depends on how it runs: in the cloud, the API key is enough; for a self-hosted instance, you sign in with your Umami login — plus the website ID in both cases. Matomo you connect via an auth token, host URL, and site ID; Fathom via an API token and site ID; and Pirsch, for once, via an OAuth client (client ID and secret). Self-hosted instances connect additionally via their respective host URL.
Nothing changes about your clients' tracking code — MetricDash only reads the statistics. Once connected, the numbers appear in the respective client's website tab and in the portal, in the same normalized view as every other source.
The GDPR Angle for Your Client Conversation
Cookieless analytics is a strong argument in a client conversation — but sell it honestly. The right pitch isn't "this makes you guaranteed GDPR-compliant" but "this reduces consent friction, loses less data to unconfirmed banners, and rests on a more data-minimal foundation." The final legal assessment belongs with your data protection officer, not in your sales promise.
For you as an agency, the practical gain is clear: you can offer clients who want to move away from classic tracking for privacy reasons a clean alternative — and still run unified reporting with MetricDash. If you want to try it, connect a client with Plausible, Umami, or Rybbit in the current open alpha and see how the shared view feels. The alpha is completely free, no credit card.