Integration & tools · Knowledge
Matomo or Google Analytics – which fits a Joomla site?
GA4 is free, powerful and wired into Google's advertising universe – paid for with data in Google's hands, a hard consent requirement and modelled numbers where consent is refused.
Matomo is the self-hosted counterpart: your data on your server, cookieless and banner-lean operation possible, raw numbers – paid for with a bit of hosting and update duty.
Our recommendation on this site is openly Matomo – the plugin serves both without judging.
The comparison along what a Joomla site actually needs
Fairness first, GA4's real strengths: the integration with Google Ads is unmatched – imported conversions steer bidding, audiences flow into campaigns; a site that spends meaningful Google ad budget will struggle to skip that bridge. Machine-learning insights and the price of zero are real arguments too. The costs in EU practice: GA4 requires prior consent, so every banner refusal punches a hole that Google fills with modelling – you steer partly by estimate; data lives in the Google ecosystem with all the regulatory history that entails; and the report interface has a learning curve that surprises veterans. Matomo mirrors the trade: on your own server (a small PHP/MySQL app next to Joomla, or via a hosting package), measured cookieless with masked IPs, it produces complete raw data with no consent leak – the banner-lean setup this knowledge area describes end to end – and it stays yours: export, retention, deletion under your control. Its price is stewardship – updates, backups, occasional archiving cron care – roughly the same muscle a Joomla site owner already exercises. The decision grid for typical cases: information site, association, company site without ad spend → Matomo, clearly – simpler legals, complete data, sovereignty. Heavy Google Ads engine → GA4 at least alongside, for the conversion bridge. In-between → run Matomo as the system of record; add GA4 only where the ads machinery demands it, cleanly separated in consent. Our openly declared preference is the first case's logic – this very site runs on cookieless Matomo, and JStats carries whichever snippet you choose.
Key facts
- GA4 strengths: free, Google-Ads bridge (conversions, audiences), ML insights.
- GA4 costs: hard consent duty, modelled gaps, data in the Google ecosystem.
- Matomo strengths: data ownership, cookieless banner-lean operation, complete raw numbers.
- Matomo price: self-hosting stewardship – updates, backups, archiving cron.
- Grid: no ad budget → Matomo · heavy Google Ads → GA4 alongside · in-between → Matomo leads, GA4 only where ads demand.
- Plugin stance: JStats carries either snippet – the recommendation is editorial, the tool is neutral.