GeckoStats vs Fathom
Fathom charges one price for everything it has and keeps your data forever. GeckoStats costs less to start and answers a different question: not how many came, but which of them paid.
Seven days free, no card. Checked against their own pages in November 2026.
Which one should you actually use?
Fathom and GeckoStats are both cookieless, both need no consent banner, and both put every feature in front of you rather than behind a tier.
Fathom has the simpler offer and the longer track record: one price, fifty sites, data kept forever, and no feature tiers at all.
GeckoStats goes further in one direction: a payment joined to the visit that produced it, per-visitor journeys, Search Console with the money beside each query, and 26 tools your AI agent can call.
| GeckoStats | Fathom | |
|---|---|---|
| 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. | Events you send Event and revenue tracking on every plan, with the value coming from your own front end. It is not joined back to the visit and the source that produced it. |
| 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 Fathom aggregates by design and keeps no per-person view. |
| 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. | Not listed Not on their pricing or documentation pages when we checked. |
| 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 UTM tracking on every plan, with visitors against each campaign. |
| 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 Current visitors, updating live. |
| Returning visitors | Yes New against returning for the period, week-by-week retention, and what the people who came back were worth. | Not listed Not on their pricing or documentation pages when we checked. |
| 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. | Not listed Not on their pricing or documentation pages when we checked. |
| 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 an analytics API on every plan. |
| 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. | On every plan Analytics API, with no tier gate. |
| 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 Unlimited email reports on every plan. |
| 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 cookie banner required, 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. | Fathom Lite only The hosted product is closed. Fathom Lite is a separate, older, self-hosted version that uses cookies and has no API. |
| Where it runs | Cloudflare A United States company, on its global network. Data at rest is encrypted; no IP addresses are stored at all. | EU isolation available An EU data isolation option is offered; specific locations are not detailed on the pricing page. |
| 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. | Forever Data kept for as long as you are a customer, on every plan. Better than ours on paper and with years behind it. |
| 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 $15 a month Counted in pageviews: 100,000 for $15, 500,000 for $45. Every feature is on every plan. |
| Websites and seats | 1 on Starter, 30 on Growth Seats match the websites: just you on Starter, up to thirty on Growth. | 50 on every plan No tiering by site count at all. |
| Free tier | Seven-day trial No card, and every feature is on during it. | 7-day trial A card is required to start it. |
Where something is marked “not listed”, it means we could not find it on their pages, not that it does not exist. Fathom’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
Fathom has event and revenue tracking on every plan, with the value sent from your own front end. Ours comes from the payment provider's webhook, so the amount is the provider's, a refund takes the sale back off the chart, and the payment is joined to a visit rather than to a number.
02Every visitor's journey
A session-by-session trail for one anonymous visitor, from an identity that rotates daily: first source, pages read, clicks, and the day they paid. Fathom aggregates and keeps no per-person view.
03Sites, and what you are buying
Fathom gives fifty sites on every plan. Starter here is one site and Growth is thirty. If you are counting sites rather than revenue, theirs is simply the better deal and we would rather say so than bury it.
04Starting price, and the meter
Fathom counts pageviews: $15 for 100,000, with a seven-day trial that takes a card. We count events, which is pageviews plus anything you tag: $9 for 25,000, $19 for 100,000, and seven days free without a card.
Moving across from Fathom
Run both tags for a week. Fathom counts pageviews and we count events, so the two totals will not line up; what should line up is which sources are at the top. Then connect your payment provider, give it a few real sales, and decide with the money on screen.
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 Fathom: the questions people ask
Fathom gives 50 sites for $15. Why would I pay you?
If the fifty sites are the point, you should not. We are cheaper for one site that sells something and more expensive for thirty that do not. The question worth asking is whether you need to know which visitor paid, because that is the thing the price difference buys.
Fathom has ecommerce tracking. Is that the same as revenue attribution?
Not quite. Theirs is an event you send with a value on it, which means your own code decides what the number is and a refund does not take it back. Ours comes from the payment provider over a webhook, so the amount is the provider’s, a refund reverses the sale, and the payment opens into the visitor behind it.
Can I import my Fathom data?
No. Run the two side by side for a week rather than merging two different ways of counting into one chart.
Do either of you need a cookie banner?
No. Neither sets a cookie for analytics.
Comparisons with the other five
vs Plausible
Both are cookieless, both fit in a page of numbers rather than a reporting suite.
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
