Matomo Analytics plugin review and common issues

Matomo stores detailed tracking data including log-level visitor records, which grows rapidly on high-traffic sites. Steps: (1) go to Matomo → Privacy → Data Retention and reduce the retention period for raw log data (14-30 days is typical, keeping aggregated reports longer); (2) enable archive processing via server-side cron job rather than on page load; (3) disable heatmaps and session recordings if not actively used — they generate disproportionate data volume. For sites with over 50,000 monthly visits, a dedicated database server for Matomo is recommended.

Use browser DevTools Network tab to confirm the tracking request fires — filter for “matomo.php” or “piwik.php” requests. If no request appears: (1) ensure the Matomo plugin is active and tracking is enabled in WordPress → Matomo → Tracking; (2) check if a security plugin is blocking the Matomo tracking script — add an exclusion if needed; (3) verify the Matomo URL configured in the plugin points to your actual Matomo installation.

Discrepancies between Matomo and GA4 are normal and expected. Matomo On-Premise typically shows higher visitor counts because it captures visits that ad blockers and browser privacy settings cause GA4 to miss. Differences in session timeout definitions, bot filtering logic, and unique visitor identification methods also contribute. Neither number is definitively correct — they measure slightly different things with different methodologies.

Matomo WordPress plugin includes WooCommerce ecommerce tracking automatically when both plugins are active. Go to Matomo → Settings → Tracking and ensure ecommerce tracking is enabled. Matomo tracks product views, cart additions, and orders as ecommerce events. View results in Matomo → Ecommerce → Overview. For advanced ecommerce reports, ensure the Ecommerce plugin is enabled in Matomo plugin settings.

Heatmaps and session recordings are premium features for On-Premise — they require purchasing the Heatmaps & Session Recordings add-on from marketplace.matomo.org. After purchasing, install the plugin via Matomo Admin → Marketplace. Set sampling rates carefully — recording every session on a busy site generates enormous data volume and impacts performance significantly.

For most analytics use cases, yes. Matomo provides equivalent or superior features to GA4 including event tracking, conversion goals, ecommerce reporting, audience segmentation, and funnel analysis. The primary differences: GA4 includes Google Signals for cross-device audience data and integrates natively with Google Ads. If your advertising is primarily on Google platforms, GA4 integration advantages are meaningful. For sites not heavily invested in Google Ads, Matomo is a complete replacement.

For a small blog with modest traffic (under 10,000 monthly visits), Matomo On-Premise is technically viable but may be more infrastructure than needed. WP Statistics or Site Kit are simpler for basic traffic tracking. Matomo strengths — heatmaps, session recordings, funnel analysis — become valuable as site complexity grows. Start with WP Statistics or Site Kit and move to Matomo when behavioral analysis becomes a priority.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.