Skip to content

Comparison

traffic.cx vs Plausible

Both are simple, cookieless web analytics. The difference is where revenue comes from: Plausible records revenue your website sends with an event, while traffic.cx reads payments from your payment provider and links them to visits.

Plausible facts checked on 15 October 2026 from its own website. See the sources.

The short answer

Plausible may suit you better if

  • You need analytics hosted only in the EU, or code you can audit and run yourself.
  • Revenue is a side question and you mostly want a mature, private traffic dashboard.
  • You want to bring your Google Analytics history with you.

traffic.cx may suit you better if

  • You sell through Stripe, Dodo Payments, Lemon Squeezy or Polar and want refunds and renewals in your revenue.
  • You want to switch between first-touch and last non-direct attribution.
  • You want revenue attribution from the smallest plan ($7/month for 10k events).

Side by side

Topictraffic.cxPlausible
Where revenue comes fromPayments from a connected provider, the Payments API or the tracking script. The checkout carries traffic.cx visit IDs.Revenue values attached to custom events, sent by your site’s script or the Events API.
Refunds and renewalsRefunds reduce revenue on the day they happen. Renewals keep the customer’s earlier attribution.Not described in the revenue documentation; it covers events sent after a purchase.
AttributionFirst touch or last non-direct, with a 7 to 365-day lookback. Unlinked payments stay visible as Unattributed.The source that started the visitor’s session stays credited for the conversion.
Revenue features by planEvery paid plan has the same features.Ecommerce revenue attribution, funnels and custom properties are on the Business plan.
Price with revenue, 10k a month$7/month (10k pageviews and custom events)Business plan, $19/month (10k pageviews; custom events count too)
SitesUnlimited sites on every paid plan.1 on Starter, up to 3 on Growth, up to 10 on Business.
Visitor cookiesNone by default. An optional cookie mode links visits across days.None.
HostingA server in India, delivered through Cloudflare. Not EU-only.Made and hosted in the EU.
Source codeA closed service.Public source code; you can run it yourself.
Importing historyNot available yet.Google Analytics import on every plan.
Free trial7-day trial with up to 10,000 events, no card, one per Google account30 days, no card

Revenue: events or payments

Plausible builds revenue on custom events. Your site sends an amount and currency, usually from a thank-you page, and Plausible converts currencies and breaks revenue down by source and campaign. It is simple to add when your site knows the amount.

traffic.cx starts from the payment record instead. You connect a provider and pass two visit IDs in checkout metadata; the payment arrives from the provider and is linked to the visit. Refunds and subscription renewals come from the same provider, so revenue stays net of refunds and renewals keep their original source. A payment with no matching visit shows as Unattributed rather than being assigned a guess.

If your checkout is not one of the four providers, both products accept revenue from your own code: Plausible through events, traffic.cx through the Payments API or the tracking script.

Privacy and hosting

Both count visitors without cookies by default. Plausible keeps all visitor data on EU-owned servers and publishes its code. traffic.cx runs on a server in India behind Cloudflare and is a closed service. If EU-only processing or self-hosting is a requirement, Plausible fits that requirement and traffic.cx does not.

traffic.cx also offers an optional first-party cookie, which links a visitor’s visits across days for longer attribution. It changes your consent obligations, so it is off until you turn it on.

Price for the same traffic

For a site with 10k pageviews and custom events a month that wants revenue attribution, Plausible’s Business plan is $19/month and traffic.cx is $7/month. Plausible’s Starter plan is $9/month for 10k pageviews without revenue attribution or funnels. Both count custom events toward the limit and offer two months free on yearly billing. Prices for larger volumes are on each pricing page.

Trying traffic.cx alongside Plausible

You can run both scripts on the same site while you compare. Install the traffic.cx snippet, connect your payment provider and add the visit IDs to your checkout. Your Plausible history stays in Plausible: traffic.cx cannot import it yet, so its reports start from the day you install it.

Try it on your own traffic

See how revenue attribution works, then follow the setup guide for your payment provider.

Sources

Plausible details come from these pages, checked on 15 October 2026. Products and prices change, so check them before you decide. traffic.cx details come from our pricing, privacy notice and revenue documentation. Spotted something out of date? Tell us.