Matomo

What Is Matomo?

Matomo is an open-source, privacy-focused web analytics platform that lets organizations measure website and app traffic while keeping full ownership of the underlying data. It is the most widely used open-source analytics tool in the world, and the project reports that it powers analytics on well over one million websites across more than 190 countries. Because it can be self-hosted, Matomo is the answer most teams reach for when the question is "how do we understand our visitors without handing their data to a third party?"

Originally launched in 2007 under the name Piwik, the project rebranded to Matomo in 2018. The name change reflected a maturing platform, but the core promise never changed: a feature-complete analytics suite that you can run on your own server, under your own legal jurisdiction, with no data sampling and no obligation to share visitor records with an advertising company. Matomo is frequently chosen by government agencies, universities, healthcare providers, and privacy-conscious businesses precisely because of this ownership model.

If you are auditing a website and want to understand its measurement stack, Matomo is one of the most important analytics tools to recognize. This profile explains how Matomo works, the concrete technical signals that reveal it on a live site, its strengths and weaknesses, and how it compares to alternatives like Google Analytics 4.

How Matomo Works

Matomo collects data using a small JavaScript tracker that you embed on every page. When a visitor loads a page, the tracker builds a tracking request describing the page view, screen resolution, referrer, language, and any custom events, then sends that request to a Matomo endpoint. Crucially, that endpoint is a server you control, not a Google or vendor server, when you run the self-hosted edition.

The tracker is configured through a global JavaScript array named _paq (the "p" is a nod to the original Piwik name). Your installation snippet pushes commands onto this array, for example _paq.push(['trackPageView']) and _paq.push(['enableLinkTracking']). The Matomo library reads from _paq, processes those commands, and dispatches the tracking beacon. This queue-based design means tracking commands can be registered even before the main matomo.js file finishes loading.

On the server side, Matomo is a PHP application backed by a MySQL or MariaDB database. The tracking endpoint is historically named matomo.php (older installs use piwik.php), and reporting data is processed through a system of archived aggregates so that dashboards load quickly even for high-traffic sites. Because you own the database, there is no data sampling: every visit is recorded and queryable.

Matomo also supports server-side tracking and a HTTP Tracking API, so events can be sent directly from a backend without any browser JavaScript. This is useful for measuring conversions, server events, or environments where client-side scripts are blocked. There is also a Tag Manager built into Matomo for deploying tags without code changes.

A useful detail for anyone reverse-engineering a stack is how Matomo handles archiving. Rather than computing every report on demand, Matomo periodically aggregates raw logs into pre-summarized "archives," either on a cron schedule for large sites or on the fly for smaller ones. This is why a self-hosted Matomo install on a busy site is typically paired with a scheduled core:archive task; the presence of that pattern is a strong operational tell that an organization is running Matomo seriously rather than as a casual add-on. The raw log tables remain in the database, so historical reprocessing and unsampled drill-downs are always possible, which is a meaningful contrast with sampled, vendor-hosted platforms.

How to Tell if a Website Uses Matomo

Detecting Matomo is straightforward once you know its fingerprints. Here are the most reliable signals and the tools you can use to find them.

Script domains and file names. Look for requests to matomo.js or the older piwik.js. Matomo Cloud customers load the tracker from a subdomain like yourbrand.matomo.cloud, while self-hosted installs serve it from the site's own domain (for example /matomo/matomo.js). The tracking beacon itself hits matomo.php (or piwik.php).

JavaScript globals. Open your browser DevTools, go to the Console, and type _paq then press Enter. If Matomo is present you will see an array (often with trackPageView style entries inside). You can also check window.Matomo or the legacy window.Piwik object, which expose the tracker API.

Cookies. Matomo's first-party cookies are easy to spot. The session cookie is typically named MATOMO_SESSID, and visitor cookies are prefixed _pk_ (for example _pk_id and _pk_ses). In DevTools open Application, then Cookies, and scan for those names.

Network requests. In DevTools open the Network tab, reload the page, and filter for matomo or piwik. You will see the request for the tracker JavaScript and one or more beacon requests to matomo.php with query parameters such as idsite, rec=1, action_name, and url.

Here is a quick reference for the main detection methods:

Tool	What to look for	Signal of Matomo
View Source	matomo.js, piwik.js, the _paq array	Tracking snippet present in HTML
DevTools Network	Requests to matomo.php, *.matomo.cloud	Beacons being sent
DevTools Console	Type _paq, Matomo, or Piwik	Globals defined
DevTools Application	MATOMO_SESSID, _pk_id, _pk_ses cookies	First-party Matomo cookies
curl -I / curl	curl -s https://example.com | grep -i matomo	Snippet in raw HTML
Wappalyzer	Browser extension flags "Matomo"	Automated detection
BuiltWith	Analytics section lists Matomo	Historical and current detection

A curl check is handy when you want to inspect raw markup without a browser. Running curl -s https://example.com and searching the output for matomo, piwik, or _paq quickly confirms whether the snippet ships in the initial HTML. Note that tags injected by a tag manager may not appear in the raw response, so combine curl with a DevTools Network check for completeness. If you want a fast automated read across a list of URLs, StackOptic runs these same server-side checks for you. You can also read our deeper walkthrough on how to find out what analytics a website uses and the broader guide on how to find out what technology a website uses.

Key Features

Matomo offers feature parity with the major commercial analytics platforms, plus a few capabilities that depend directly on its self-hosted, data-owned model.

• 100% data ownership. With the self-hosted edition, every record lives in your own database. No data is shared with advertising networks, and you decide retention policies.
• No data sampling. Reports are computed from the full dataset, so large sites never see the approximations that sampled platforms introduce.
• Visitor logs and visitor profiles. Unlike strictly aggregate tools, Matomo can show individual (pseudonymized) visit logs, useful for debugging funnels and understanding session-level behavior.
• Goals, events, and e-commerce tracking. Conversion tracking, custom events, and full e-commerce reports (product views, add-to-cart, revenue) are built in.
• Heatmaps, session recordings, and A/B testing. Available as premium features or plugins, bringing behavior analytics into the same platform.
• Built-in consent manager and anonymization. IP anonymization, do-not-track support, configurable cookie-less tracking, and a consent API help with GDPR and similar regulations.
• Tag Manager and Marketplace. A native tag manager plus a plugin marketplace for extending functionality.
• Roll-up and multi-site reporting. Aggregate metrics across many properties in one view.
• Importable Google Analytics data. Migration tooling helps teams move historical data in.

Pros and Cons

Pros

• Full control and ownership of analytics data, ideal for compliance and data-residency requirements.
• Open-source codebase (GPL) that can be audited and extended.
• No sampling and complete, granular reporting.
• Strong privacy tooling, including a cookie-less measurement mode that can avoid consent banners in some jurisdictions.
• Flexible deployment: self-host for free, or use Matomo Cloud for a managed experience.

Cons

• Self-hosting requires server resources and ongoing maintenance (PHP, MySQL, updates, backups).
• Reporting on very high-traffic sites needs careful archiving configuration to stay fast.
• The interface, while comprehensive, can feel dense compared to streamlined privacy tools.
• Some advanced features (heatmaps, A/B testing, some funnels) are paid add-ons rather than core.
• Matomo Cloud pricing scales with traffic, which can become significant for large sites.

Matomo vs Alternatives

Matomo competes both with the dominant free platform (Google Analytics 4) and with a wave of lightweight privacy-first tools. The core trade-off is depth and ownership versus simplicity and zero maintenance.

Platform	Hosting model	Data ownership	Depth of analysis	Best for
Matomo	Self-host or cloud	Full (self-host)	High (logs, funnels, e-commerce)	Privacy-conscious teams needing full features and ownership
Google Analytics 4	Vendor cloud (free)	Vendor-controlled	Very high (event model, BigQuery)	Teams in the Google/ads ecosystem wanting free, deep analytics
Mixpanel	Vendor cloud	Vendor-controlled	Very high (product analytics)	Product teams focused on events, funnels, and retention
Plausible / Fathom	Cloud or self-host	Full (self-host)	Light (essential metrics)	Sites wanting simple, cookie-less, consent-free stats

Compared with Google Analytics 4, Matomo trades GA4's free hosting and machine-learning extras for data sovereignty and unsampled reports. Compared with product-analytics platforms like Mixpanel, Matomo is broader (traffic, marketing, and e-commerce reporting) but less specialized in deep event funnels and cohorts. Against ultralight privacy tools, Matomo offers far more features at the cost of more setup.

Common Use Cases

• Regulated industries and the public sector. Government bodies, healthcare, and education adopt Matomo to keep citizen and student data within their own infrastructure and legal jurisdiction.
• GDPR-driven migrations. Organizations leaving Google Analytics for compliance reasons use Matomo to retain rich analytics while controlling data processing.
• Agencies managing many clients. Roll-up reporting and multi-site management make Matomo a fit for agencies that need consolidated dashboards.
• E-commerce measurement with privacy. Stores track revenue, products, and funnels without sharing customer behavior with ad networks.
• Internal and intranet analytics. Because it self-hosts, Matomo can measure private or internal applications that should never call out to external vendors.

Frequently Asked Questions

Is Matomo really free?

The self-hosted edition of Matomo is free and open source under the GPL license; you only pay for the server you run it on and for any premium plugins you choose to add. Matomo Cloud is a paid, managed alternative billed on traffic. Many teams start self-hosted to avoid recurring costs, then evaluate Cloud if they would rather not maintain infrastructure.

How can I tell if a site is using Matomo or the older Piwik?

Both share the same fingerprints because Matomo was formerly called Piwik. Look for matomo.js/piwik.js, the global _paq array, requests to matomo.php or piwik.php, and cookies like MATOMO_SESSID and _pk_id. Older installations are more likely to use the piwik file and cookie names, while newer ones use matomo.

Does Matomo need cookie consent banners?

It depends on configuration and jurisdiction. Matomo offers a cookie-less tracking mode and IP anonymization that, in some regions, allow measurement without a consent banner. By default Matomo can set first-party cookies, in which case standard consent rules apply. Always confirm with your own legal guidance.

Is Matomo GDPR compliant?

Matomo is designed with GDPR in mind and provides anonymization, a consent manager, data-retention controls, and the ability to keep all data on your own servers. When self-hosted, no visitor data leaves your infrastructure, which simplifies compliance. Compliance ultimately depends on how you configure and operate the platform.

How accurate is automated Matomo detection?

Automated tools like Wappalyzer, BuiltWith, and StackOptic are reliable when the tracker ships in the page HTML or loads from a recognizable Matomo domain. They can miss installs where the tag is injected by a tag manager after page load, or where the tracker is heavily renamed and proxied. For certainty, combine automated detection with a manual DevTools Network and Console check.

Can Matomo data be sampled like some cloud analytics tools?

No. One of Matomo's defining characteristics is that reports are computed from the full dataset, not from a statistical sample. Cloud platforms sometimes sample data on high-traffic properties to keep queries fast, which can introduce small inaccuracies in long-tail segments. Because Matomo keeps every raw record in your own database and aggregates it through archiving, you can always drill into the complete, unsampled data, which is why analysts who need exact numbers for low-volume segments often prefer it.

What is the difference between Matomo Cloud and self-hosted Matomo?

Self-hosted Matomo is the free, open-source edition you install on your own PHP/MySQL server, giving you complete data ownership and responsibility for maintenance, updates, and scaling. Matomo Cloud is a managed service hosted by the Matomo team, billed on traffic, where infrastructure and upkeep are handled for you. The feature sets are largely aligned, so the decision usually comes down to whether you prefer control and zero licensing cost (self-host) or convenience without server management (Cloud).