An Umami Analytics alternative that shows which traffic pays

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

In short#

• Both are cookieless web analytics with one script tag, goals, funnels and a revenue report.
• Revenue. Umami Cloud imports payments and refunds from six providers on Pro or Business and links them to visitors through a distinct ID. traffic.cx syncs payments on every plan, links them with a pageview ID at checkout, and handles renewals and unmatched payments.
• Getting started. Umami's Hobby plan is free for up to 100,000 events a month on one website. traffic.cx is free on one site with every feature, revenue attribution included, at 3,000 events a month, with no card. Sign up with Google or email.
• Where Umami is stronger. MIT-licensed open source you can self-host, a much bigger free allowance, product analytics (replays, heatmaps, retention, cohorts), data import, and Paddle and WooCommerce connectors.

What's the same#

Simple dashboard, one script, revenue report#

Both give you sources, pages, UTM campaigns, countries and devices from one script tag, with custom events, goals, funnels and realtime visitors. Both have a revenue report and both can pull payments from providers, so revenue alone isn't the whole difference. The details of how a payment is linked to a visit are.

No visitor cookie by default#

Umami's tracker doesn't use cookies (Umami), and traffic.cx sets no 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#

Payment sync on every plan, Free included#

Umami's payment-provider integrations need a Pro or Business plan, as of 29 October 2026 (Umami docs). In traffic.cx you connect Stripe, Lemon Squeezy, Polar or Dodo Payments in Settings → Revenue on any plan, including Free on one site.

A pageview ID instead of a user ID#

Umami links an imported payment to a visitor when you identify that visitor with a distinct ID and pass the same ID to your provider as umami_distinct_id. Lemon Squeezy isn't supported for this (Umami docs). traffic.cx reads a pageview ID in the browser when checkout starts and adds it to checkout metadata, so guest checkouts work without a login (how it works). Lemon Squeezy checkouts pass it as custom data (Lemon Squeezy guide).

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. Connecting Stripe, Lemon Squeezy, Polar or Dodo Payments also imports that provider's last 90 days of payments, so your revenue totals don't start at zero. Those older payments will mostly be Unattributed.

Two attribution models with a configurable lookback#

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). Umami credits an imported payment to the visitor's most recent visit in the previous 90 days (Umami docs).

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

Where Umami Analytics is the better choice#

• Open source and self-hosting. Umami is MIT-licensed, and you can run it on your own server with Node.js and PostgreSQL (GitHub, install docs). Self-hosted data is kept until you delete it. traffic.cx isn't open source and can't be self-hosted.
• A bigger free tier. Umami Cloud Hobby is free for up to 100,000 events a month with 6 months of retention (Umami pricing). traffic.cx's Free plan has 3,000 events a month and shows the last 30 days.
• Product analytics. Journeys, retention, segments and cohorts on every plan, and session replays and heatmaps on Business (Umami docs). traffic.cx focuses on traffic and revenue.
• More payment providers. Umami also connects Paddle and WooCommerce (Umami docs). traffic.cx doesn't.
• Data import and full export. Umami Cloud can import your existing data on paid plans and exports all of a website's raw data. traffic.cx can't import Umami data and exports report tables only.
• Community. Umami has community plugins for WordPress, Nuxt, Gatsby, Docusaurus and more (Umami docs). traffic.cx is newer and smaller.

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.

Umami Cloud: Hobby $0 (up to 100K events a month, 1 website, 6-month retention); Pro $20/month (1 million events included, then $0.00003 per event, up to 20 websites); Business $200/month (10 million events, then $0.00002 per event); Enterprise custom (umami.is/pricing), as of 29 October 2026. Paid subscriptions start with a 14-day free trial. Self-hosting the open-source version has no licence fee. You pay for your own server and database. Prices may change. Check Umami pricing for the current numbers.

How to switch from Umami 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 Umami or any other analytics tool, so your history starts when you install the script. Umami Cloud exports a website's data as CSV (Umami docs). Self-hosted data stays in your own database.

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 umami.track('name') calls with window.trafficcx?.('name') and create a matching custom-event goal in the dashboard. Events that only carried revenue and currency may not be needed 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. You can keep any umami_distinct_id metadata while you compare. Test with your provider's test mode on a separate traffic.cx test site. Connecting Stripe, Lemon Squeezy, Polar or Dodo Payments imports that provider's last 90 days of payments. Those older payments will mostly be Unattributed.

7. Run both while you compare, then remove the Umami script. traffic.cx is safe to run alongside Umami'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 (how the script stays separate).

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.

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

• Pricing (plans and feature table)
• Subscription (14-day trial, spending budget)
• Features (cookies, data import, pixels, links; footer "Umami Software, Inc.")
• GitHub (MIT licence)
• Install
• FAQ (self-hosted retention)
• Revenue
• Attribution
• Payment providers and integrations
• Cloud (Cloud versus self-hosted)
• Import
• Export
• Community integrations
• Sub-processors (last updated 24 Apr 2026)