Google Analytics is free, and that is the hardest argument in this comparison to beat. It is also the reason most WordPress sites end up with a GA4 property nobody quite understands, a consent banner that costs them a third of their data, and a nagging feeling that the numbers do not describe their business. If you have started looking for a Google Analytics alternative, that feeling is usually why.
We build Must-Have Analytics, a self-hosted analytics plugin, so treat the conclusion accordingly. What follows is an honest Google Analytics vs WordPress analytics comparison — including the places where nothing we ship can replace what Google gives you for nothing.
One note on method: the screenshots here are from Must-Have Analytics running on a demo WooCommerce store. There are no GA4 screenshots — we did not send test traffic to a real Google property, because polluting a live analytics account to illustrate a blog post is not something we are willing to do. The GA4 side is described from Google’s own documentation.
The short version
| Must-Have Analytics | Google Analytics 4 | |
|---|---|---|
| Price | $99/year, 1 site | Free (GA4 360 is enterprise-priced) |
| Where your data lives | Your own WordPress database | Google’s infrastructure |
| Needs cookie consent for its own tracking | No | Yes |
| Data lost to consent rejection | None | Whatever visitors decline |
| Data sampling | None | Applied above thresholds |
| Setup | Activate the plugin | Property, data stream, tag, often Tag Manager |
| Reports live in | WordPress admin | Separate Google interface |
| Retrospective goals | ✔ | Conversions count from creation onward |
| Core Web Vitals from real users | ✔ | Via other Google tools, not GA4 reports |
| Server-side conversions to Meta / TikTok | ✔ | Not its job |
| Remarketing / email list export from first-party data | ✔ | Audiences inside Google Ads |
| Correlation analysis and Sankey flows | ✔ built in | Build it in Explorations |
| Cross-domain, app and offline data | — | ✔ |
| BigQuery export, Looker Studio, Ads integration | — | ✔ |
| Data retention | You decide | 2 or 14 months for event data |
The consent problem
Google Analytics sets cookies and processes personal data, so in the EEA and the UK it needs consent before it runs. That is not a controversial claim — it is why Google built Consent Mode in the first place.
The consequence is arithmetic. Every visitor who ignores or rejects your banner is a visitor GA4 either does not see or models statistically. Consent Mode v2 fills some of that back in with behavioural modelling, but modelled data is an estimate, and the gaps show up exactly where you least want them — in conversion counts. We went through this in detail in why Consent Mode still leaves gaps in your marketing data.
A privacy-friendly analytics tool sidesteps the problem rather than patching it: no cookies for its own tracking, no personal data leaving your server, no consent required for it to count a visit. Every visitor is measured, including the ones who close your banner — which is what people usually mean by GDPR analytics. You will still need a Cookie CMP for your other services — a tag manager, ad pixels, embedded video — but your baseline traffic data stops depending on a click. Our write-up of a practical analytics setup for privacy-conscious teams covers how the two fit together.
Setup and the learning curve
GA4 asks you to create an account, a property and a data stream, install a tag (often through Tag Manager), configure enhanced measurement, mark events as key events, and then learn an interface built for a much larger analytics problem than “how is my shop doing”. Plenty of site owners never get past the default reports — and fewer still notice that event-level data is kept for 2 or 14 months depending on a setting most people never touch.
Must-Have Analytics starts collecting when you activate it, and its reports are named after the questions people actually ask: which pages, which sources, which countries, which devices, which products, how fast.
Goals you can define after the fact
This is the single behaviour that surprises people most when they switch. In GA4, a conversion starts counting the day you configure it. If you realise in November that you should have been tracking newsletter signups since March, that history does not exist.
Must-Have Analytics records the underlying events continuously, so a goal you create today immediately shows its past. You are not punished for not having predicted, months ago, what you would want to measure.
WooCommerce reporting without a configuration project
GA4 can do excellent eCommerce analysis — after someone implements the enhanced eCommerce data layer correctly. In practice that means a plugin, a tag manager container, and a debugging session or three. Get it wrong and your revenue numbers quietly disagree with WooCommerce.
On our demo store, Must-Have Analytics recorded product views, add-to-cart events, initiated checkouts and completed orders with values, out of the box. Having WooCommerce analytics in the same place as your traffic is what turns a number into a decision — we argued the case in what your conversion rate does not tell you.
Getting conversions back that browsers hide
Ad blockers, Safari’s tracking prevention and consent rejections all remove conversions from browser-side measurement. Must-Have Analytics can send conversions to Meta and TikTok from your server, using data you already own — the approach we described in server-side conversion tracking. It can also export hashed remarketing audiences built from your own first-party data.
GA4 is not designed for this. It feeds Google Ads, which it does very well; it is not a conversion pipeline to other ad platforms.
Audiences, correlations and flow analysis
GA4 builds audiences and shares them with Google Ads — inside Google’s ecosystem. First-party analytics does the equivalent with data that stays yours: anonymous visitors are linked to known customers when they register or buy, and the resulting Entities list can be filtered by country, device, pages visited, conversions or value and exported as a remarketing audience or an email list.
Alongside the reports there are two analysis tools GA4 makes you build in Explorations: Correlations, which tests statistical relationships between your metrics, and Sankey Analysis, which draws the visitor flow toward a chosen goal. Charts also carry moving average, trend, standard deviation, Bollinger band and cumulative overlays.
Real-user performance data
Must-Have Analytics records LCP, FCP, CLS and TTFB from real sessions and lets you slice them by country and device — so a slow experience in one market shows up as data rather than a complaint. Our Core Web Vitals guide explains what each metric means and which fix moves it, and Swift Performance is what you reach for once the data points at the site itself. GA4 does not report Core Web Vitals; Google puts that data in Search Console and PageSpeed Insights instead, which means another interface and a different sampling basis.
Where Google Analytics wins
Being straight about this matters more than winning an argument.
- It is free, at a scale no self-hosted tool can match on cost alone.
- Scope beyond one website. Cross-domain journeys, mobile apps via Firebase, offline conversion imports, multi-property roll-ups. If your business is not one WordPress site, GA4 is built for that and we are not.
- The Google ecosystem. Native Google Ads integration, audience sharing, Search Console linking, Looker Studio, and BigQuery export for anyone who wants raw event data and SQL.
- Exploration and modelling. Free-form explorations, path and cohort analysis, attribution modelling across channels.
- Familiarity. Every agency and freelancer you might hire already knows it.
If you need any of those, the honest recommendation is to keep GA4. Plenty of sites run both: Google for ecosystem reach, a self-hosted tool for numbers that do not depend on consent.
Who should choose what?
Stay on Google Analytics 4 if you:
- run several domains, an app, or offline conversions that must be joined together
- depend on Google Ads audiences, Looker Studio dashboards or BigQuery
- need advanced exploration, attribution or cohort analysis
- have a budget of zero for analytics tooling
Move to Must-Have Analytics if you:
- run one WordPress site or store and want answers, not a data platform
- are tired of losing a third of your data to a consent banner
- want WooCommerce revenue, funnels and abandoned carts without an implementation project
- want goals that work retrospectively and conversions that survive ad blockers
- need to be able to say, truthfully, that visitor data never leaves your server
Frequently asked questions
Is Google Analytics illegal in the EU?
No — but it is regulated. Several EU data protection authorities have ruled against specific implementations over transfers of personal data, and the legal position has shifted with successive frameworks. The practical reality for most site owners is simpler: GA4 requires consent, and consent costs you data. A self-hosted tool removes that particular question from your compliance surface. This is not legal advice.
Can I import my Google Analytics history?
No. Historical GA4 data cannot be imported into a self-hosted plugin. Run both in parallel for a few weeks so you have an overlap, and expect the numbers to differ — different definitions of a session, different bot filtering, and GA4’s consent gap all guarantee it.
Why do the numbers not match GA4?
Because they measure different populations. GA4 sees consenting, non-blocked visitors and models the rest; a cookieless self-hosted tool sees everyone but identifies returning visitors differently. Session definitions and bot filtering differ too. Expect a self-hosted tool to report more traffic than GA4, not less.
What is the best Google Analytics alternative for WordPress?
It depends on what you are replacing. If you only need traffic reporting, several self-hosted analytics plugins do that well and some are free. If you need revenue, funnels, campaigns and conversions in one place — analytics without Google, but without losing the reports you actually use it for — the shortlist gets much shorter, because most privacy-friendly tools stop at pageviews.
Can I run both at the same time?
Yes, and many sites should. Keep GA4 for Google Ads and ecosystem integrations, and use a self-hosted tool for a consent-independent view of traffic and revenue. They do not conflict.
Does self-hosted analytics slow my site down?
It removes third-party requests to Google’s servers, and adds a small first-party one instead. Must-Have Analytics also measures its own effect on you: field Core Web Vitals are one of its reports, so you can check rather than take our word for it.
The verdict
Google Analytics 4 is a powerful platform, and for organisations measuring several properties, apps and ad channels together it remains the sensible default. Nothing in this article changes that.
But most WordPress sites are not that. They are one site, often a shop, run by people who want to know which pages work, where buyers come from, what is selling and what is being abandoned — without a consent banner eating the answer, a two-month retention limit truncating it, or a separate interface to learn. For them, the best Google Analytics alternative is simply the one that already lives where they work. For that site, Must-Have Analytics gives you complete data you own, in the admin you already use, with the eCommerce and marketing reports GA4 makes you build yourself.
There is a 14-day money-back guarantee, so the cheapest way to settle it is to run both for a fortnight and see which dashboard you keep opening.
Screenshots taken on 6 August 2026 from Must-Have Analytics 1.0.1 on a demo WooCommerce store (WordPress 7.0.2, PHP 8.3.33, WooCommerce 11.0) with 30 days of generated test traffic and 58 orders. Google Analytics 4 behaviour is described from Google’s public documentation; no test traffic was sent to a Google Analytics property.
