Matomo Problems & Issues
Real user-reported problems, complaints, and limitations for Matomo. Based on analysis of 14 signals.
Overall score: 68/100
Issues by Category
Matomo reports not updating: archiving cron not running
Self-hosters who disable browser archiving (the recommended setting) must run core:archive on a schedule. Forum threads show it breaking after server moves, old archive.sh cron lines and permission problems, leaving flat graphs while the Visits Log still shows traffic.
'Oops... there was a problem during the request' error in Matomo
A generic error shown in reports that can mean file permissions, a WAF blocking requests, PHP memory or timeouts, CORS or CSRF problems or a broken update. Matomo's troubleshooting page lists 14 ordered steps, and users report it appearing after upgrades.
Ad blockers make Matomo undercount visitors
Matomo says ad blockers and privacy extensions can stop the tracker, which can mean 5-10% fewer visits than other tools. Requests to matomo.js and matomo.php are commonly filtered, and the usual workarounds (self-hosting the JS, proxying on your own domain) are community-driven rather than one-click.
Self-hosting means you own upgrades, backups and security patches
Matomo On-Premise needs PHP, MySQL/MariaDB, file permissions, cron and regular updates. Update problems, wrong permissions and missing files after upgrades are a recurring forum topic, so it is a poor fit for teams with no sysadmin.
Matomo visitor numbers don't match Google Analytics or Search Console
Matomo counts visits, not clicks, honors Do Not Track by default, and can lose visits to blockers and consent banners. Matomo's FAQ lists ten reasons its numbers differ from search engines and ad networks, which frustrates people comparing tools.
Matomo archiving is slow or runs out of memory on busy sites
Archiving can run for hours on high-traffic installs or with many segments, and users report PHP memory errors even at multi-GB limits, especially for yearly periods and roll-up sites. Matomo's own guidance is a tiered setup with cron, Redis queued tracking and a tuned database.
Matomo for WordPress can bloat the database and slow the site
Reports describe the WordPress plugin's database growing far past expectations and tracking requests loading the full WordPress stack (up to hundreds of milliseconds in one report). Fixes involve cleanup, queued tracking or switching to a standalone install.
Matomo Cloud prices by 'hits' and charges overage fees
Cloud tiers are based on monthly hits (pageviews plus events). Matomo's Cloud terms say exceeding the allowance triggers overage fees, unused hits expire at the end of the term, and prices below the top tiers require checking the pricing page or asking sales.
Heatmaps, funnels and search keywords cost extra with self-hosting
Matomo Community is free, but plugins for Heatmaps and Session Recording, Funnels, Custom Reports, Form Analytics and Search Engine Keywords Performance come with paid On-Premise bundles (Team from EUR 275, Business EUR 1,450, Enterprise EUR 3,400 per Matomo's pricing page), so 'free' only covers the base reports.
Matomo shows 'no data' even though tracking code is installed
The most common complaint. Reports stay empty because of a wrong tracking code or site ID, an ad blocker or Do Not Track setting, a consent setup that waits for opt-in, or browser-triggered archiving being switched off with no cron job. Matomo's own FAQ lists 16 separate causes, which says how often it happens.
Matomo has a steep learning curve and dated interface
Review-site summaries describe a learning curve and technical setup effort, and G2 reviewers mention dashboards that are hard to customize. It is much heavier to learn than minimal tools like Plausible or Fathom.
Matomo support is email-only and community-driven for free users
Free Community users rely on the forum and FAQs. Paid support is email-based (the Team bundle lists 24/5 with a 12-hour response) and one reviewer described paid support as poor, while others say email replies do arrive.
'Keyword not defined' replaces organic search keywords
Google, DuckDuckGo and others withhold keywords, so Matomo shows 'Keyword not defined'. Real queries only come via the Search Engine Keywords Performance plugin (included in Cloud, a paid add-on On-Premise) and only as aggregated data, not per visit.
Matomo still needs a cookie banner outside France
Matomo is the tool the French CNIL points to for the consent exemption, but the exemption is strict, France-focused and the CNIL retired its approved list in 2026. Elsewhere in the EU most setups still need consent, and features like e-commerce analytics go beyond the exemption.
Regret Patterns
Common reasons users regret choosing Matomo.
Disabled browser archiving without setting up cron
Following the advice to turn off browser-triggered archiving, then discovering reports stay empty because no cron job runs core:archive.
Assumed the self-hosted edition included heatmaps and funnels
Found out these are paid premium plugins only available in bundles or on the Marketplace.
Underestimated hits on Matomo Cloud
Pageviews plus events count as hits, so traffic growth or event tracking pushed the site over its allowance and into overage fees.
Put self-hosted Matomo on a small server
Archiving and reports struggled as traffic and segments grew, forcing database tuning and more RAM.
Expected zero consent banner anywhere
Assumed Matomo removes the need for consent, then learned the exemption is strict and mostly France-specific.
Tried to cancel by emailing support
Cloud terms say only cancelling through the account screen counts, so the subscription kept renewing.
When Matomo Breaks Down
Specific scenarios where Matomo fails or underperforms.
High-traffic site on a small server
Archiving runs for hours or hits PHP memory limits without cron, tuned MySQL and queued tracking.
Privacy-aware visitor base
Ad blockers, Brave and Do Not Track mean a noticeable share of visits go uncounted, around 5-10% per Matomo.
Moving Matomo to a new server
The cron job is left behind or file permissions break, leaving reports empty or throwing 'Oops' errors.
Many segments and long date ranges
Yearly or multi-month reports and custom segments multiply archiving work and cause timeouts.
Selling to the EU outside France
The CNIL exemption does not cover other regulators, so you still need consent for full tracking.
WordPress hosting with many plugins
The tracking request loads WordPress and the database grows, slowing small hosts.