Google Analytics alternatives for SaaS that track revenue

On February 10, 2022, France's data protection authority, the CNIL, ruled against a website using Google Analytics. It found the transfer of visitor data to the US broke the GDPR. The site got one month to comply. The CNIL suggested tools that produce anonymous statistics instead (Hunton Andrews Kurth, a law firm's summary).

That was an EU decision, and the picture has changed since. On July 10, 2023, the European Commission adopted the EU-US Data Privacy Framework. Data can now flow to US companies in the Framework without extra safeguards (European Commission). US sites face different rules again. Ask your lawyer about your markets.

Privacy is one reason to look for a Google Analytics alternative. For SaaS founders, the bigger reason is money. GA4 often can't see the payment in Stripe. For that problem, read GA4 vs Stripe revenue: why they don't match and how to fix it first.

A note on bias: Kratly sells in this space. I've linked every vendor claim so you can check it.

What should a GA4 alternative for SaaS do?#

A Google Analytics alternative is a tool that replaces GA4 for counting visits, sources and conversions, with a different trade-off on privacy, depth or revenue.

For SaaS, I'd rank tools on three questions:

1. Can it see revenue? The actual payment in Stripe or Shopify, including renewals and refunds. Not a browser "purchase" event.
2. What does it need for consent? Read the vendor's wording, then ask your lawyer. A cookie banner loses visitors who decline.
3. Who will use it? Marketers want sources. Product teams want funnels. Few tools do both well.

Tools that split credit across many ad touches are a different purchase; see Marketing attribution software: buyer's guide for SaaS and stores. The method behind revenue by source is in SaaS marketing attribution: tie every campaign to real revenue.

Privacy-friendly analytics: Plausible, Fathom, Simple Analytics, Matomo#

Privacy friendly analytics tools collect fewer visitor details, mostly without cookies. They fit marketing sites, blogs and docs.

Plausible#

Who it's for: content-led SaaS and small teams that want one simple dashboard.

Revenue: Plausible lets you "send monetary values alongside custom events to track revenue." You can filter revenue by source, campaign, entry page, country or device (Plausible). Its page names Shopify setup, but not a direct Stripe connection.

Consent: Plausible says "No cookie banner required" and that it doesn't use cookies.

Pricing model: subscription, with a 30-day free trial.

Fathom#

Who it's for: agencies and founders with several small sites.

Revenue: "Event and revenue tracking" is listed on every plan (Fathom). The pricing page doesn't mention Stripe.

Consent: Fathom says "No cookie banners required."

Pricing model: from $15 a month for up to 100,000 monthly pageviews and 50 sites, with a 7-day trial.

Simple Analytics#

A Dutch, EU-hosted option (European Alternatives). I couldn't confirm its revenue features or prices for this guide; check its pricing page.

Matomo#

Who it's for: teams that want to own their data on their own servers.

Revenue: Matomo has ecommerce tracking. There's a catch for consent-free use in France. Its CNIL compliance mode strips campaign parameters, rejects user IDs and recommends turning ecommerce off (Matomo CNIL self-assessment). In that mode, you can't fully tie revenue to campaigns.

Pricing model: On-Premise is "Free forever." Cloud is paid and priced by monthly hits (Matomo).

What I'd check first: does a tool keep campaign data in its strictest privacy mode? Ask every vendor.

Product analytics with Stripe revenue: PostHog, Mixpanel, Amplitude#

These track what users do inside your app. They're the better GA4 alternative for SaaS when your questions are about activation and retention.

PostHog#

Who it's for: product-led SaaS with engineers who will set it up.

Revenue: Stripe connects as a data warehouse source. PostHog then "will automatically use the data from Stripe to compute your revenue metrics." You can link Stripe customers to PostHog persons and groups (PostHog Docs). The docs recommend webhook syncing, since append-only syncs miss changed rows.

Pricing model: usage-based. The free monthly allowance includes 1M product analytics events and 1M synced warehouse rows (PostHog pricing).

Mixpanel#

Who it's for: product and growth teams that want funnels and cohorts.

Revenue: Mixpanel's Stripe guide streams Stripe webhooks through a Google Cloud Function that you deploy. Each Stripe event becomes a Mixpanel event, keyed to the Stripe customer (Mixpanel Docs). Historical data needs its warehouse connectors.

Amplitude#

Who it's for: larger product teams already using Amplitude for behavior data.

Revenue: Amplitude's Stripe source imports charges, refunds, invoices and payment intents. It matches users by metadata.user_id and email, among other fields. It can't backfill: only events after you set up the webhook arrive (Amplitude Docs). Set it up early.

I didn't verify Mixpanel or Amplitude pricing or cookie posture; check each vendor.

Revenue-first web analytics tools#

A newer group starts from the payment and works back to the visit, showing revenue by source, page and campaign.

DataFast is one example. It connects Stripe, LemonSqueezy, Polar and Shopify (DataFast Docs). Its Starter plan is $9 a month and Growth is $19, each with a 14-day trial.

DataFast says its default script "uses cookies to recognise returning visitors," so you may need a banner. Its cookieless script avoids that, but is less accurate for revenue over weeks (DataFast).

That's the core trade-off here. Tying a payment to a visit three weeks earlier means recognizing the visitor. Cookie-free tools rotate or drop that identifier.

Which Google Analytics alternative fits? A comparison table#

My picks: a privacy-first tool for EU-heavy marketing sites, PostHog or Mixpanel for activation questions, and a revenue-first tool when ad budget is the question.

When should you keep GA4?#

Often. Dropping a free tool still has costs. Keep it if:

• You run Google Ads. You can import GA4 key events into Google Ads. They arrive as secondary conversions by default (Google Analytics Help). Many accounts depend on that link.
• You need long lookback windows. GA4 keeps a 30-day default for acquisition key events and 90 days for others (Google Analytics Help).

Limit it if EU consent rules shrink your GA4 data until it stops helping.

For most SaaS teams I'd run GA4 for Google Ads plus one alternative for the question GA4 answers badly. Either way, set up GA4 key events for SaaS so the GA4 side stays clean.

How to switch without losing data#

Run both tools in parallel for 30 days.

1. Install the new tool next to GA4, with the same UTM naming convention on both.
2. Export the GA4 reports you use most, by month.
3. Compare visitors weekly. Expect gaps; cookie-free tools count people differently.
4. Compare revenue with Stripe. The new tool's total should sit at or below Stripe's. More means double counting.
5. Decide on day 30. Keep both, keep one, or keep GA4 just for Google Ads.

My estimate: two to six hours for steps 1 to 4.

How to do this in Kratly#

Kratly isn't a product analytics tool and won't replace PostHog for in-app funnels. It fits teams asking which campaigns, pages and emails bring revenue.

1. Add Kratly's website tracking and connect Stripe or Shopify. Kratly ties each payment to the campaign, page or email that brought it.
2. Connect Google Ads, Meta Ads and Search Console. Spend and search data sit next to revenue.
3. Compare against Stripe for 30 days. Run it beside GA4 and check totals weekly, as above.
4. Review suggestions. Kratly suggests budget changes. You approve them, and each change is logged and reversible.

LinkedIn, TikTok and Reddit Ads are coming soon. Until then, tag that traffic with UTMs and upload its spend as a CSV. Compare us fairly in Kratly alternatives and comparisons: which growth tool fits. For AI tools, see AI marketing agent: what it can do, what it can't, how to choose.