GA4 alternatives for a WooCommerce store: what each category actually replaces

Last updated: November 4, 2026. Vendor prices and claims were read on each vendor's own website on that date.

Say you opened Google Analytics 4 (GA4) this morning to answer one question, how many orders came from last week's email, and twenty minutes later you had a channel report, a threshold warning and no answer. You are not alone, which is why "GA4 alternatives" is a search with a Reddit thread in the top three and a dozen vendor listicles under it. Most of those lists rank ten tools and never ask what you were trying to do. This guide sorts the GA4 alternatives into four categories, says what each category replaces and what it does not, gives prices from each vendor's own site, and ends with a way to choose that starts from your question rather than from a feature grid.

Why are store owners looking for GA4 alternatives?

Four reasons repeat across forums and support threads: GA4 is harder to read than the tool it replaced, it needs a consent banner where cookie rules apply, it stores visitor data on Google's servers, and its reports can withhold rows or sample data. For a store there is a fifth: GA4 never sees the orders table, so its revenue is always an estimate from browser events.

The fifth reason is the one that decides the category. If your problem is the interface or privacy, a hosted privacy tool solves it. If your problem is that analytics and orders do not line up, no tag-based tool solves it, because they all count the same browser events GA4 counts. The WooCommerce Analytics vs Google Analytics guide explains that gap with numbers.

What should you judge a GA4 alternative on?

Six things: where the data is stored, whether it sets cookies, whether it reads WooCommerce orders or only tag events, what it costs at your traffic level, whether it can feed Google Ads, and whether your team will open it. The last one is not a joke. A tool nobody reads is the most expensive kind.

1. Data location. Vendor cloud, your own server, or your WordPress database.
2. Cookies. Cookieless tools need no analytics banner. Cookie-based tools need consent where rules apply.
3. Order data. Tag events only, or direct access to WooCommerce orders, refunds and stock.
4. Price at scale. Count your monthly pageviews or events, then price the tier you would land in.
5. Ads. Google Ads can import GA4 conversions and audiences. None of the alternatives feed the ad account, so for advertisers they are "as well as", not "instead of".
6. Daily use. Does it answer the morning question in one screen.

Category 1: hosted privacy-first analytics (Plausible, Fathom)

Lightweight, cookieless, hosted by the vendor, priced by pageviews. They replace GA4's traffic reports with a single simple dashboard and remove the analytics consent banner. They do not read orders, do not feed Google Ads, and keep your data on the vendor's servers rather than yours.

Facts from the vendors' pricing pages on November 4, 2026. Plausible lists $9 a month for up to 10,000 pageviews, a 30-day trial with no card, no free plan, and states "No cookies, no persistent identifiers" and "No cookie banner required". It is open source and can be run yourself. Fathom lists $15 a month for up to 100,000 pageviews across 50 sites, a 7-day trial with a card, and says "No cookies, so no consent banner for analytics".

A worked example, not a customer result. A store with 40,000 visits and about 200,000 pageviews a month would need a Plausible tier above the $9 entry and sits inside Fathom's 100,000-pageview tier only until it grows. Check the exact tier on each pricing page for your own numbers.

Category 2: self-hosted and open-source analytics (Matomo, Umami)

Free software you run on your own server, or pay the vendor to host. They replace GA4's traffic and event reports and answer the data-location question completely when self-hosted. The cost is a database to maintain. Like category 1, they count tag events and do not read WooCommerce orders directly.

Matomo's pricing page lists On-Premise as "Free forever" with unlimited users and hits, and Matomo Cloud priced by monthly hits with tiers from 50,000. Its requirements page asks for PHP 8.1 and MySQL 8.0 or MariaDB 10.6 or newer for Matomo 6. Umami's pricing page says "Self-hosting is always free", lists a free Cloud Hobby plan at 100,000 events a month for one site with six months of retention, and a Pro plan at $20 a month for one million events across 20 sites, and states it "does not use cookies". The Matomo vs Google Analytics guide goes deeper on the hosting cost of free.

Category 3: product analytics suites (PostHog, Mixpanel, Amplitude)

Event-based tools built for software products: funnels, cohorts, feature flags, session replay. They replace GA4 for teams that want to analyse user behaviour inside an app. For a WooCommerce store they are usually more than the job needs, and their pricing is per event, which a busy store generates by the million.

Several of them offer session replay and funnels that look like store features. The difference is the data model: they expect you to define events, and a WooCommerce store generates its events from the cart and checkout whether you defined them or not.

These appear in every GA4 alternatives list because the lists are written for SaaS teams. A store owner who wants to know which email brought orders does not need cohort retention curves. If you do run a membership or subscription product with a logged-in experience, this category becomes relevant, and the vendors' own pricing pages are the place to check event costs.

Category 4: analytics plugins that run inside WordPress

Plugins that store analytics in the WordPress database and show reports in the admin. They replace GA4's daily dashboard and, for store-focused plugins, add what no tag-based tool has: orders, refunds, live carts and sales matched to paid orders, next to traffic. They do not feed Google Ads. Scope varies widely between plugins, so read each one's feature list rather than the category name.

As of November 2026 this category includes general traffic plugins such as Independent Analytics, Burst Statistics and Koko Analytics, and store-focused plugins such as StorePinger. The difference inside the category is whether the plugin knows what an order is. A traffic plugin shows visits and pages inside WordPress. A store plugin joins the visit to the cart and the order.

StorePinger keeps all data in the store's own WordPress database and hosting, has a visitor tracker that sets no cookies and uses a random id in local storage, does not store IP addresses, and sends nothing about visitors to StorePinger. The free plan shows live visitors on a world map, visitors by country, today's visitors and page views. Pro, at $49.99 a year for one site, adds traffic sources including ChatGPT, Perplexity, Gemini, Claude and Copilot, sales by source, the conversion funnel, session recordings on your own hosting, abandoned cart recovery, reports and alerts, and 90 days of history. The alternative page lists what it replaces and what it leaves to GA4.

How do the categories compare?

The table below is by category, with one or two named examples, because the decision is made at the category level. Prices are the lowest listed tier on each vendor's site on November 4, 2026, and will change.

Sources: Plausible pricing, Fathom pricing, Matomo pricing, Umami pricing. GA4 cookie behaviour is from Google's cookie usage documentation.

Do you still need GA4 if you run Google Ads?

Usually. Google Ads can link to a GA4 property to import conversions and build audiences, and none of the alternatives feed the ad account. Stores that advertise on Google generally keep GA4 for the ad account, or at least the Google Ads tag, plus one alternative for daily reading. Plan for two tags from the start and set the GA4 property's retention to 14 months.

This is the point most lists bury. "Replace GA4" is only possible for sites that do not advertise on Google. For everyone else the question is which tool you read, not which tag you remove. The consent banner stays for the GA4 tag where rules apply, which removes one of the reasons people switch, so weigh that honestly.

What do you give up when you leave GA4?

Three things most lists skip: the link to Google Ads, the multi-visit attribution models, and the free BigQuery export for people who query raw data. If none of those is in your weekly routine you give up nothing you use. If one of them is, keep the GA4 property for that job and read the alternative for everything else.

Attribution is the one store owners miss most. GA4 can show that a shopper came from a Google search, left, returned from an email and bought, and credit both touches. Cookieless hosted tools and in-WordPress plugins credit the visit that contained the order, which is the same last-click rule WooCommerce's own Order Attribution uses. For most stores last click is enough to decide where next month's budget goes. For a store running several paid channels at once, the multi-touch view is worth keeping GA4 open for, monthly.

A worked example, not a customer result. A store spends $2,000 a month on Google Ads and $500 on Meta. GA4's data-driven model credits Google with 35% of purchases and Meta with 20%. Last-click sales by source credits Google with 30% and Meta with 15%, with email and direct taking the rest. The numbers differ, the ranking does not, and the budget decision is the same either way. The owner reads the last-click report daily because it sits next to the orders, and checks GA4 monthly to confirm nothing has flipped.

Is a cookieless tool as accurate as GA4?

More complete and less precise. A cookieless tool keeps the visits of people who would have declined cookies, so it counts more sessions and more purchases than GA4 on the same site. It cannot recognise a visitor who returns tomorrow without a persistent identifier, so it over-counts unique visitors and under-counts returning ones. For deciding what sells, completeness wins. For studying loyalty, precision wins.

The trade is visible in the numbers within a week. Run a cookieless tool beside GA4 and the cookieless one shows more visits and more purchases, often by a tenth or more on stores with a consent banner. Then compare both with WooCommerce paid orders and neither matches, because blocked scripts and gateway redirects remove orders from both. That is the moment most owners understand why the orders table has to be in the picture.

How to choose: start from your question

Write down the three questions you open analytics to answer. If they are about traffic and pages, category 1 or 2. If they are about orders, carts and which channel sells, category 4. If they are about product behaviour in an app, category 3. Then price the category at your traffic, and run the choice beside GA4 for a month before switching anything off.

A worked example, not a customer result. A store owner's three questions: did last week's email bring orders, who is on the site now and what do they have in the cart, and which city should the next ad target. All three are order questions. Category 1 and 2 tools answer none of them directly. A store-focused in-WordPress plugin answers all three from the orders table. The owner keeps GA4 for Google Ads, installs the plugin, and reads GA4 once a month. Total cost: the plugin's yearly price. Time saved: the twenty minutes a morning spent in GA4.

1. List your three questions.
2. Pick the category that answers them from its own data.
3. Count monthly pageviews or events and price the tier.
4. Check data location against your privacy policy.
5. Run it beside GA4 for a month and compare purchase counts with WooCommerce.
6. Keep the one you open. Switch off the one you do not, unless it is the GA4 tag your ads need.

Common mistakes

• Choosing from a vendor's list. Every list on the first page is written by a vendor on it. Start from the category.
• Removing GA4 while advertising on Google. The ad account loses its conversion source.
• Pricing at today's traffic only. Pageview and event tiers climb with a good month.
• Expecting a tag-based tool to match orders. Only a plugin that reads the orders table does.
• Assuming cookieless means complete. Blocked scripts still miss visits, and returning visitors can be counted as new.
• Switching without an overlap month. You lose the baseline that tells you what each tool misses.
• Ignoring who will read it. The daily report email is read. A dashboard with forty reports is not.

Conclusion

GA4 alternatives come in four kinds, and three of them count the same browser events GA4 counts, just somewhere else and without cookies. That solves the interface, the banner and the data-location problems, which are real. It does not solve the store's problem, which is that analytics and orders never agree. For that you need the fourth kind, a plugin inside WordPress that reads the orders table and shows live carts, sales by source and refunds next to traffic. Keep GA4 for the ad account if you advertise, pick one tool to read every morning, and judge it by whether it answers your three questions in one screen. The StorePinger features page shows the store-focused version of the fourth category, and the free live visitors view is a reasonable place to start.