# GeckoStats

> Privacy-friendly web analytics that ties every visit to revenue. It answers which traffic brought
> paying customers, not just which traffic arrived. Hosted, from $9 a month, with a
> seven-day free trial.

GeckoStats is a hosted service. You add one script tag to a website you own and connect a payment
provider; there is nothing to install, operate, back up or update, and there is no self-hosted
edition. The script is cookieless by default, so it needs no consent banner in the EU, and a
visitor's identity is derived per website rather than shared across them.

## What it measures that an ordinary analytics tool does not

- **Revenue per source.** Payment webhooks (Stripe, Creem, Polar, Dodo) are matched back to the
  session that led to them, so a channel is reported in dollars rather than in sessions.
- **AI crawlers.** Which assistants read your pages, what for (training, search, answers, agent),
  how many pages each read, and how many visitors it then sent. Reported by the site's own
  middleware, because a crawler runs no JavaScript and the tracker cannot see it.
- **Search Console, joined to money.** Queries, Discover, index verdicts and Core Web Vitals sit
  beside the revenue of the pages they belong to, so "not indexed" has a cost attached.
- **A live globe** of who is on the site right now, and per-visitor profiles and funnels.

## Plans

Priced by events a month, on a slider from 25K to 10M events.

- **Starter**: For one site and one person. 1 site. From $9 a month.
- **Growth**: For several sites and the people who work on them. Up to 30 sites. From $19 a month.

Yearly billing is ten months for the price of twelve. Every plan starts with seven days free, and
every size includes every payment provider, Search Console, the AI assistant and the MCP server.

## Pages

- [Home](https://geckostats.com): what it does, pricing, FAQ.
- [Live demo](https://geckostats.com/demo): a working dashboard on generated traffic, no sign-up.
- [Help and contact](https://geckostats.com/help): how to reach a person, and the common problems with their fixes.
- [Terms](https://geckostats.com/terms), [Privacy](https://geckostats.com/privacy), [Data Processing Agreement](https://geckostats.com/dpa), [Refunds](https://geckostats.com/refund).

## Compared with the alternatives

Each page says what the other product does better as well as what this one does. Every figure in
them was read off the other product's own pages, and the month it was checked is on the page.

- [vs Plausible](https://geckostats.com/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.
- [vs Fathom](https://geckostats.com/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.
- [vs Google Analytics](https://geckostats.com/vs/google-analytics): GA4 is free, and that is a real argument. What it costs you instead is a consent banner, a 14-month ceiling on user data, and an afternoon every time you want a number out of it.
- [vs DataFast](https://geckostats.com/vs/datafast): This is the closest comparison on the site. Both join payments to visits, both have visitor profiles, funnels and an MCP server. The honest differences are narrower than either of us would like.
- [vs Simple Analytics](https://geckostats.com/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. What it does not do is tell you which visit turned into money.
- [vs Umami](https://geckostats.com/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. The case for paying us is narrow and specific.

## The MCP server

Every website exposes an MCP endpoint at `https://geckostats.com/api/mcp`, HTTP transport, authenticated with
a bearer token that is that website's own API key. A key reads one website and is revocable from its
settings. There are 26 tools; 24 of them
only read, and the two that write are `create_funnel` and `rematch_payments`.

- **Traffic.** The numbers the dashboard opens on, for any period you ask for.
  `site_overview`, `top_pages`, `top_sources`, `top_goals`, `breakdown`, `geography`, `devices`, `realtime`
- **Money and people.** Who paid, who came back, and what a channel is worth.
  `customers`, `subscriptions`, `visitors`, `visitor_profile`, `retention`, `list_funnels`, `funnel_stats`
- **Search.** Search Console joined to the revenue of the pages it sends people to.
  `search_queries`, `seo_opportunities`, `index_status`, `ctr_pressure`, `ai_vs_search`
- **Speed and releases.** Core Web Vitals from real visits, and what you shipped when.
  `vitals`, `deploys`
- **Setup and admin.** The only two tools in the whole set that write anything are create_funnel and rematch_payments. The other 24 only look.
  `list_sites`, `site_install`, `create_funnel`, `rematch_payments`

Each tool runs the same query the dashboard runs, so it returns the figure on screen or an error,
never an approximation. Set-up pages, with the exact command or config file each client wants:

- [Claude Code](https://geckostats.com/integrations/claude-code): Ask in the terminal.
- [Cursor](https://geckostats.com/integrations/cursor): Ask inside the editor.
- [ChatGPT](https://geckostats.com/integrations/chatgpt): A connector in the chat.
- [Gemini CLI](https://geckostats.com/integrations/gemini-cli): One entry in settings.json.
- [Hermes](https://geckostats.com/integrations/hermes): An MCP server in the config.
- [GrokBot](https://geckostats.com/integrations/grokbot): The same tools, from Grok.

Any other MCP client works the same way; only the registration differs.

## The other AI features

- **An assistant in the dashboard.** Ask in plain English and it calls the same tools and shows the
  calls it made. The question and the aggregated results are sent to Anthropic to compose the
  answer; nothing is sent unless you ask.
- **AI crawler tracking.** Which assistants read your pages, what for (training, search, answers,
  agent), how many pages each took and how often. Reported by your own server's middleware, because
  a crawler executes no JavaScript and no tracker can see it.
- **AI referrals, against everything else.** Visitors arriving from ChatGPT, Claude, Perplexity,
  Gemini, Copilot and DeepSeek, with their revenue, conversion rate and revenue per visitor set
  beside organic search, so "is AI sending us anything" has a number rather than an opinion.
- **This file is measured.** Requests for /llms.txt are counted and reported in the AI crawlers
  panel, under the `llms` format. A tool that tells you who reads your llms.txt should have one.

## For developers

- The tracking script is at https://geckostats.com/js/script.js and takes a `data-website-id`. Under 2 kB,
  cookieless by default, honours Global Privacy Control and Do Not Track.
- A REST API over every figure the dashboard shows, with the same per-website key.
- Server-side events, payments, deploys and crawler hits are posted to `/api/v1/*`.
- Payment providers connect by webhook: Stripe, Polar, Creem, Dodo Payments. Anything else
  is one API call carrying the amount and the visitor id.