We self-host Matomo today. How does a switch change operational ownership?

Then the decision is operating strategy, not a missing checkbox. With Prelumen Analytics, infrastructure, updates, and plugin lifecycle leave your environment. That can reduce maintenance and attack surface in your environment, but it also means your team no longer runs the analytics stack itself.

We track goals and ecommerce in Matomo today. What happens to that?

Revenue arrives once your payment provider is connected and then sits directly on top of traffic: purchases attributed by source, page and campaign, in realtime and without cookies. Micro-conversions run as custom events, funnels show drop-off per step, and aggregated form friction shows where forms break down.

Does Prelumen Analytics match Matomo plugin extensibility?

The model is different. What often arrives as add-on plugins in Matomo — funnels with per-step drop-off, aggregated form friction, custom events and revenue attribution by source, page and campaign — ships as part of the product in Prelumen Analytics, as does diagnostics for quality, security, accessibility, privacy and carbon. Session replay and heatmaps are not included. If your current value hinges on exactly that kind of plugin, validate parity before switching.

Do we need a separate stack for server-side campaign feedback?

No. Customer-owned CAPI delivers selected conversion signals server-side to your own destinations: the Meta Conversions API, plus Google Enhanced Conversions or Data Manager. It is off by default and delivers only with an active destination, explicit event mapping, passing DNT/GPC and consent checks, supported identifiers and valid credentials; event_id deduplication and delivery diagnostics are part of it. It is not a tag management or server-side GTM replacement.

Can we keep our raw-data ownership expectations?

Prelumen Analytics processes data on managed EU infrastructure with documented processing terms. The data is yours, stays in the analytics context and is not passed to ad networks; access to traffic, check, compliance, carbon and issue data runs through the REST API and MCP on selected plans. Self-host-level raw-data ownership is a Matomo-specific architectural choice and does not carry over directly. If that ownership model is non-negotiable, keep it as an explicit architecture requirement.

How do we justify a switch to stakeholders who chose Matomo for privacy reasons?

Both products are privacy-first. Prelumen Analytics is cookie-free in its default mode, respects Do-Not-Track and processes data in the EU. The difference is operating model: Matomo prioritises in-house stack ownership; Prelumen Analytics prioritises managed execution with less customer-side code, infrastructure, and attack surface. Frame the decision as stack ownership vs operational focus, not as a privacy tradeoff.

Matomo Alternative

With Matomo the analytics stack is yours. Prelumen measures revenue in realtime and runs the stack for you.

Matomo delivers analytics to run yourself or as a managed cloud. Prelumen connects realtime revenue attribution, funnels and aggregated form friction with recurring audits, issue tracking and verifiable proof in one managed EU-hosted system.

Start where you can stay.

Analytics history rarely moves cleanly between products. Start free with the system that already has the next layer built in: revenue attribution and funnels as well as audits, issues and verifiable proof when you need them.

Free isn’t a trial mode. It’s the product, in small.

Start for free Plans and Pricing

Choose by fit

Both can support privacy-oriented measurement. The difference is the operating model, and how much of revenue, conversion delivery and website diagnostics sits inside the same product.

Prelumen Analytics is a fit when

Revenue, funnels and conversion signals should sit in the same surface as traffic and website quality.
You want analytics and website diagnostics managed in one platform instead of running infrastructure and plugin lifecycle yourself.
Your teams need faster handoff from finding to fix.
You want the tracking script to stay small: selectable profiles from 1.037 KB gzip, plus Core Web Vitals from real usage.

Matomo is a fit when

Self-hosted analytics ownership is a deliberate strategic requirement.
You intentionally run plugin-driven extensibility in your stack.
Your team is ready to own analytics infrastructure, application updates, and extension lifecycle permanently.

Capability comparison

Compare on measurement depth, server-side activation, operating model and follow-through.

Focus area	Prelumen Analytics	Matomo
Operating model	Managed platform: analytics, diagnostics and issue flow in one product	Analytics platform you run self-hosted yourself, or take as a managed cloud
Revenue and conversion	Revenue by source, page and campaign in realtime once your payment provider is connected; funnels, custom events, form friction	Goals, ecommerce reporting, funnels and form analytics, partly via add-on plugins
Server-side conversion delivery	Customer-owned CAPI: selected mapped events to your own Meta or Google destinations, off by default, with consent and DNT/GPC gating	Delivery to ad platforms via plugins and your own server integrations
Hosting model	Managed EU platform; your data is yours, stays in the analytics context and is not passed to ad networks	Self-hosting governance with raw data in your own stack, or the managed cloud
Privacy baseline	Cookie-free default, EU processing and hosting, DNT/GPC respected by default	Privacy controls and raw-data ownership, fully in your hands when self-hosted
AI agent access	Native MCP server across traffic, check, compliance, carbon and issue data, on selected plans	Agent access through the reporting APIs
API surface	REST API + MCP on selected plans	Tracking and reporting APIs, extensible via plugins
Diagnostics scope	Built-in checks for quality, security, accessibility, privacy, SEO/GEO, content and carbon, as subscriptions on fixed intervals	Analytics-side diagnostics, extended via plugins and adjacent tools
Action after insight	Every finding becomes an issue with incident alerts: weighted by page hits from the last 30 days and resolved or ignored across every affected URL in one step	Reporting and findings feed into your own process and ticketing systems
Best-fit profile	Teams consolidating revenue measurement, website quality and follow-through in one managed system	Teams prioritizing self-host-first analytics architecture

Decision guide

Pick by required measurement depth, activation needs and operating constraints.

Choose Prelumen

when revenue, conversion signals and remediation should live in the same managed system.

Choose Matomo

when owning the analytics stack yourself is a strategic requirement.

Decide by maintenance and attack-surface ownership

when both products fit and the customer-side code and infrastructure surface differs between teams.

Frequently Asked Questions

We self-host Matomo today. How does a switch change operational ownership?: Then the decision is operating strategy, not a missing checkbox. With Prelumen Analytics, infrastructure, updates, and plugin lifecycle leave your environment. That can reduce maintenance and attack surface in your environment, but it also means your team no longer runs the analytics stack itself.
We track goals and ecommerce in Matomo today. What happens to that?: Revenue arrives once your payment provider is connected and then sits directly on top of traffic: purchases attributed by source, page and campaign, in realtime and without cookies. Micro-conversions run as custom events, funnels show drop-off per step, and aggregated form friction shows where forms break down.
Does Prelumen Analytics match Matomo plugin extensibility?: The model is different. What often arrives as add-on plugins in Matomo — funnels with per-step drop-off, aggregated form friction, custom events and revenue attribution by source, page and campaign — ships as part of the product in Prelumen Analytics, as does diagnostics for quality, security, accessibility, privacy and carbon. Session replay and heatmaps are not included. If your current value hinges on exactly that kind of plugin, validate parity before switching.
Do we need a separate stack for server-side campaign feedback?: No. Customer-owned CAPI delivers selected conversion signals server-side to your own destinations: the Meta Conversions API, plus Google Enhanced Conversions or Data Manager. It is off by default and delivers only with an active destination, explicit event mapping, passing DNT/GPC and consent checks, supported identifiers and valid credentials; event_id deduplication and delivery diagnostics are part of it. It is not a tag management or server-side GTM replacement.
Can we keep our raw-data ownership expectations?: Prelumen Analytics processes data on managed EU infrastructure with documented processing terms. The data is yours, stays in the analytics context and is not passed to ad networks; access to traffic, check, compliance, carbon and issue data runs through the REST API and MCP on selected plans. Self-host-level raw-data ownership is a Matomo-specific architectural choice and does not carry over directly. If that ownership model is non-negotiable, keep it as an explicit architecture requirement.
How do we justify a switch to stakeholders who chose Matomo for privacy reasons?: Both products are privacy-first. Prelumen Analytics is cookie-free in its default mode, respects Do-Not-Track and processes data in the EU. The difference is operating model: Matomo prioritises in-house stack ownership; Prelumen Analytics prioritises managed execution with less customer-side code, infrastructure, and attack surface. Frame the decision as stack ownership vs operational focus, not as a privacy tradeoff.