GeckoStats vs Plausible
Both are cookieless, both fit in a page of numbers rather than a reporting suite. The difference is what the numbers are about: Plausible counts visits, GeckoStats follows them to the payment.
Seven days free, no card. Checked against their own pages in November 2026.
Which one should you actually use?
Plausible and GeckoStats are both cookieless, both need no consent banner anywhere in the EU, and both fit on one screen rather than in a reporting suite.
Plausible is the more established product, open source under AGPLv3, hosted in the EU, and with a longer track record than ours.
GeckoStats goes further in one direction: revenue attributed back to the source that produced it, per-visitor journeys, funnels on every plan, and 26 tools your AI agent can call.
| GeckoStats | Plausible | |
|---|---|---|
| Revenue | ||
| Revenue attribution | From the provider’s webhook The payment arrives from your payment provider carrying the visitor id, so the amount is theirs rather than your front end’s, a refund takes the sale back off the chart, and every source, campaign, page and query is ranked by the money instead of the traffic. | Revenue on goals Ecommerce revenue attribution is a Business tier feature, $19 a month at 10,000 pageviews. The value is sent as a goal from your own code, not taken from a payment provider. |
| Every visitor’s journey | Open any payment A session-by-session trail for one anonymous visitor, from an identity that rotates daily: the source that first brought them, every page and click, the days between visits, and the payment at the end. | No Deliberately: Plausible does not build a per-person view, which is part of its privacy position rather than a gap. |
| Funnels and goals | On every plan Button clicks and signups as goals, then step-by-step drop-off between them, with the revenue that came out of the last step. | Business tier Funnels and user journeys are listed on the Business plan. |
| Subscriptions and MRR | Yes MRR, churn and lifetime value broken down by source: which channel brings customers who stay, rather than which brings the most first payments. | Not listed Not on their pricing or documentation pages when we checked. |
| Visitors | ||
| Campaigns, with revenue | Yes A tagged link per tweet, article or newsletter issue. It appears by name with the visitors and the money it brought, including people who came back and bought a fortnight later. | Yes Full UTM support, with visitors against each campaign. Revenue beside them needs the Business tier and a goal you send. |
| Live view | A globe, and a feed Everyone on the site right now on a rotating globe, with pages, goals and payments landing in a feed beside it. | Realtime dashboard A live visitor count and a current-visitors view. |
| Returning visitors | Yes New against returning for the period, week-by-week retention, and what the people who came back were worth. | Yes Returning visitor breakdowns are part of the standard reports. |
| Content and search | ||
| Search Console, with revenue | Built in Connect it once and every query, page and country you rank for arrives with the money its page earned beside it, so the list is ordered by what it is worth rather than by clicks. | Search Console import Queries, clicks and positions imported from Google, without the money the page earned beside them. |
| AI crawlers and AI referrals | Both halves Which assistants read your pages, named, and what each one sent back: the visitors arriving from ChatGPT, Claude, Perplexity and Gemini, with their revenue and conversion rate against everyone else’s. | Not listed Not on their pricing or documentation pages when we checked. |
| Core Web Vitals | From real visits LCP and INP measured on your actual visitors, shown beside the revenue of the page, so a slow page that earns is the one you fix first. | Not listed Not on their pricing or documentation pages when we checked. |
| For developers | ||
| Release markers | Yes One curl at the end of your deploy puts a marker on the chart, so a drop can be read against what you shipped rather than guessed at. | Not listed Not on their pricing or documentation pages when we checked. |
| MCP server for AI agents | 26 tools Your agent calls the same queries the dashboard runs, with a key issued per website and revocable. Twenty-four of the twenty-six only read; the two that write create a funnel and re-run attribution. | No There is a Stats API on the Business tier, limited to 600 requests an hour. |
| REST API and server events | On every plan Read every figure the dashboard shows, and post payments, goals, deploys and crawler hits from your own backend with the same key. | Business tier Stats API at 600 requests an hour, plus an events API for server-side events. |
| Alerts | Yes Tracking stopped, revenue down, organic clicks down, a page deindexed, a query dropped five places. Emailed when it happens rather than found a week later. | Email reports Weekly and monthly email reports, and traffic spike notifications. |
| Privacy | ||
| Cookies and consent banner | None by default A visitor is a salted hash that rotates daily and the IP is never stored, so there is nothing on the device to consent to anywhere in the EU. Global Privacy Control and Do Not Track are honoured in the script and again in the collector. | None No cookies and no persistent identifiers, the same position as ours. |
| Open source | No A hosted product. The tracker is the only part that runs on your side, and there is no self-hosted edition. | AGPLv3 Plausible CE is open source and self-hostable; the tracker script is MIT. |
| Where it runs | Cloudflare A United States company, on its global network. Data at rest is encrypted; no IP addresses are stored at all. | European Union Made and hosted in the EU, on European-owned infrastructure. |
| Data retention | As long as the site exists No ceiling and no tier. Deleting a website deletes its events, visitors and payments in the same minute, and deleting the account does that for every website it owns. | Not listed Not on their pricing or documentation pages when we checked. |
| Price | ||
| Entry price, and the meter | From $9 a month Counted in events, which is pageviews plus anything you tag yourself: 25,000 for $9, 100,000 for $19 on Starter. Seven days free, no card, every feature on. | From $9 a month Counted in pageviews: 10,000 for $9 on Starter. The tier with revenue and funnels is Business, from $19, and custom events count against the same 10,000. |
| Websites and seats | 1 on Starter, 30 on Growth Seats match the websites: just you on Starter, up to thirty on Growth. | 1, 3 or 10 by tier Starter one site, Growth three sites and three members, Business ten and ten. |
| Free tier | Seven-day trial No card, and every feature is on during it. | 30-day trial No card required, and no free plan afterwards. |
Where something is marked “not listed”, it means we could not find it on their pages, not that it does not exist. Plausible’s figures were read off their own pricing and documentation pages in November 2026. Found something out of date? Tell us and we will correct it.
The screens you would be moving to
Not a description of them. The same tiles the front page shows, and the same live demo behind them.
Every customer’s full journey
Who paid, where they came from, how long it took. Open anyone and read every page and click from first visit to payment.
Chrome- 7:31 PM/pricing
- 7:33 PMcheckout_click on /pricing
- 7:35 PMPaid $49
- 9:02 AM/blog/ship-faster
X / Twittercampaign: launch-tweet2m 40s- 2:14 PM/
- 2:15 PM/pricing
Traffic and revenue in one view
Blue shows visitors and orange shows revenue. See how they move together, then drill into the channels and sources behind each spike.
Point your AI agent at it
An MCP server with 26 tools over your own numbers, so you ask in plain English instead of reading a dashboard. Twenty-four of them only read, the key is issued per website, and you can revoke it whenever you like.
Claude Code~/sites/nimbusWhat actually differs
01Revenue attribution
Plausible tracks revenue on custom goals, on the Business tier. It does not attribute a payment back to the visit and the source that produced it. Ours arrives on the payment provider's own webhook, so the amount is the provider's, a refund reverses the sale, and the payment opens into the visitor behind it.
02Every visitor's journey
A session-by-session trail for one anonymous visitor: the pages, the clicks, the campaign that first brought them and the day they paid. Plausible aggregates by design and keeps no per-person view, which is part of its privacy position rather than an omission.
03Bringing your history
Plausible imports from Google Analytics. We import from nothing, deliberately: no two analytics tools count a session the same way and a merged chart has a visible seam at the join. Run both tags for a week instead; neither sets a cookie, so it costs nothing.
04Starting price, and the meter
The meters differ, so read them carefully. Plausible counts pageviews and starts at $9 for 10,000, with revenue and funnels on the $19 Business tier. We count events, which is pageviews plus anything you tag, and start at $9 for 25,000 with everything on.
Moving across from Plausible
Add our script beside Plausible rather than instead of it, and run both for a week. The numbers will not match to the visitor, because no two analytics tools count a session the same way, but the shape will. When you are satisfied, connect the payment provider and drop the other tag.
What it costs
Priced by events a month, with everything on both plans except the number of sites and seats.
Starter
For one site and one person.
Billed monthly · up to 100K events
7 days free trial
- Realtime dashboard
- Live Globe
- User Profiles
- Funnels
- Revenue tracking
- Core Web Vitals
- and 9 more, on every plan
Growth
RecommendedFor several sites and the people who work on them.
Billed monthly · up to 100K events
7 days free trial
- Realtime dashboard
- Live Globe
- User Profiles
- Funnels
- Revenue tracking
- Core Web Vitals
- and 9 more, on every plan
Every plan starts with 7 days free. No commitment, cancel anytime. Prices exclude VAT, which may apply at checkout.
GeckoStats and Plausible: the questions people ask
Is GeckoStats a drop-in replacement for Plausible?
For the traffic half, yes: visitors, sources, pages, countries, devices, goals and a realtime view, with the same cookieless tracker and no banner. The part that is not a replacement is the open-source one. If you are self-hosting Plausible to own the server, we are not the same kind of product.
Can I import my Plausible history?
Not today. Both products count a visit differently enough that a merged history would be a chart with a seam in it, and we would rather say so than ship a button that produces one. Run the two side by side for a week instead.
Plausible has revenue attribution too. What is different?
Plausible attributes revenue you send it as an ecommerce event. We take the webhook from the payment provider itself, which means the amount comes from the provider rather than your front end, a refund takes the sale back off the chart, and the payment opens into the visitor who made it.
Do I need a cookie banner with either?
No. Neither product sets a cookie or stores an IP address, which is the thing a consent banner exists to ask about.
Comparisons with the other five
vs Fathom
Fathom charges one price for everything it has and keeps your data forever.
vs Google Analytics
GA4 is free, and that is a real argument.
vs DataFast
This is the closest comparison on the site.
vs Simple Analytics
Simple Analytics is the most privacy-forward product in this comparison and it has a free plan that is not a trial.
vs Umami
Umami is the most generous product in this comparison: MIT licensed, self-hostable for nothing, and free in the cloud up to 100,000 events.
See which traffic pays, this week.
Add the script, connect your payment provider, and the next sale arrives knowing where it came from.
7 days free · no commitment · cancel anytime
