Matomo vs Google Analytics for a WooCommerce store: which should you actually run?

Last updated: November 4, 2026. Vendor facts were read on each vendor's own site on that date.

Say your store gets 40,000 visits a month and you have been told, by a consultant or a Reddit thread, that you should drop Google Analytics 4 (GA4) for Matomo because of privacy. Before you move, work out what each tool would cost you in money, hosting and attention. Matomo On-Premise is free to download, but 40,000 visits a month is a database you now run. Matomo Cloud is priced by hits. GA4 is free and lives on Google's servers, which is the whole privacy question in one sentence. Matomo vs Google Analytics is less a contest than a choice about where your visitor data sits and who does the work of keeping it.

This guide compares the two on the questions a store owner actually asks: ownership, cookies and consent, sampling and thresholds, cost, ecommerce reports, and the one question neither tool answers, which is what happened to yesterday's orders inside WooCommerce.

What are Matomo and Google Analytics 4?

Google Analytics 4 is Google's free web analytics service. A tag on your pages sends events to Google, and you read reports at analytics.google.com. Matomo is an open-source analytics platform you can run on your own server (On-Premise) or pay Matomo to host (Cloud). A tag on your pages sends data to your Matomo instance, and you read reports there.

Both track page views, sessions, sources, devices and ecommerce events. Both have a WordPress plugin to place the tag, and the GA4 setup guide and its no-plugin version apply almost unchanged to Matomo's tag. Both can be configured for a WooCommerce store. The differences are not in what they can count. They are in where the data goes, what the tracking requires of visitors, and what the tool costs to run.

Who owns the data?

With Matomo On-Premise the data is on your server and nobody else's. Matomo's own comparison page says "your web analytics data is yours to own, with no external parties looking in." With GA4 the data is processed and stored by Google under Google's terms. Matomo Cloud sits between: Matomo hosts it for you, under Matomo's terms.

Ownership also decides what happens when you leave. Export your Matomo database and you have every visit. Close a GA4 property and the data is gone after Google's retention period, with exports limited to what the interface or the API gives you. For a store that may change hands or be audited, that difference is worth stating in writing before you choose.

Why this matters to a store: your analytics data includes which products each visitor viewed, what they put in the cart, and where they came from. Under privacy rules in many regions you are responsible for where that goes. With On-Premise you can answer the question in one line. With GA4 you rely on Google's documentation and your consent setup. Neither is wrong, but only one of them lets you say "it never left our server".

Do they need cookies and consent?

GA4's tags use first-party cookies to distinguish users and sessions, per Google's cookie documentation, so where consent rules apply the tag must wait for consent. Matomo's site says it can "track users without the use of third-party cookies" in a cookieless mode and that this configuration is "exempt from tracking consent by France's Data Protection Authority (CNIL)". Cookieless Matomo loses some accuracy on returning visitors in exchange for no banner.

Facts for Matomo are from Matomo's own comparison page and pricing page. Facts for GA4 are from Google's cookie documentation and retention settings pages.

What are the key differences between GA4 and Matomo on accuracy?

Matomo states that it does not sample data, so a report shows every recorded hit. GA4's standard reports are built from all collected data but apply thresholds that withhold rows when a report could identify a person, and some explorations are built on samples. For a small store the practical difference is that Matomo will show the row with three visitors from one town and GA4 may hide it.

There is a second accuracy question that neither vendor page raises: bots. Google says GA4 automatically excludes traffic from known bots and spiders and that this cannot be turned off. Matomo On-Premise gives you the filtering settings and the raw logs to tune them. A store that sees odd spikes from one network will find the cause faster in Matomo and will never see it at all in GA4, which is either a feature or a blind spot depending on what you needed to know.

Accuracy also depends on what is collected in the first place. Both tools lose visitors who block scripts. GA4 additionally loses visitors who decline cookies where consent is required. Cookieless Matomo keeps those visitors but may count a returning visitor as new. So "more accurate" has two meanings: Matomo collects more of the visits, GA4 ties more of the visits to a returning user. Pick the one that matters for your decisions.

Is Matomo free?

Matomo On-Premise is free. The pricing page lists it as "Free forever" with unlimited users and hits. What you pay is the hosting and the work: a server or a hosting plan with a database, updates, backups and the disk space that analytics data fills. Matomo Cloud is paid, with tiers starting at 50,000 hits a month, and offers a free trial without a card.

A worked example, not a customer result. A store with 40,000 visits a month at roughly five page views each sends about 200,000 hits to analytics every month. On Matomo Cloud that is a tier above the smallest. On Matomo On-Premise it is a database growing by a few hundred megabytes a month on a hosting plan you already pay for, plus an hour a month of someone's time for updates. On GA4 it is nothing. Free in money, paid in data location. Price the three honestly for your own numbers before deciding, and check the Cloud tier price on Matomo's site for your hit count, because the page lists tiers without mapping every tier to a figure.

What database does Matomo use, and does it matter?

Matomo On-Premise stores its data in a MySQL or MariaDB database, the same kind WordPress uses. Matomo's requirements page lists MySQL 8.0 or MariaDB 10.6 or newer and PHP 8.1 or newer for Matomo 6. It matters because that database grows with every visit, and because reports are built from it on your server. A busy store should give Matomo its own database and consider the archiving settings Matomo documents, rather than sharing the WordPress database on a small hosting plan.

This is the hidden cost of "free". Analytics tables for a store with a few hundred thousand hits a month can outgrow the WordPress database within a year. If the hosting plan has a database size limit, the first warning is often a slow admin. Agencies who run Matomo for clients usually put it on a separate server for this reason, and budget the time to update it when a new major version arrives.

Which is better for a WooCommerce store's ecommerce reports?

Both can receive ecommerce events from a WooCommerce tag and show revenue, products, carts and conversion by source. Neither reads the orders table, so neither shows refunds, order statuses, stock or the exact revenue your accountant sees. Matomo published an ecommerce comparison of the two in August 2026 that makes its own case. The fair summary is that the ecommerce reports are similar in scope and both depend entirely on the tag firing.

That dependence is the problem for a store. A cached thank-you page, a payment gateway that returns the shopper by webhook, a declined consent, an ad blocker: each one removes a purchase from both tools and from neither the WooCommerce orders list. The WooCommerce Analytics vs Google Analytics guide works through the gap with numbers. Whatever you run for sessions, run WooCommerce Analytics or an in-dashboard plugin for money.

Which should you choose?

Choose GA4 if you run Google Ads, want zero hosting work and accept data on Google's servers with a consent banner. Choose Matomo On-Premise if data location is a requirement you can state in a sentence and you have someone to run a database. Choose Matomo Cloud if you want Matomo's model without the upkeep and the hit-based price fits. For most stores the deciding factor is Google Ads.

1. Write down whether your analytics data may leave your servers. If no, Matomo On-Premise or an in-WordPress plugin. GA4 is out.
2. Write down whether you run Google Ads. If yes, you will keep a GA4 property for the ad account whatever else you run.
3. Count your monthly hits and price Matomo Cloud against the hosting and hours for On-Premise.
4. Decide whether a consent banner for analytics is acceptable. If not, cookieless Matomo or a no-cookie in-WordPress plugin.
5. Run the chosen tool for a month beside WooCommerce Analytics and compare purchase counts, so you know the tracking gap before you rely on either.

How long does switching take, and what do you lose?

Placing the Matomo tag takes an afternoon. Rebuilding the reports you actually read takes a week or two. What you lose is history: Matomo starts from the day you install it, and GA4 data does not move across. Keep the GA4 property open for its retention period so last year's numbers are still there to compare against.

1. Set up Matomo (Cloud account or On-Premise install), create the site, and get the tracking code.
2. Install Matomo's WordPress plugin or place the tag in a child theme, exactly as you would for GA4.
3. Enable ecommerce tracking for WooCommerce and place a test order in a private window.
4. Run both tools for a full month. Record visits, sessions and purchases from each next to WooCommerce paid orders.
5. Rebuild your three or four core reports in Matomo. Most owners read fewer reports than they think.
6. If Google Ads is in use, leave the GA4 tag in place for the ad account and decide whether a consent banner is still required for it alone.

A worked example, not a customer result. A store records 1,200 paid orders in the overlap month. GA4 shows 960 purchases, a ratio of 0.80. Cookieless Matomo shows 1,110, a ratio of 0.93, because it kept the shoppers who declined cookies. Neither reached 1,200: the missing orders came from gateway redirects and blocked scripts. The owner now knows two things: Matomo sees about 13% more purchases than GA4 on this store, and no tag-based tool will ever match the orders list. Both facts are worth the month.

Is there a third option for WordPress stores?

Yes: an analytics plugin that runs inside WordPress, stores data in the store's own database, uses no tracking cookies and reads orders directly. It answers the data-location question the way On-Premise Matomo does, without a second server, and it shows things neither Matomo nor GA4 can, such as live visitors with carts and sales by source matched to paid orders. It does not feed Google Ads, so advertisers keep GA4 beside it.

StorePinger works this way. Data stays in the store's WordPress database and hosting, the tracker sets no cookies and uses a random id in local storage, IP addresses are used only for the country or city lookup and are not stored, and nothing about visitors is sent to StorePinger. The free plan shows live visitors, the world map, visitors by country, today's visitors and page views. Pro adds traffic sources including AI tools, sales by source, the conversion funnel, session recordings stored on your own hosting, cart recovery and reports, at $49.99 a year for one site. The alternative page sets out what it replaces and what it does not.

Common mistakes

• Choosing on privacy without naming the rule. Write the requirement down. "Data must not leave the EU" is a decision. "Privacy is important" is not.
• Forgetting the hosting cost of free. On-Premise is free software on a server you pay for and maintain.
• Running Matomo on the WordPress database of a small plan. Give it its own database.
• Dropping GA4 while running Google Ads. The ad account needs it.
• Treating either tool's revenue as the ledger. Both count tag events. WooCommerce counts orders.
• Migrating without a baseline. Run both for a month and record the ratio of purchases to WooCommerce orders in each. The daily report email gives you the WooCommerce side of that ratio without opening a dashboard.
• Leaving GA4 retention at the shorter option. Standard properties offer 2 or 14 months. Set 14.

Conclusion

Matomo and Google Analytics count the same things in different places. Matomo's case is ownership, no sampling and cookieless tracking, at the price of running or renting a server. GA4's case is zero cost and zero upkeep, at the price of data on Google's servers and a consent banner. For a store the decision usually turns on Google Ads, which keeps GA4 in the picture, and on whether data location is a stated requirement, which brings Matomo On-Premise or an in-WordPress plugin in. Whichever you pick, pair it with the numbers that live in WooCommerce itself, because no tag-based tool sees refunds, stock or the carts left at checkout. The StorePinger features page shows those numbers inside the WordPress dashboard, and the GA4 alternatives guide covers the wider field if Matomo is not the fit.