GA4 alternatives and comparisons
Peeko vs Fathom on price, cookies, bot handling and where Fathom wins
By Jonas Reed · Nov 8, 2026 · 8 min read
Everything below about Fathom comes from Fathom's own pricing page and documentation, read in November 2026, and each claim links to its page. Everything about Peeko comes from what Peeko documents about itself. We did not run both tools on one site, so this post compares documented behavior and makes no claim about whose numbers are closer to the truth.
Price: what each plan costs and what it counts
Fathom sells ten fixed plans. As of November 2026, the Fathom pricing page lists $15 a month for 100,000 pageviews, $60 for 1,000,000 and $200 for 10,000,000. Past 25,000,000 pageviews you talk to Fathom. Yearly billing is two months free.
Source: Fathom Analytics, Fathom Analytics pricing, 2026-11-05. Retrieved Nov 5, 2026.
Peeko has one plan on a slider from 100,000 to 10,000,000 events a month, priced from $9 to $199 monthly, with yearly billing at two months free. Every feature is on every size. The Peeko pricing page shows the $9 starting price.
Read the two numbers with care, because the meters are close but not identical. Fathom's pricing page says pageviews and custom events share your allowance. Peeko counts events, and an event is a page view, an outbound click or a custom event, measured over the UTC calendar month. Peeko records outbound clicks with no code, so a site with many of them will use more of a Peeko plan than its page views and custom events alone suggest. On both tools, every custom event you add uses the allowance the same way a page view does.
At the bottom of the range Peeko costs $6 less a month. At 10,000,000 the two are $1 apart ($199 against $200). Price will not decide this for you unless you sit near the bottom.
Other limits worth knowing:
- Trial. Fathom has a 7-day trial that requires a card. Peeko has a 14-day trial with no card, and it covers one site.
- Sites. Fathom says every plan includes at least 50 sites, with extra packs of 50 at $10 a month. Peeko includes unlimited sites and unlimited team seats on every size.
- Going over. Fathom says it will never turn your analytics off for occasional traffic spikes. If you stay well over, it emails you, and it may pause dashboard and API access after reminders while it keeps collecting data. On Peeko, nothing stops recording when you pass your limit.
- History. Fathom lists full analytics history while you are subscribed. Peeko keeps page views, events and crawler hits three years by default, and the owner can set that window anywhere from 30 days to ten years.
Cookies and identity: the same promise, a different tradeoff
Neither tool sets a cookie. Fathom's cookie documentation says its analytics does not use cookies or similar technologies, and that other scripts on your page may still set them. Peeko is one script tag with a site key, it sets no cookie, and it needs no configuration once it is on the page. For the legal side of this, see the Washington pixel ruling and what it settles for small sites.
The difference is how each tool recognizes a person across days. Fathom's measurement documentation says each visitor gets a signature that rotates every 24 hours at midnight UTC, and states: "There are no cookies and no cross-day tracking." A person who visits Monday and Tuesday is two visitors.
Peeko does the same for its People number: the hash it counts mixes in the date and is re-salted daily, so nobody can be followed from one day to the next. But Peeko also keeps a second hash without the date. That hash is what tells a returning visitor from a new one, strings page views into a journey, and is the identity behind goals, funnels and revenue. No IP address is ever stored by Peeko. A visitor is the first part of a one-way keyed hash of the address and browser string.
So this is a real tradeoff, not a tie. If you want an analytics tool that cannot connect Monday's visit to Tuesday's under any setting, Fathom's documented design is the more minimal one. If you want to know that the person who read your pricing page on Monday signed up on Thursday, you need the second hash, and Fathom's documentation says it does not do that. Fathom's features page does not list funnels either.
Bots and AI crawlers: filtered out or counted
This is the largest difference between the two, and it follows from what each tool is for.
Fathom's bot detection documentation says it classifies each request when it reaches Fathom's servers, using known bot user agents, datacenter IP ranges and missing user agents. Blocked traffic is "never included in your pageviews, visitor counts, or event data." A toolbar icon shows how many requests were blocked, with a breakdown by classification and by country. That is a good default if you want clean human numbers. The page does not say whether crawlers that never run JavaScript are recorded at all, so we cannot tell you what Fathom shows for them.
Peeko treats crawlers as a separate measurement. Crawlers do not run JavaScript, so AI crawler tracking is a separate server-side path: the @usepeeko/bot-track middleware is ESM only, needs Node 20 or newer, has zero runtime dependencies and weighs under 3 KB gzipped. Peeko matches a user agent against a curated list of 55 agents from 21 companies and files every recognized hit under AI answers, Search indexing, AI training or Other AI bots. No address and no visitor hash exist on the crawler path at all. AI crawler hits are never billed.
Visits that arrive from ChatGPT, Claude, Perplexity, Copilot and Gemini are a third thing. Peeko counts those from ordinary page views by their referrer, with no middleware involved. Fathom's features page does not mention AI referrals, so if that number matters to you, ask Fathom whether it reports them. Our own post on counting visits from AI assistants by referrer shows how the referrer method works.
Events, funnels and revenue
Fathom tracks custom events with fathom.trackEvent, and its events documentation shows an optional value in cents:
fathom.trackEvent('newsletter signup', { _value: 100 });
That covers a signup count and a simple revenue total. Peeko records five kinds of click with no code at all: outbound, phone, email, whatsapp and form. Anything else is a data-peeko-event attribute or a window.peeko.event call, with one name and one optional string and no properties object:
<button data-peeko-event="signup">Create account</button>
Three Peeko behaviors have no counterpart in the Fathom pages we read:
- A goal is a definition rather than a counter, so a goal written today counts over months before it was written. A site can hold twenty.
- A funnel holds two to five steps, follows a person rather than a visit, and covers at most 90 days. See how to build a two step funnel from traffic you already recorded.
- Revenue arrives one of two ways, a one-line
window.peeko.revenuecall or a verified Stripe webhook, and the two totals are never added together. Peeko never holds a Stripe API key, only the webhook signing secret. Report revenue from your site or let Stripe confirm it covers the choice.
Peeko also reaches your agent. It hosts an MCP server at usepeeko.com/api/mcp, and npx @usepeeko/cli speaks the same endpoint, so a command and a tool call return the same numbers. Fathom documents an API for bringing data into your own tools, which is the closest equivalent in its pages.
Where Fathom is the better choice
Pick Fathom when one of these is true:
- You need EU processing. Fathom's EU isolation documentation says EU visitors are processed in the EU by default, along with Iceland, Liechtenstein, Norway, Switzerland and the UK. Loading
https://cdn-eu.usefathom.com/script.jsroutes all global traffic through the EU. We make no equivalent statement here, so a requirement about where data is processed should send you to Fathom first. - You want cleaner human-only numbers by default. Fathom removes bots before they reach any count and shows a blocked total. If you do not care about crawlers and only want to see people, you get that with no further setup.
- You send reports to other people. The Fathom features page lists scheduled weekly or monthly emails, CSV downloads, and shared dashboards that can be public or password protected. Peeko share links are no-sign-in pages behind a 32 character token, up to ten per site, and they never show goals, funnels, individual visitors or the AI crawler tab.
- You want to run it yourself. Fathom still publishes Fathom Lite, a self-hosted version. Its page says "With Lite, you're on your own," and lists missing pieces: Device Types, Browsers and Countries metrics, Events and Email Reports.
- You want cross-day anonymity as a rule. The daily-rotating signature with no cross-day tracking is a simpler thing to explain to a privacy-minded audience than a second hash.
Where Peeko is the better choice
Pick Peeko when you ship with an AI coding agent and want to see which crawlers reached your pages. Pick it when you need journeys, funnels or goals that count backward, or when you want unlimited sites and seats on one price. If you are still unsure what your site loads today, the analytics checker shows which of 18 analytics tools any page loads, with no signup.
A short way to decide
- If a legal or contractual rule says where data is processed, start with Fathom.
- If the question you ask most is "which AI crawlers and assistants reached me", start with Peeko.
- If you only need page views and a weekly email, either works, and the $6 difference at 100,000 will not matter much.
- If you track conversions beyond a count, compare funnels and revenue first, because they are where the two diverge most.
For the same comparison against another privacy-first tool, read Peeko vs Plausible from each tool's docs and pricing.
Prices and limits above are as of November 2026 and change. Check Fathom's pricing page and Peeko's before you buy.