A Simple Analytics alternative that shows which traffic pays

Last checked: 29 October 2026. Simple Analytics facts come from simpleanalytics.com and docs.simpleanalytics.com on that date and can change; the sources are listed at the end. Prices may change; see Simple Analytics pricing. "Unconfirmed" means the fact wasn't on Simple Analytics' own pages that day. It doesn't mean the feature is missing. See all comparisons, including Google Analytics.

In short#

• Both are simple, cookieless web analytics with one script tag and a one-page dashboard.
• Revenue. No revenue or payment-provider feature was found on Simple Analytics' pages. traffic.cx connects your payment provider and handles renewals, refunds and unmatched payments.
• Getting started. Simple Analytics has a free plan (5 websites, 1 month of history, badge required) and a 14-day trial with no card. traffic.cx is free on one site with every feature, revenue attribution included, no card. Sign up with Google or email.
• Where Simple Analytics is stronger. EU hosting by an EU company, GA4 import, raw data export in several formats, and more platform guides.

What's the same#

Simple dashboard, one script#

Both are built to be read without training. You add one script tag and see sources, pages, campaigns, countries and devices, with custom events for sign-ups and clicks. Both filter bot traffic. traffic.cx has a bot traffic report on every plan (pricing), and Simple Analytics has robot blocking (Simple Analytics docs).

No visitor cookie by default#

Neither tool sets a visitor cookie by default, so this is parity, not an advantage. traffic.cx's default tracker uses a daily visitor identifier whose secret is deleted after 48 hours, and an optional cookie mode supports longer visitor journeys (privacy notice). Whether you need consent depends on your setup and the rules that apply to you, especially because revenue attribution links payments to visits.

Where traffic.cx is different#

Revenue from your payment provider#

No revenue feature was found on Simple Analytics' pages as of 29 October 2026. Its docs cover pageviews, events, goals and metadata (Simple Analytics docs). In traffic.cx you connect Stripe, Lemon Squeezy, Polar or Dodo Payments in Settings → Revenue, and payments arrive from the provider. Your checkout passes one extra value, the pageview ID, so each payment can be matched to its visit (how it works). Using another checkout? Send payments with the Payments API or report them from the tracking script.

Renewals, refunds and unmatched payments#

A renewal for a known customer inherits the attribution of that customer's first payment. Refunds are subtracted on the day they happen and credited to the payment they refund. A payment that can't be linked to a visit stays in your totals as "Unattributed" instead of going to a guessed source.

Revenue per visitor and two attribution models#

The Revenue page compares sources by revenue, paying customers, conversion rate and revenue per visitor, and toggles between last non-direct (the default) and first touch, with a 90-day lookback by default (7 to 365 days) (revenue attribution).

One honest caveat. In the default cookieless mode, a pageview ID links a payment to the visit where checkout started. Visitor IDs rotate daily, so a purchase can't be connected to a campaign visit on an earlier day unless you turn on the optional cookie mode (same browser only) or the customer has paid before (cookieless versus cookie mode).

Every feature on the free plan, and teammates priced by volume#

traffic.cx's Free plan has every feature, revenue attribution, goals and funnels included, on one site. Sign up with Google or email. Paid plans are priced by monthly events only, with unlimited sites and team members (pricing). Simple Analytics' docs say goals need a plan that includes them, and its pricing adds $20/month per extra user, as of 29 October 2026 (Simple Analytics).

Where Simple Analytics is the better choice#

• EU hosting and an EU company. Simple Analytics stores website data in the EU, with primary infrastructure in the Netherlands, and is a Dutch company (Simple Analytics). traffic.cx's server is in Mumbai, India, and it doesn't promise EU-only hosting.
• Your history. Simple Analytics imports GA4 pageviews (Simple Analytics docs). traffic.cx can't import Simple Analytics or any other analytics tool, so your history starts when you install it.
• Raw data export. Simple Analytics exports raw pageviews and events in formats such as CSV, JSON and Parquet (Simple Analytics docs). traffic.cx exports report tables as CSV and has no raw-event export.
• Several sites for free. Simple Analytics' free plan covers 5 websites with a badge. traffic.cx's Free plan covers one site.
• Platform guides and extras. Simple Analytics has guides for WordPress, Webflow, Squarespace, Wix, Ghost and Google Tag Manager, plus an iOS and macOS app and email reports (Simple Analytics). traffic.cx has fewer.
• Track record. Simple Analytics started in 2018. traffic.cx is newer.

Pricing#

Sign up with Google or email and start on the Free plan: every feature on one site, no card and no trial clock. The Free plan is $0, forever: every feature on one site, 3,000 events a month, the last 30 days. Paid plans add more events, more sites, your full history, the API and teams. See pricing for the volume tiers.

Simple Analytics has a free plan for hobby sites (1 user, 5 websites, 1 month history, badge required), and a paid plan shown at $20/month for 100,000 pageviews with 1 user included and $20/month per extra user. Sign-up starts a 14-day trial with no credit card (simpleanalytics.com/pricing), as of 29 October 2026. Prices may change. Check Simple Analytics pricing for the current numbers.

How to switch from Simple Analytics#

These steps come from the install guide, the revenue docs and the provider guides.

1. Export what you want to keep. traffic.cx can't import Simple Analytics or any other analytics tool, so your history starts when you install the script. Simple Analytics lets you export raw pageviews and events (Simple Analytics docs).

2. Sign up and add your site. Sign up with Google or email, add the site with its real domain and copy the snippet from Settings → Tracking.

3. Install the script. Put this once in the shared head, with the full tcx_ ID. Don't add manual pageview calls on route changes. The tracker follows single-page navigation.

   html

   <script defer src="https://traffic.cx/js/YOUR_SITE_ID.js"></script>

4. Verify your first visit on your published domain. Localhost and iframes are ignored by default.

5. Recreate your events as goals. Replace sa_event('name') calls with window.trafficcx?.('name') and create a matching custom-event goal in the dashboard.

6. Connect payments and pass the pageview ID. In Settings → Revenue, connect Stripe, Lemon Squeezy, Polar or Dodo Payments, then add trafficcx.pageviewId() to your checkout metadata, and to the subscription's metadata for renewals. Test with your provider's test mode on a separate traffic.cx test site. Connecting a provider imports its last 90 days of payments. Those older payments will mostly be Unattributed.

7. Run both while you compare, then remove the Simple Analytics script. traffic.cx is safe to run alongside Simple Analytics's script. It keeps to its own window.trafficcx global and tcx_ storage, and it adds to the browser's page-change handling instead of replacing it.

Sources#

traffic.cx facts come from pricing, the home page, privacy, how revenue attribution works (updated 14 Oct 2026), revenue attribution, plans (updated 25 Oct 2026), the docs index, install (updated 14 Oct 2026), Search Console and the provider guides for Stripe, Lemon Squeezy, Polar and Dodo Payments, checked 29 Oct 2026. Each of those guides says connecting imports the last 90 days. The operator line is the site footer. The Free plan numbers come from the same plan catalogue as pricing.

Simple Analytics facts come from these pages, as of 29 Oct 2026:

• Pricing (plans, FAQ, "What we do and don't do with your data")
• Features
• Integrations
• Docs and API
• Goals
• GA4 import
• Export
• Server-side events
• Robot blocking
• About