You can learn which pages attract visitors without building a profile of every person who visits your website. The right analytics tool depends on the decisions you need to make, how much data you need to collect, and whether you want to operate the software yourself.
This comparison is based on the vendors' current documentation and pricing, not on hands-on installations or performance tests. Prices and limits were checked on October 22, 2026; confirm the linked vendor pages before choosing a plan.
Privacy-friendly does not mean data-free
An analytics service still receives information about page visits. Depending on the product and configuration, that can include page paths, referrers, browser and device details, approximate location, or events you define. A tool that avoids cookies can still process data, and a website can still send personal information in a URL or custom event by mistake.
Start with the question you want to answer. If you only need to know which pages are popular, you may not need persistent visitor IDs, session replay, or detailed user journeys. Collecting less makes the setup easier to explain and maintain.
Compare the options
| Tool | Hosting and cost | Documented data approach | Good fit |
|---|---|---|---|
| Cloudflare Web Analytics | Free; available on all Cloudflare plans | Cloudflare says it does not use cookies or local storage for usage metrics and does not fingerprint visitors for analytics | A small site that wants basic usage and performance information without a paid analytics subscription |
| Plausible | Paid Cloud plans scale with pageview volume; the pricing selector showed a 10,000-pageview tier starting at $9/month. Its AGPL-licensed Community Edition can be self-hosted | No cookies or persistent visitor IDs; its daily visitor estimate is scoped to one site and device | A managed, compact dashboard or an open-source option for someone prepared to run it |
| Umami | Cloud Hobby is free for up to 100,000 events per month and one website. Pro is $20/month for up to 1 million events. It can also be self-hosted | Its tracker does not use cookies, but collects pageviews, referrers, browser and operating-system details, device type, and approximate location | Someone who wants an open-source product, event tracking, and a choice between hosted and self-managed service |
| Matomo | On-Premise software is available to download for free; hosting and maintenance are yours. Cloud plans are priced by traffic | Provides configurable privacy controls, including options for cookies, consent, anonymization, and retention | A site that needs more control or reporting flexibility and can budget for setup and ongoing administration |
Cloudflare describes its analytics as available on all plans, and its product page says the service does not use client-side state such as cookies or local storage, or fingerprint people for analytics. That makes it a reasonable first check if you use Cloudflare and only need a high-level view of traffic and page performance. Review the setup guide to see how its tracking snippet fits your site.
Plausible Cloud is managed, while the Community Edition is a free, self-hosted release under the AGPL license. Plausible says it does not use cookies or persistent visitor identifiers. Its daily visitor identifier is limited to one device and website, so it does not recognize the same visitor across days or sites. Its data policy also explains what information it derives from requests and what it stores. Choose the hosted service to avoid maintaining the analytics stack; choose the Community Edition only if you can handle deployment, updates, backups, and security.
Umami's hosted plans count events rather than advertising an unlimited allowance. Check what your site sends, especially if you plan to record custom events, before estimating the monthly bill. Its FAQ says the tracker does not use cookies, but it still collects useful details such as referrers and approximate location. Self-hosting gives you more control over infrastructure, but you also take responsibility for keeping the service available and deciding how long to retain its data.
Matomo offers both Cloud and On-Premise deployments. Its privacy guide covers settings for cookies, consent, anonymization, and data retention. Those options are useful when you need to fit analytics to a specific data policy, but flexibility means more choices to configure and review. The free On-Premise download does not remove server, backup, upgrade, or maintenance costs.
Which one should you choose?
- Choose Cloudflare Web Analytics if you want a free starting point for basic traffic and performance questions and are comfortable using its dashboard and tracking setup.
- Choose Plausible Cloud if you want a straightforward managed dashboard and its pageview-based plans match your traffic. Consider the Community Edition if you can operate your own server and comply with its license.
- Choose Umami if you want an open-source option with hosted and self-hosted paths, and its event limits and reporting suit your needs.
- Choose Matomo if detailed controls or more extensive reports are worth the extra configuration and operating effort.
These are workflow recommendations, not a ranking of accuracy. The best fit is the least complicated tool that answers your real questions.
Check privacy and cost before adding a tracker
- Write down the decisions you need to make. Page popularity, campaign referrals, and a checkout completion count are different requirements. Do not collect visitor-level data just because a tool offers it.
- Choose hosted or self-hosted deliberately. Hosted plans trade a recurring bill for less infrastructure work. Self-hosting trades that bill for server costs, upgrades, backups, monitoring, and responsibility for access and retention.
- Review the data your site will send. Check page URLs, query parameters, referrers, custom events, and any other scripts on the page. Do not include email addresses, account IDs, or other identifying details in event names or properties.
- Set a retention and access policy. Keep only the detail and history you need, limit dashboard access, and understand how exports and deletion work for the plan you choose.
- Check applicable privacy requirements. A cookie-free tracker is not a universal exemption from privacy or notice obligations. Umami, for example, notes that whether a cookie notice is needed depends on other services and applicable requirements. Consider your jurisdiction, purpose, configuration, and the rest of your website before deciding what notice or consent is appropriate.
- Estimate the full cost. For a hosted plan, include event or pageview limits, additional usage, and any features you need. For self-hosting, include infrastructure and the time required to keep the service secure and working.
If you are uncertain, start with aggregate page and campaign metrics, avoid collecting custom personal data, and add detail only when it supports a specific decision. Recheck the product's data policy and settings whenever you add a new tracking feature.
