Looking for a Matomo alternative? Start with what you actually use
If the problem is the server or the cookie banner, Matomo itself may be the fix. If you still want to leave, list what people rely on, pick the kind of tool that covers it, and bring your history and campaign links with you.
In this article
Matomo does a lot. That's why people choose it, and it can also be why they start looking for something else. Before you compare tools, work out which part of Matomo you want to get away from, because for some of those problems the answer is still Matomo.
This guide covers how to tell which problem you have, what to list before you switch, the main kinds of replacement, and how to move without losing your history or your campaign links.
Name the problem first
Start by naming what's actually wrong. Each of these leads somewhere different:
Running the server
With Matomo On-Premise you run it yourself: a web server, PHP and a MySQL or MariaDB database, all kept updated, secured and backed up. If the reports are fine and only the server is the problem, Matomo Cloud runs the same software for you. Its plans include hosting, updates and daily backups.
The cookie banner
Matomo sets cookies by default, but it can run without them. For one site, add _paq.push(['disableCookies']) before the trackPageView line. There's also a setting that covers every site at once, and a checkbox in Matomo Tag Manager. You don't need a new tool to stop setting cookies.
Too much to look at
If people can't find the three numbers they care about among dozens of reports, a narrower tool can help. It won't help if they actually use those dozens of reports.
The bill
The core of On-Premise is free. Funnels, Heatmaps & Session Recording, Form Analytics and A/B Testing cost extra, either in a paid On-Premise plan or as plugins bought one by one. Cloud is a paid subscription with a free trial. If cost is the problem, price a replacement for the features you use, not for its cheapest plan.
If you turn cookies off, Matomo still has to tell visits apart. It does this with what it calls a config_id: a hash of the visitor's operating system, browser, browser plugins, IP address and language. It's valid for one visit and 24 hours at most, and the random seed behind it is thrown away every day, so a visitor who comes back on a later day isn't recognised. Whether that means you can also drop the banner depends on where you are and on everything else your site loads. The guide to running a website without a cookie banner covers what to check.
While you're in the settings, open Administration, then Privacy, then Anonymize data. Current Matomo masks two bytes of each IP address by default, but an installation that has been running for years may have been set up differently.
List what you actually use
If you still want to leave, list what people open or depend on in Matomo. Ask everyone who logs in, and search your site's code for anything that calls Matomo directly. Then check each item against the replacement:
| In Matomo | What to check in the replacement |
|---|---|
| Goals and ecommerce | Whether it has goals or conversions and revenue tracking, and on which plan. |
| Events | Custom events. Every _paq.push(['trackEvent', …]) call in your code has to be rewritten for the new tool. |
| Funnels | Funnels, if anyone uses them. On On-Premise they're a paid plugin, so check whether you're paying for it. |
| Visits log and visitor profiles | Visit-level history. A tool that counts visitors from a daily key can't show one person across several days, by design. |
| Heatmaps, session recordings, form analytics, A/B tests | Each one by name. If the replacement doesn't have them, you'll need a separate tool or will have to do without. |
| Segments and custom dimensions | Whether you can filter by the same things. A field you defined yourself in Matomo has to exist in the new tool too. |
| Matomo Tag Manager | Where your other tags will live. If Tag Manager loads other scripts on your site, those have to move as well. |
| AI Assistants channel | Since Matomo 5.5.0, visits from ChatGPT, Claude, Gemini, Copilot, Perplexity and a few others get their own channel under Acquisition. Check whether the new tool shows them separately or mixes them in with ordinary referrals. |
| MCP server | Since May 2026, Matomo Cloud and On-Premise can connect to AI tools such as Claude and ChatGPT through Matomo's own MCP server. If someone relies on that, look for an equivalent. |
| API and exports | Any spreadsheet, dashboard or script that pulls numbers from Matomo's API. It breaks on the day you switch. |
If the replacement is missing something on this list, that's a reason to pick another one, or to stay. For AI assistant visits in particular, the guide to tracking ChatGPT traffic shows how to find them in any tool, so you can check a candidate before you commit.
Five kinds of replacement
Once you know what you need, the options sort into a few kinds. The names below are examples, not a ranking. Plans and features change, so check each tool's own pages. What's here is as of November 2026.
| Kind | Examples | Fits when | Watch for |
|---|---|---|---|
| Matomo, hosted | Matomo Cloud | The reports are right and the server is the problem. | Price it for your traffic, and check that the features you use are in your plan. |
| Lighter, self-hosted | Umami (MIT licence; events, goals, funnels and journeys). Plausible Community Edition (AGPLv3). | Data has to stay on your own servers, but you want fewer reports. | It's still a server to run. Umami needs Node.js and PostgreSQL. Plausible's Community Edition leaves out funnels, user journeys and ecommerce revenue goals, and is released twice a year. |
| Lighter, hosted | Plausible, Umami Cloud | You want no server and no cookies. | Plan tiers. Plausible includes goals and custom events on every plan, but funnels and ecommerce revenue attribution only on its Business plan. |
| A full suite | Google Analytics 4 | You need events, funnels and the rest, and it has to cost nothing. | It sets a _ga cookie to tell users apart, which lasts about two years by default. That's exactly the kind of storage the EU's consent rule is about. |
| Free and minimal | Cloudflare Web Analytics | A rough count of pages and visits is enough, with no cookies or local storage. | No custom events, only the previous six months of data, and figures that may be sampled, depending on your filters and how much data matches. |
Two things matter more than any feature list. The first is how the tool counts a visitor, because that decides whether its numbers can be compared with your Matomo history at all. There's more on that below. The second is whether it can take your old data, which is the next problem.
Take your history with you
A new tool starts counting on the day you install it. Don't assume it can import years of Matomo data. Check its documentation, and plan as if it can't. Matomo gives you three ways to get your data out:
- Report exports. Pick a date range, open a report and click the export icon. Matomo exports CSV, TSV, XML, JSON, HTML and RSS, and the Reporting API returns the same formats. A yearly and a monthly export of the few reports you use may be all you need.
- Raw visit data. The
Live.getLastVisitsDetailsAPI returns individual visits on both Cloud and On-Premise. On your own server you can also read the database directly. Matomo Cloud has a Data Warehouse Connector for warehouses such as BigQuery. - The whole database. On Cloud, support can export your entire database as a dump that you install in a Matomo of your own. It's all or nothing, and it isn't available on trials.
Switch the tracking in one day. Keep the history for as long as you still need to look things up.
Check your campaign links
Matomo reads its own campaign tags as well as the standard ones. By default it reads the campaign name from parameters such as mtm_campaign, the older pk_campaign, and utm_campaign, utm_source or utm_medium. It reads the keyword from mtm_kwd, pk_kwd, utm_term and a few variants.
If your old links use mtm_, pk_ or other Matomo-only tags and the new tool only reads utm_ tags, it will treat those visits as ordinary visits and drop the campaign name. Check the new tool's docs, then look where old links tend to hide: newsletter templates, QR codes, social profiles, ad accounts and email signatures.
Matomo reads utm_ tags too, so you can retag before you switch and both tools will read the same campaign names. The UTM naming conventions guide has three rules that keep the reports clean.
Run both for a few weeks
Add the new script next to Matomo and leave both running for a few weeks. Compare trends, not totals. The lines should rise and fall on the same days. The totals won't match, and that usually has nothing to do with which tool is right:
- Unique visitors. With cookies, Matomo recognises a returning visitor by a random ID it stores in a first-party cookie. Plausible builds a key from a daily salt, the site, the IP address and the browser's user agent, and deletes the salt every 24 hours. So someone who visits on three days in a month can be one visitor to the first and three to the second. Run Matomo without cookies and it doesn't recognise returning visitors across days either, so the two get closer.
- Consent. If your Matomo setup waits for consent before it tracks or before it sets cookies, the new tool may count people Matomo never saw, or saw differently.
- Bots and blockers. Each tool filters bots its own way, and browser extensions block some trackers and not others.
- AI assistant visits. Matomo's AI Assistants channel only covers data collected after the upgrade to 5.5.0. Older visits stay in the channel they were first recorded under, such as Referral or Direct. Compare the same dates.
The article on why analytics numbers don't match goes through the first three in more detail and ends with a ten-minute check. If one tool shows much more Direct traffic than the other, the article on what direct traffic really is explains what's usually in it.
A short checklist
- Name the problem: the server, the banner, too many reports or the cost.
- If it's only the server or only the banner, try Matomo Cloud or cookieless Matomo first.
- List every report, plugin, tag, API script and AI connection people rely on.
- Pick the kind of replacement that covers that list, then compare tools within it.
- Export the reports you'll want later, or keep Matomo running without tracking.
- Retag
mtm_andpk_links withutm_tags. - Run both for a few weeks and compare trends, not totals.
A switch goes well when your list decides the tool. It goes badly when the tool decides what you no longer need.
Lomen is one of the lighter, hosted tools in that table. It takes one script tag, sets no cookies, never stores IP addresses, and shows pageviews, sources, countries, devices and UTM tags. It picks out visits from nine AI assistants and puts revenue from Stripe, Shopify, Lemon Squeezy, Polar and Paystack on the same chart as visitors, added together rather than split by source. It has no goals, custom events or funnels, and you can't host it yourself. If your list includes any of those, keep Matomo or choose a tool that has them.