Analytics & CRO
Before switching to Matomo’s premium plugins, our analytics stack was Hotjar for heatmaps and session recordings, a separate A/B testing platform, and GA4 for everything else. Three tools, three billing relationships, data siloed across all of them. The business case for consolidating onto Matomo premium plugins wasn’t a hard sell — the cost comparison did most of the work.
This is a practical walkthrough of what each plugin actually delivers, where it adds value over standalone tools, and where the limitations are. For teams already running Matomo on-premise, the premium plugins extend the core installation without adding external data dependencies.
Heatmaps and session recordings
This is where most teams start when evaluating Matomo against Hotjar. The functionality is comparable: click maps, scroll maps, move maps, and session recordings with the ability to replay individual user journeys. The material difference is data ownership — Hotjar sends behavioural data to Hotjar’s servers. Matomo keeps it in your infrastructure.
For an OTA with European users, that matters. Hotjar has its own consent requirements under GDPR; session recordings capture enough detail about user behaviour that the legal position is genuinely complex. Moving to Matomo’s heatmap and session recording plugin removed that complexity entirely.
In practice, I’ve used heatmap data most usefully to resolve design disagreements — not to validate UX hypotheses (that’s what A/B testing is for), but to establish actual behaviour when two teams have conflicting assumptions. Which CTA is getting clicked. Where users stop on the search results page. What the scroll depth looks like on long-form content. These are questions that can end a product review debate if the data is available.
Form analytics
Matomo’s Form Analytics plugin tracks how users interact with every form field: which fields cause drop-off, where hesitation happens, how long users spend before completing or abandoning. For a booking flow or checkout, this is high-value data that standard event tracking doesn’t capture without significant custom implementation.
On our platform, form analytics surfaced a problem we hadn’t anticipated: a date-picker in the search flow had an unusually high abandonment rate. Not because users weren’t engaging — field interaction data showed high start rates — but because a specific combination of mobile device and browser was causing an error that hadn’t appeared in QA testing. Form Analytics showed where the drop-off was and which user segment it affected. Finding the problem didn’t require engineering. Fixing it did.
A/B testing
Matomo’s A/B Testing plugin lets you run experiments using your own visitor data to measure outcomes. The setup is straightforward: define the experiment, set the traffic split, specify the goal metric, and run until statistical significance is reached.
The advantage over standalone tools is integration — experiment results connect directly to your Matomo conversion data without stitching together reports from two systems. The limitation is volume: Matomo’s A/B testing works well for high-traffic pages where you can reach significance in a reasonable timeframe. For lower-traffic pages or micro-segments, test duration stretches to the point where results become practically unusable.
Campaign tracking and content tracking
Campaign tracking in Matomo uses UTM parameters compatible with GA4 conventions to attribute sessions to marketing campaigns. The Marketing Campaigns Reporting plugin extends this with cross-channel visibility — email, paid, organic, social — in a unified report. For teams that have spent time manually reconciling campaign data across multiple tools, having a single source of truth has a straightforward operational value.
Content tracking is more niche but useful in specific contexts: it measures how often a content block — banner, CTA, product card — is displayed versus interacted with. Impressions against interactions, calculated as an interaction rate, without custom event implementation.
Is the cost worth it?
Matomo’s premium plugins are sold as a bundle or individually, with pricing based on number of users. For teams already paying for Hotjar Business, a separate A/B testing tool, and a form analytics platform, the consolidated cost is usually lower — and you gain data ownership on top.
The honest caveat: the individual plugins don’t always match the polish of category-specialist tools. Hotjar’s UX is better than Matomo’s heatmap interface. Optimizely has more sophisticated experiment configuration than Matomo’s A/B plugin. If any one of these capabilities is central to your work rather than supplementary, the specialist tool is probably the right call.
For teams where these capabilities are supporting functions — where data ownership, cost consolidation, and a unified analytics environment matter more than best-in-class UX in each tool — the premium bundle is a sensible choice. That was the calculation I made, and it’s held up.
