Matomo Tag Manager

What Is Matomo Tag Manager?

Google Tag Manager is the default choice for deploying tracking scripts on the web. It is free, well-documented, and supported by an enormous community of developers and marketers. It is also a Google product — which means every tag container you deploy establishes a data connection to Google's infrastructure, even if the tags inside it point elsewhere. For organisations that have spent considerable effort removing Google Analytics for GDPR reasons, continuing to use GTM creates an uncomfortable contradiction.

Matomo Tag Manager exists to resolve that contradiction. Released in 2019 as a module within the Matomo Analytics platform, it provides a free, open-source tag management system that you can self-host alongside your analytics. Tags, triggers, and variables work similarly to GTM. But the fundamental difference is architectural: when self-hosted, Matomo Tag Manager sends zero data to any third party. The tag manager itself collects nothing. It is a deployment mechanism, not a data collection mechanism.

The trade-off is real and significant. Matomo Tag Manager has a fraction of GTM's template library, a smaller community, fewer tutorials, and a less polished preview/debug experience. It requires a Matomo installation to run — you cannot use it as a standalone tag manager. For teams already running Matomo Analytics, the tag manager is a natural extension. For teams that want a privacy-first tag manager without committing to the full Matomo ecosystem, the dependency is a meaningful limitation.

Still, for the growing number of organisations that need tag management without Google's data footprint, Matomo Tag Manager is the most complete open-source option available.

Key Features

Tag, Trigger, and Variable System

Matomo Tag Manager follows the familiar GTM paradigm: tags define what to execute (tracking scripts, pixels, custom code), triggers define when to execute (page views, clicks, form submissions, scroll depth, timers), and variables provide dynamic data to tags (page URL, referrer, custom data layer values). The visual editor for creating and configuring these elements is clean and intuitive, though it offers fewer pre-built templates than GTM. The conceptual model will be immediately familiar to anyone who has used Google Tag Manager, reducing the learning curve for migration.

Custom HTML Tags

While the built-in tag template library is limited — covering Matomo Analytics, basic tracking pixels, and a handful of third-party services — the custom HTML tag type accepts any JavaScript or HTML snippet. This means you can deploy Facebook Pixel, LinkedIn Insight Tag, live chat widgets, A/B testing scripts, or any other third-party service through custom tags. The flexibility is there; it simply requires manual configuration rather than selecting from a template dropdown. For teams with a small number of tags, this is a minor inconvenience. For teams managing dozens of tags across multiple sites, the lack of templates becomes a productivity drag.

Version Control and Publishing

Every change to a Matomo Tag Manager container is versioned. You can create new versions, compare changes between versions, and roll back to previous configurations if a deployment causes issues. The publish workflow requires explicit action — changes are not live until you publish — which provides a safety net against accidental deployments. Container export and import allow you to replicate configurations across multiple Matomo instances, useful for organisations managing staging and production environments.

Preview and Debug Mode

Before publishing changes, you can enter a preview mode that shows which tags fire, which triggers activate, and which variables resolve on each page. This is essential for verifying that new tags work correctly before they go live. The preview interface is functional but noticeably less refined than GTM's Tag Assistant, which provides richer debugging information and a more intuitive visual presentation. For complex debugging scenarios with many interacting tags, the Matomo preview mode can feel limited.

Deep Matomo Analytics Integration

The tightest integration is naturally with Matomo Analytics itself. Matomo tracking tags in the tag manager automatically feed data into your Matomo dashboards, goals, and segments. Changes to your Matomo tracking configuration — adding custom dimensions, modifying event tracking, enabling heatmaps — can be managed through the tag manager without touching site code. This seamless data flow between tag management and analytics is something GTM achieves with Google Analytics but that no other privacy-first combination matches as cleanly.

Pricing

Matomo Tag Manager is entirely free. On a self-hosted Matomo installation, the tag manager is a built-in module with no additional cost, no usage limits, no premium gating, and no restrictions on the number of tags, containers, or websites. You can create unlimited containers, deploy unlimited tags, and manage unlimited sites — all for the cost of your Matomo hosting infrastructure.

On Matomo Cloud, the tag manager is included in all subscription tiers starting at approximately EUR 23 per month. The cloud subscription covers Matomo Analytics and Tag Manager together, with no separate tag management fee.

There is no scenario where Matomo Tag Manager costs more than free (for self-hosted) or is an add-on cost (for cloud). This makes it the most cost-effective tag management solution available — provided you are already running or willing to run Matomo.

The hidden cost is the Matomo dependency. If you do not use Matomo Analytics, you must install and maintain a Matomo instance solely to use the tag manager. For organisations using a different analytics tool (Plausible, Pirsch, or even a privacy-configured GA4), this overhead may not be justified.

EU Compliance & Privacy

Matomo Tag Manager achieves a perfect EU compliance score in our assessment, and for good reason. When self-hosted, the tag manager operates entirely within your infrastructure. It sets no cookies of its own, sends no data to external servers, and performs no tracking. It is purely a mechanism for deploying and managing scripts — the compliance profile of each deployed tag depends on the tag itself, not on the tag manager.

This architectural approach means that the tag management layer introduces zero additional compliance concerns. Compare this to GTM, where the container script itself makes requests to Google's servers on every page load, regardless of what tags are inside it. Even an empty GTM container establishes a data connection to Google.

The open-source codebase (GPL licence) allows full security auditing, which is a requirement for some public sector and regulated industry deployments. You can verify exactly what the tag manager does and does not do by inspecting the source code.

For organisations that have invested in GDPR compliance by adopting Matomo Analytics, the tag manager completes the picture: a fully sovereign analytics and tag management stack with no third-party data flows.

Who It's Best For

Organisations already using Matomo Analytics who want tag management that integrates seamlessly without introducing Google into their privacy-respecting analytics stack.

Public sector and regulated industry teams that require auditable, self-hosted tag management with no external data flows and open-source transparency.

Privacy-first website operators who have removed Google Analytics and want to remove Google Tag Manager as the next step in eliminating Google's data footprint.

Small to medium websites with a manageable number of tags that do not require GTM's extensive template library or community ecosystem.

The Verdict

Matomo Tag Manager is the best privacy-first tag management solution available — with the caveat that it only works within the Matomo ecosystem. If you already use Matomo, adding the tag manager is an obvious decision: it is free, deeply integrated, and eliminates the last Google dependency in your analytics stack. If you do not use Matomo, the dependency is a real barrier. The 7.5 overall score reflects outstanding value (9.5) and unmatched EU compliance (10.0), balanced against a limited template ecosystem (5.5 integration score) and the Matomo-only requirement.

Frequently Asked Questions

Can I migrate from Google Tag Manager to Matomo Tag Manager?

There is no automated migration tool. You will need to recreate your tags, triggers, and variables manually in Matomo Tag Manager. For simple setups with a few tags, this takes an hour. For complex GTM containers with many custom triggers and data layer integrations, the migration requires careful planning and testing.

Does Matomo Tag Manager work with non-Matomo analytics tools?

Yes. You can deploy any analytics or tracking script through custom HTML tags, including Plausible, Fathom, or even Google Analytics. The Matomo dependency is for running the tag manager platform — the tags themselves can point to any service.

Is the preview mode reliable for testing?

The preview mode works correctly for basic tag firing verification. It shows which tags fired, which triggers matched, and variable values. However, for complex debugging — race conditions between tags, data layer timing issues, or cross-domain tracking — the experience is less robust than GTM's Tag Assistant. Testing in a staging environment before publishing is strongly recommended.

How does Matomo Tag Manager affect page load speed?

The Matomo Tag Manager container script is lightweight and loads asynchronously, so its impact on page performance is minimal. The actual performance impact depends on the tags you deploy within it — a container full of heavy third-party scripts will slow your page regardless of which tag manager delivers them.

Can I use Matomo Tag Manager for consent management?

Matomo Tag Manager can implement basic consent logic using triggers that check for consent cookies or data layer variables before firing tags. However, it is not a consent management platform. For full consent management with cookie banners and preference centres, you should pair it with a dedicated CMP like Cookiebot or Usercentrics, deployed through the tag manager itself.