Matomo vs Google Analytics: privacy-first analytics for your store

Last reviewed June 2026, the EU-US Data Privacy Framework remains the active transfer mechanism for Google Analytics, and the cookieless-Matomo caveat below still depends on your own configuration and jurisdiction. Confirm legal specifics with your DPO.

Google Analytics is the default for a reason: it is free, it is everywhere, and the PrestaShop tutorials all assume it. But "free" has a quieter price, your visitor data flows to Google, where it feeds an advertising business you have no stake in. For a store owner in Germany, Austria or France, that is not a philosophical footnote; it is a compliance question with real legal weight behind it. Matomo (formerly Piwik) is the open-source answer to that question, and on a self-hosted instance it keeps every byte of visitor data on your own server. This post is the honest comparison for one specific decision: which analytics platform should run on your PrestaShop store when privacy and GDPR exposure are part of the calculation.

It is deliberately not a setup tutorial or a metrics primer. If you have already chosen GA4 and want it wired up correctly, follow our GA4 for PrestaShop complete setup guide; if you want to know which GA4 numbers are worth your attention once it's running, see the metrics that actually matter. This page is about the choice that comes before setup.

The real question isn't features. It's where your data lives

Both tools track the same e-commerce events: product views, add-to-cart, checkout steps, purchases, revenue. The difference that should drive your decision is architectural. With GA4, the tracking script ships your visitors' data to Google's servers, where Google acts as a third-party processor under its GA terms (with separate controller roles for some of its own business operations) and uses aggregated signals to improve its advertising products. With self-hosted Matomo, you can keep analytics data on your own infrastructure, if the instance is self-hosted and configured without external services (geolocation, CDN, cloud or third-party plugins), there is no third party, no international transfer, and no data-sharing clause to explain to a customer or a regulator.

That single distinction cascades into three things European merchants actually care about: GDPR exposure, how much of your traffic you are legally allowed to measure, and who ultimately owns the dataset. Everything below follows from it.

GDPR and cookie consent: the part that costs you data

This is where the two platforms diverge most sharply for a PrestaShop store, because the difference shows up directly in how complete your numbers are.

What GA4 requires

GA4 sets cookies and processes personal data (IP addresses, device and browser signals). Under GDPR and the ePrivacy directive, that means the tracking script must not fire until the visitor gives explicit consent. In practice a meaningful share of visitors decline, exactly how many varies by country, audience and how the banner is worded, but a double-digit percentage is common, and in privacy-conscious markets it can be substantial. Those declined visitors simply don't appear in your reports. Google's Consent Mode v2 fills the hole with modelled data, statistical estimates for the visitors who said no, but a modelled figure is an inference, not a recorded fact, and it is worth knowing the difference before you base a decision on it.

On PrestaShop, getting that consent gate right is its own task: the GA4 tag has to be held back until your cookie-consent module reports approval, which is precisely the kind of conditional firing that Google Tag Manager handles cleanly rather than hard-coding into your theme.

Where Matomo changes the maths

Matomo can run in a cookieless mode: IP addresses are anonymised (you can drop the last one or two octets), no persistent cookie is stored, and visitors are not individually identified across sessions. Configured that way, many deployments operate under a "legitimate interest" basis rather than requiring opt-in consent. Which means the tracker can, in principle, measure close to all of your traffic instead of only the consenting fraction. For a store owner that is the headline benefit: analytics you can actually trust because they reflect everyone who visited, not just the people who clicked "accept."

The two settings that earn this are IP anonymisation and disabling the tracking cookie. In Matomo's own tracking code those are explicit calls, and they belong before the page-view is recorded:

<script>
var _paq = window._paq = window._paq || [];
// Anonymise the visitor IP (mask the last two bytes) and run without a cookie.
_paq.push(['setSecondaryTrackerUrl']); // optional, harmless if unused
_paq.push(['disableCookies']);
_paq.push(['trackPageView']);
_paq.push(['enableLinkTracking']);
(function() {
  var u = "https://analytics.yourdomain.com/"; // your self-hosted Matomo URL
  _paq.push(['setTrackerUrl', u + 'matomo.php']);
  _paq.push(['setSiteId', '1']);              // your Matomo site ID
  var d = document, g = d.createElement('script'), s = d.getElementsByTagName('script')[0];
  g.async = true; g.src = u + 'matomo.js'; s.parentNode.insertBefore(g, s);
})();
</script>

IP-byte masking itself is set on the Matomo server side (Administration → Privacy → Anonymize data, where you choose how many bytes of the IP to drop); disableCookies in the tracking code is what removes the persistent cookie. Use both together. One without the other is a half-measure that won't survive scrutiny.

The honest caveat, because this is a legal claim and not a software feature: whether cookieless tracking is lawful without consent depends on your exact Matomo configuration and your jurisdiction's interpretation. Confirm it with your DPO or counsel before you rely on it. We can tell you what the software does; we can't certify your compliance.

The regulatory backdrop you can't ignore

This isn't a hypothetical. Several European data protection authorities, the Austrian DSB, the French CNIL and others, have issued decisions finding specific Google Analytics implementations incompatible with GDPR, on the grounds that they transferred personal data to the US without adequate safeguards. The legal landscape has shifted since (the EU-US Data Privacy Framework now provides a transfer mechanism), and the picture continues to evolve, so don't treat any single ruling as the final word. The durable takeaway for a PrestaShop merchant: if your store serves EU customers, "we use Google Analytics like everyone else" is not automatically a safe position, and keeping data on your own server removes the entire transfer question from the table.

GA4 vs Matomo, head to head

Neither tool is strictly better, they optimise for different things. Here is the comparison that matters for an e-commerce store rather than a generic feature checklist.

Two rows deserve a plain-language gloss. Sampling in GA4 mainly bites in Explorations and ad hoc queries: once those cross a high event-volume threshold, Google computes the figure from a subset of your sessions and extrapolates, fine for trends, frustrating when you're trying to reconcile a specific number. Standard reports are generally unsampled but can still be affected by thresholding and modelling in some cases. Matomo reports on every session, so a figure is a count, not an approximation. And maintenance is the honest cost of ownership: self-hosting Matomo means you are responsible for the server, the upgrades and the backups. A small VPS handles moderate PrestaShop traffic comfortably; busier stores need to size for it. If running infrastructure isn't something you want to own, Matomo Cloud exists as a hosted option, though that reintroduces a processor, so weigh it against the privacy reason you came here for.

Wiring either one into PrestaShop properly

Whichever you choose, the value is only as good as the tracking underneath it, and PrestaShop's e-commerce events are exactly where naive installs fall down. Dropping a bare tracking snippet into your theme's header captures pageviews but misses the events that make analytics worth having: add-to-cart, checkout step progression, and the purchase event with order value and product detail. Those fire at specific points in the order flow, and getting them to send correctly is the difference between "we had some traffic" and "this campaign produced €X in revenue from these products."

This is the gap our analytics integration modules close. The GA4 and Matomo integrations hook into PrestaShop's order and cart flow and fire the relevant GA4 recommended e-commerce events for you, product list views and item views, cart actions, checkout steps, and the purchase event on the order-confirmation page, so revenue and conversion data land in your reports without editing theme files or maintaining custom tracking code through every PrestaShop upgrade. So what does that buy you? Analytics you can act on: which products people actually buy versus merely view, where the checkout leaks, and what a channel is genuinely worth. Instead of a pageview counter that goes stale the next time you update your theme. If you're still deciding which of those e-commerce numbers deserve your attention in the first place, start with what to track and what to ignore.

"But what about heatmaps and session recordings?"

It's a fair question, because it's often where the GA-vs-Matomo debate drifts. Matomo offers heatmaps, session recordings and form analytics as premium plugins; GA4 has no native equivalent at all. But for most PrestaShop stores this shouldn't be the deciding factor between the two, because the strongest behavioural tools are purpose-built and platform-aware. If you want to watch how customers move through your store, that's a job for Microsoft Clarity (free, with recordings and heatmaps) or Hotjar. Run alongside your chosen analytics platform, not in place of it. Keep this decision focused on the thing it's actually about: where your quantitative, GDPR-exposed visitor data lives.

Which should you choose?

Choose GA4 if your store leans on Google Ads and you need the native attribution, if the predictive metrics genuinely inform your decisions, and if you'd rather Google handle all the infrastructure and you're comfortable with the consent-and-transfer trade-offs that come with it.

Choose self-hosted Matomo if you operate in a market where DPA scrutiny of Google Analytics is high (Germany and Austria first among them), if measuring close to 100% of your traffic without a consent wall matters to you, if you want unsampled data and full ownership of the database, and if you're willing to run a small server to get all of that.

Run both if you can't fully give up Google's ecosystem but want clean baseline numbers too, Matomo for privacy-compliant coverage of all visitors, GA4 for the consented audience that feeds Google Ads and the ML features. It's a common setup, the incremental cost is mostly the second integration and a little server overhead, and it gives you both honest totals and Google attribution. With both integrations firing the same PrestaShop e-commerce events, your purchase data stays consistent across the two.

The bottom line

For a European PrestaShop store where privacy and GDPR exposure are real considerations, self-hosted Matomo is the stronger default: it removes the data-transfer question entirely, can measure traffic the consent banner would otherwise cost you, and leaves you owning the dataset. For a store built around Google's advertising stack, GA4 is hard to replace and the trade-offs are worth accepting with eyes open. Either way, the platform is only half the job. The half that pays off is correct PrestaShop e-commerce tracking underneath it, which is exactly the part you shouldn't be hand-coding into a theme. Once the data is flowing honestly, the next step is turning it into money decisions; that's the territory of advanced reporting for store owners.

Frequently asked questions

Can I really run Matomo without a cookie banner?

Sometimes, and that "sometimes" is doing a lot of work. Configured cookieless, with IP anonymisation on and the tracking cookie disabled, Matomo collects far less than GA4 does, and many deployments treat that as a legitimate-interest basis that doesn't require opt-in. But whether that's lawful for your store depends on your exact configuration and your country's interpretation of ePrivacy, so confirm it with your DPO before you remove the banner. The software gives you the privacy-respecting mode; it can't give you legal certainty.

How much server do I need to self-host Matomo for a PrestaShop store?

For moderate traffic, a small VPS handles it comfortably. Matomo is a PHP/MySQL application much like PrestaShop itself, so the resource profile is familiar. The real cost isn't the hardware, it's the ownership: you're responsible for updates, backups, and scaling the database as it grows. Busy stores with high pageview volumes need to size the instance deliberately and keep the archiving cron healthy, or reports start lagging.

Will switching from GA4 to Matomo lose my historical data?

Yes, analytics platforms don't migrate history between each other, so a switch starts a fresh dataset. That's the main argument for running both during a transition: keep GA4 alive for continuity and comparison while Matomo builds up its own baseline, then decide later whether to retire one. Because both integrations fire the same PrestaShop e-commerce events, the purchase figures stay reconcilable across the two while you overlap.

Does Matomo track PrestaShop orders and revenue, or just pageviews?

It tracks full e-commerce data, but only if the order, cart, and checkout events are wired into PrestaShop's flow, not just a bare pageview snippet in the header. A raw Matomo tag counts visits and pages; it won't know an order happened or what it was worth. That's exactly the gap our Matomo integration closes, firing add-to-cart, checkout-step, and purchase events from the right points in the order process so revenue and product-level conversion appear in your Matomo reports.

Matomo or Clarity. Which one do I actually need?

They're not competitors; they answer different questions. Matomo (or GA4) is your quantitative analytics. Counts, rates, revenue, where traffic comes from. Clarity is qualitative, heatmaps and recordings that show you why a page leaks. Most serious stores run one analytics platform plus one behavioural tool, because neither replaces the other.