A Fathom Analytics alternative that shows which traffic pays

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

In short#

• Both are simple, cookieless-by-default web analytics with a single script tag.
• Revenue. Fathom Analytics attaches a value, in cents, to events your site sends. traffic.cx connects your payment provider and handles renewals, refunds and unmatched payments.
• Getting started. Fathom Analytics has a 7-day trial that needs a card. traffic.cx is free on one site with every feature, no card. Sign up with Google or email.
• Where Fathom Analytics is stronger. GA4 history import, EU data isolation, at least 50 sites on every plan, and more platform install 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 events for sign-ups and purchases. Both filter bot traffic. traffic.cx has a bot traffic report on every plan (pricing), and Fathom Analytics lists automatic bot filtering (Fathom Analytics).

Cookieless 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, not from event code#

In Fathom Analytics, revenue is a value in cents that you attach to an event your site sends, for example on a thank-you page (Fathom Analytics docs). In traffic.cx you connect Stripe, Dodo Payments, Lemon Squeezy or Polar 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).

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).

Free on one site, no card#

The Free plan has every feature, revenue attribution included, on one site. Sign up with Google or email. No card, and no end date (pricing). Fathom Analytics starts with a 7-day trial that needs a card, as of 28 October 2026 (Fathom Analytics pricing).

Where Fathom Analytics is the better choice#

• Your history. Fathom Analytics imports supported GA4 data (Fathom Analytics). traffic.cx can't import Fathom Analytics, Google Analytics or Plausible data, so your history starts when you install it.
• EU data isolation. Fathom Analytics processes EU visitors on EU servers and strips IP addresses there (Fathom Analytics). traffic.cx's server is in Mumbai, India, and it doesn't promise EU-only hosting.
• Many sites from day one. Every Fathom Analytics plan includes at least 50 sites. traffic.cx's Free plan covers one site. Paid plans include unlimited sites.
• Platform guides. Fathom Analytics has install guides for many platforms, including Shopify, WooCommerce, WordPress and Google Tag Manager (Fathom Analytics). traffic.cx has no Shopify or WooCommerce connector.
• Track record. Fathom Analytics has been around for years. traffic.cx is newer.

For a side-by-side with Google Analytics, see the Google Analytics comparison.

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.

Fathom Analytics plans start at $15/month for up to 100,000 monthly pageviews, with a 7-day free trial that requires a card (usefathom.com/pricing), as of 28 October 2026. Extra site packs are $10/month for 50 sites, as of the same date. Prices may change. Check Fathom Analytics pricing for the current numbers.

How to switch from Fathom 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 Fathom Analytics, Google Analytics or Plausible data, so your history starts when you install the script. Fathom Analytics offers CSV exports (Fathom Analytics).

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.

5. Recreate your events as goals. Replace fathom.trackEvent('name') calls with window.trafficcx?.('name') and create a matching custom-event goal in the dashboard. If an event only carried a purchase value, you may not need it once payments sync.

6. Connect payments and pass the pageview ID. In Settings → Revenue, connect your provider, 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 Stripe imports the last 90 days of payments. Those older payments will mostly be Unattributed.

7. Run both while you compare, then remove the Fathom Analytics script. traffic.cx is safe to run alongside Fathom 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, the docs index, install and the Stripe guide, checked 28 Oct 2026. The operator line is the site footer. The Free plan numbers come from the same plan catalogue as pricing.

Fathom Analytics facts come from these pages, as of 28 Oct 2026:

• Pricing (trial, $15/month entry plan, site packs, bot filtering, "full analytics history while subscribed")
• Features
• Events
• Ecommerce conversions
• Integrations
• GA4 importer
• Account limits
• Data isolation
• About (based in Canada)
• Exporting