Open data & tools

Matomo, Plausible and Umami next to AdSense: what they measure, consent and licences

Last updated Published By the editorial team6 min5 sources

Key takeaways

  • Matomo is licensed under the GNU GPL v3 or later, Plausible Community Edition under the GNU AGPL v3 or later, and Umami under the MIT licence.
  • Plausible and Umami both state that they work without cookies; Matomo uses cookies by default but can run cookieless with _paq.push(['disableCookies']).
  • Plausible Community Edition is released twice per year and lacks some Plausible Cloud features such as funnels, ecommerce revenue goals, SSO and the sites API.
  • None of these tools imports AdSense earnings; the AdSense Management API can report earnings by PAGE_URL, which you can join with analytics pageviews by path.
  • A cookieless analytics tool does not remove the consent requirements that apply to AdSense ads themselves.
Attendees at the FOSDEM open-source software conference
Image: Fosdem 2026 - 17,Benjamin Bellamy,CC BY-SA 4.0,via Wikimedia Commons.

Matomo, Plausible and Umami are open-source analytics tools you can run next to AdSense to see traffic, sources and top pages without sending visitor data to a third party. They do not replace AdSense reports, cannot import earnings, and a cookieless analytics setup does not remove the consent your ads need. Choose by licence, hosting effort and how much detail you need.

Quick comparison

Matomo Plausible Community Edition Umami
Licence (as stated by the project) GNU GPL v3 or later GNU AGPL v3 or later MIT
Cookies yes by default; can be disabled none (vendor statement) none (vendor statement)
Stack PHP 8.1+ and MySQL 8.0+ or MariaDB 10.6+ Docker Compose with ClickHouse (2 GB RAM recommended) Node.js 20.19+ and PostgreSQL 12.14+
Latest release seen (Nov 2026) 5.14.3 (Nov 16, 2026) twice-yearly CE releases v3.5.0 (Nov 12, 2026)
Best for detailed analytics, GA-like reports simple traffic dashboards product-style analytics, small footprint

Licence details come from each repository: Matomo’s LEGALNOTICE says its licence “is GNU General Public License v3 or later”, the plausible/analytics repository carries the AGPL v3 text, and Umami’s repository is MIT. Note that the separate plausible/community-edition repository, which holds the Docker setup, is MIT-licensed; the analytics software itself is AGPL.

What does each tool measure?

All three record pageviews, visitors, referrers, campaigns (UTM parameters), countries, devices and custom events. The differences that matter for an AdSense site:

Matomo

Closest to Google Analytics: sessions, goals, ecommerce, segments, heatmaps through plugins. By default it sets first-party cookies to recognise returning visitors. Matomo’s cookieless FAQ explains how to turn them off by adding one line before trackPageView:

var _paq = window._paq = window._paq || [];
_paq.push(['disableCookies']);
_paq.push(['trackPageView']);

The FAQ adds three caveats: tracking still runs, report accuracy for returning visitors may drop, and a few non-analytics cookies such as MATOMO_SESSID, mtm_consent or _pk_testcookie may still be created.

Plausible Community Edition

The self-hosting page states that CE is “published twice per year”, is community-supported only, uses basic bot filtering (Cloud adds data-center IP exclusions), and lacks marketing funnels, user journeys, ecommerce revenue goals, SSO, the sites API and the Data Studio connector.

The data policy explains the counting method: each request gets a daily identifier hashed from a daily salt, the site domain, the IP address and the User-Agent; the salt is rotated and deleted every 24 hours, and raw IPs and User-Agents are not stored. So unique visitors are counted per day, and a visitor returning tomorrow counts as new.

Umami

The Umami documentation describes it as an open-source web and product analytics platform that works “without cookies, cross-site tracking, or the automatic collection of personal data”. The README lists the requirements: Node.js 20.19 or later (22 LTS recommended) and PostgreSQL 12.14 or later, with official Docker images.

Two separate questions:

  1. Does your analytics tool need consent? It depends on the tool’s configuration, your jurisdiction and your regulator’s guidance. Plausible and Umami state they use no cookies, and Plausible states that no consent banner is needed for its analytics. Treat those as vendor statements, check them against your local rules, and remember that custom events and properties you add can change the analysis.
  2. Do your AdSense ads need consent? That is governed by the law and by Google’s own requirements, which do not change because your analytics are cookieless. For EEA, UK and Swiss traffic, read Google’s certified CMP requirement and the Privacy & messaging tool.

A practical consequence: if you already show a certified CMP for ads, you can configure analytics to respect the same consent choice, or run it in a cookieless mode for everyone. Do not assume cookieless analytics lets you remove the consent message.

How do I connect analytics with AdSense revenue?

None of the three tools has an AdSense connector. The clean approach is a join on page path:

  1. Export pageviews per path from your analytics (all three have CSV export and an API).
  2. Get earnings per page from AdSense. The AdSense Management API offers a PAGE_URL dimension (“URL of the page upon which the ad was served”, including scheme and query parameters), plus DOMAIN_NAME, URL_CHANNEL_NAME and COUNTRY_CODE.
  3. Normalise URLs (strip scheme, host and query strings) and join on the path.
  4. Compute your own revenue per 1,000 analytics pageviews per page or template.

Expect mismatches. Analytics pageviews and AdSense page views are counted by different systems, with different bot filtering and ad blocker effects. Use the join to rank pages, not to audit AdSense. For definitions of the AdSense side, see page RPM vs impression RPM and the AdSense reports guide.

Sending your own events: one example per tool

Custom events are where these tools become useful for an ad-supported site: newsletter sign-ups, outbound affiliate clicks, internal search, or Core Web Vitals values. The documented syntax for each:

// Matomo: category, action, name, value (value is a number)
_paq.push(['trackEvent', 'WebVitals', 'CLS', location.pathname, 0.12]);

// Plausible: event name plus custom properties
plausible('WebVitals', { props: { metric: 'CLS', rating: 'needs-improvement' } });

// Umami: event name plus a data object
umami.track('web-vitals', { metric: 'CLS', value: 0.12 });

The Matomo order (category, action, name, value) comes from its event tracking FAQ; the Plausible form from its custom properties documentation; the Umami signature umami.track(event_name, data) from its tracker functions page. The values above are placeholders, not measurements.

Keep event payloads free of personal data: no email addresses, no full URLs with query strings, no user IDs you have not disclosed. Plausible’s documentation mentions a limit of 30 properties per event when properties are set with HTML class attributes.

How to choose in three questions

  1. Do you need sessions, goals and segments similar to Google Analytics? Matomo is the most complete of the three, at the cost of a heavier server and cookies unless you disable them.
  2. Do you want one dashboard page you will actually read? Plausible and Umami show the essentials (pages, sources, countries, devices) on one screen. For most content sites that is enough to decide what to write next.
  3. Who maintains the server? Self-hosting means updates, backups and monitoring. If nobody will do that, a hosted plan from the same vendor, or Google Analytics linked to AdSense, is safer than an abandoned instance.

Licences matter mostly if you redistribute or modify the software. MIT (Umami) lets you do almost anything with attribution; GPL and AGPL (Matomo, Plausible) require you to share modifications under the same licence, and the AGPL extends that to software offered over a network.

Can I track ad clicks in my analytics?

You cannot reliably track clicks inside AdSense ads, because ads render in cross-origin iframes. Do not try to work around that with overlays or click listeners on ad containers: anything that interferes with ad behaviour risks policy problems. Track what you own (outbound links, scroll depth, internal search) and leave ad clicks to AdSense reports.

Performance cost

A self-hosted analytics script is one more request on pages that already load ad code. Keep it small and asynchronous, serve it from your own domain, and check its main-thread cost with Lighthouse. If you also collect Core Web Vitals, send them as custom events to the same tool rather than adding another collector (web-vitals RUM).

Common mistakes

  • Expecting analytics visitors to match AdSense page views. Different counting, different filtering.
  • Running two analytics tools that both set cookies and documenting only one in the privacy policy. Your privacy policy must reflect what actually runs.
  • Never updating a self-hosted instance. An outdated analytics server on your domain is a security risk; Matomo shipped 5.14.3 two days before this guide was written.
  • Calling a tool “GDPR compliant” on your site because the vendor does. Compliance depends on how you use it.
  • Exposing the analytics dashboard publicly with data you did not mean to share.

Open-source tools mentioned

ToolLicence
MatomoGPL-3.0-or-later
Plausible Analytics (Community Edition)AGPL-3.0-or-later
UmamiMIT

Frequently asked questions

Can I use Matomo, Plausible or Umami instead of Google Analytics with AdSense?

Yes, for audience analytics. AdSense does not require Google Analytics; linking the two is optional. What you lose is the built-in AdSense integration in GA4, so revenue per page has to come from AdSense reports or the AdSense Management API and be joined with your analytics data by page path.

If my analytics are cookieless, do I still need a consent banner?

For AdSense ads, almost certainly yes in regulated regions, because the ads themselves use cookies and identifiers and Google sets its own consent requirements for EEA, UK and Swiss traffic. A cookieless analytics tool only changes the analysis for the analytics part. Plausible states that no consent banner is needed for its analytics, but that is the vendor's claim about its own tool, not about your ads.

Which of the three is easiest to self-host?

Umami's README lists a Node.js server (20.19 or later, 22 LTS recommended) and PostgreSQL 12.14 or later, and ships a Docker Compose file. Plausible Community Edition runs with Docker Compose and ClickHouse, and its README recommends at least 2 GB of RAM. Matomo needs PHP 8.1 or later and MySQL 8.0 or later or MariaDB 10.6 or later. All three need you to handle updates, backups and security.

Does the AGPL licence of Plausible CE affect my website's code?

The AGPL applies to the Plausible software, including modifications you make to it and offer over a network. Running an unmodified copy to analyse your own site does not put your website's code under the AGPL. If you modify Plausible and expose it to users, read the licence text carefully or ask a lawyer.

Sources

  1. How do I go cookieless (disable Matomo cookies) for a visitor? · Matomo
  2. Plausible: Self-Hosted Google Analytics alternative · Plausible Analytics
  3. Plausible data policy · Plausible Analytics
  4. Introduction - umami · Umami
  5. AdSense Management API: Dimension reference · Google for Developers