GA4 alternatives and comparisons
Peeko vs Pirsch on price, bots, funnels and self hosting
By Jonas Reed · Nov 20, 2026 · 10 min read
This comparison uses Pirsch's own documentation and pricing pages for everything about Pirsch, and Peeko's published facts for everything about Peeko. We did not run both tools on one site, so there is no head to head count here. Where the two tools define a number differently, we explain it from the definitions.
| What matters | Peeko | Pirsch |
|---|---|---|
| Works without a cookie banner | Sets no cookie | No cookies used to collect data |
| Counts AI crawler visits | Server side, 55 agents from 21 companies | Requests made directly by AI are ignored |
| Funnels with a stated completion window | 1 hour, 1 day, 7 days or 30 days | Up to eight steps, Plus only, no window stated |
| Agent access over MCP supported by the vendor | Hosted, read only except one tool | Community server, not supported by Pirsch |
| Self hosting | We make no self hosting claim | Enterprise License only |
| Event properties | One name, one optional string | Up to 20 key value pairs |
| Unlimited data retention | Three years by default, 30 days to ten years | Unlimited on every plan |
| Price, as of Nov 2026 | $9 a month at 100,000 events, up to $199 at 10,000,000 | $6 a month Standard from 10,000 page views, $12 a month for 100,000 page views per its Matomo page |
| Best for | People who want AI crawler hits and journeys that last days | Small sites, self hosters, and people who want event detail |
Price at the traffic you have
Source: Pirsch, Best Matomo Alternative, 2026-11. Retrieved Nov 13, 2026.
The two tools price on different axes, and that is the first thing to get straight. As of Nov 2026, Pirsch's pricing page lists Standard at $6 a month and Plus at $12 a month, shown against an example of 10,000 monthly page views. Its Matomo comparison page says Pirsch "costs $12 per month for 100,000 page views" and does not name the plan. We could not find a full tier table on the pricing page, and it lists page views as "Variable" for Plus, so check the live slider before you decide. The yearly discount is not given in dollars either: the page only says "You save per year!"
Peeko is one plan on a slider from 100,000 to 10,000,000 events a month, 9 to 199 dollars monthly, and yearly is two months free. At the low end that is $9 a month for 100,000 events.
The units are close but not identical. Pirsch's pricing page says "Custom events and 10% of events for session extensions count towards your monthly page view limit." Peeko counts a page view, an outbound click or a custom event, over the UTC calendar month. Peeko never bills an AI crawler hit.
What happens past the limit differs too. Pirsch's billing docs say access is limited to the day you hit the limit, and "We will continue to collect data for your sites for five days before we stop accepting page views." In Peeko, nothing stops recording when you pass your limit.
Two other plan differences matter at the price level. On Pirsch, funnels, A/B testing, custom domains and white labeling are listed under Plus, not Standard. On Peeko every feature is on every size, with unlimited sites and unlimited team seats. Pirsch Standard allows 50 websites and unlimited members; Plus allows unlimited websites.
What the two tools do the same
Both tools work without cookies. Pirsch's cookieless tracking page says: "Because Pirsch does not use cookies to collect data, there is no need for consent banners". Peeko sets no cookie either, and it is one script tag with a site key that needs no configuration once it is on the page.
Both also build the visitor from a hash. Pirsch's privacy policy says "The IP address, the user agent, the date and a salt serve as input values," and that the address is "neither fully nor partially persisted." The same policy says visitors "cannot be recognized for longer than 24 hours." Peeko stores no IP address either. Its People number counts the first part of a one way keyed hash of the address and browser string, mixed with the date and re-salted every day, so nobody can be followed from one day to the next.
Where they split is what happens after that daily hash. Pirsch's statistics page says "A visitor is only counted once within a 24 hour window" and that a session lasts up to 30 minutes after the visitor was last seen. Peeko keeps a second hash without the date. That hash tells a returning visitor from a new one, strings page views into a journey, and is the identity behind goals, funnels and revenue. Which design you prefer depends on whether you need to know what a person did across several days. We come back to that in the funnel section.
Bots and AI crawlers
Pirsch filters bots out. Its FAQ says "We block most data center IP addresses to protect our customers from spam," and that a request "may be dropped if we think it's a bot request." Its statistics page adds that "requests made directly by AI are ignored as non-human traffic." Pirsch still tracks AI referrals when a visitor arrives from an AI source. So Pirsch answers "how many people came from an assistant" and drops the crawlers from the numbers.
Peeko does that part too. Visits from ChatGPT, Claude, Perplexity, Copilot and Gemini are counted from ordinary page views by their referrer, with no middleware. The method is written up in how to count visits from ChatGPT, Claude, Perplexity, Copilot and Gemini.
The difference is the crawler itself. Crawlers do not run JavaScript, so a script tag never sees them. Peeko reads them on a separate server side path with the @usepeeko/bot-track middleware, which is ESM only, needs Node 20 or newer, has zero runtime dependencies and weighs under 3 KB gzipped. It matches the user agent against a curated list of 55 agents from 21 companies and files each hit under AI answers, Search indexing, AI training or Other AI bots. No address and no visitor hash exist on that path, and the raw user agent is kept up to 512 characters so old hits can be reclassified as the list grows.
Pirsch's docs, as we read them, describe crawler traffic as something removed, not something reported. If you want to see which models fetch your pages, that is a Peeko feature and not a Pirsch one. If all you want is a clean human count, Pirsch's behavior is what you asked for. For what a first month of crawler data looks like, see which AI crawlers reach a new site in its first 30 days.
One install detail is worth knowing. Pirsch's FAQ says its tracking endpoints "always return a status code of 200," and that a 200 does not confirm a page view was saved, because requests are processed asynchronously. Peeko's ingest endpoint answers 204 to every well formed beacon, valid key or not, so a tracker can never leak whether a key is real. In both cases, a status code alone does not tell you the data arrived. Check the dashboard.
Events, goals and funnels
Pirsch is more capable on event detail. Its events docs say "You can send up to 20 metadata key-value pairs," with keys up to 100 characters and values up to 2,000 characters. Peeko takes one name and one optional string, with no properties object. Five kinds of click are recorded 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.
Funnels are where the two designs diverge. Pirsch's funnel docs say "You can define up to eight steps," built from pages, page patterns, custom events or tags, and call funnels a Plus feature. The page states no completion window. Pirsch's privacy policy says visitors cannot be recognized for longer than 24 hours, so a funnel that spans days is worth asking Pirsch about before you rely on it. That is our inference from two documents, not a statement either one makes.
Peeko's funnel holds two to five steps, a completion window of 1 hour, 1 day, 7 days or 30 days, covers at most 90 days, and follows a person rather than a visit. A site can hold ten. A goal is a definition and not a counter, so a goal written today counts over months before it was written, and a site can hold twenty. If you have never set one up, two step funnel from traffic you already recorded shows the whole thing.
Agents, the terminal and your data
Peeko hosts an MCP server at usepeeko.com/api/mcp. It is read only except for one tool that creates a site, reached with a bearer API key and scoped to the sites of the teams you belong to. The command line needs no install:
npx @usepeeko/cli
It speaks the same endpoint an agent does, so a command and a tool call return the same numbers. There is a walkthrough in read your site traffic from a terminal.
Pirsch's MCP page describes "an unofficial integration created by the community" that Pirsch does not support. It is read only, needs Node.js 22.19 or later and a Pirsch OAuth client, and provides three tools. Access keys starting with pa_ will not work because they are write-only.
For export, Pirsch's export docs name CSV of aggregated statistics, with "raw data exports and custom formats upon request." On retention, Pirsch lists unlimited data retention on every plan. Peeko keeps page views, events and crawler hits three years by default, and a site owner can set that anywhere from 30 days to ten years.
Where Pirsch is the better choice
Pick Pirsch in these cases, going by its own documentation:
- Your site is small. At about 10,000 page views a month, $6 on Standard is less than Peeko's $9 floor, and Peeko's floor is 100,000 events.
- You need to self host. Pirsch's FAQ says "Yes, you can host Pirsch yourself by purchasing an Enterprise License," and recommends the hosted plan for smaller companies and personal projects. Peeko is the hosted product described here, and we make no self hosting claim.
- You want event properties. Up to 20 key value pairs per event beats one name and one string.
- You want longer funnels. Eight steps against five.
- You want unlimited retention rather than a window you set.
- You want a longer trial. Pirsch offers a 30 day trial with no credit card; Peeko's is 14 days with no card, and covers one site.
Where Peeko fits better
Pick Peeko if you want to see AI crawler hits per page and per bot, if you want funnels, goals and revenue to follow a person over days rather than a day, or if you want an agent to read your numbers from a hosted MCP endpoint that the vendor supports. Revenue arrives one of two ways, a one line window.peeko.revenue call from your own site or a verified Stripe webhook, and the two totals are never added together. Peeko never holds a Stripe API key; the only credential it stores for revenue is the webhook signing secret.
Pick it too if you do not want to choose a plan before you can use a feature. There is one plan, every feature is on, and AI crawler hits are never billed. That is the edge, and it is slight: if your site is under 10,000 page views a month and you only want a clean human count, Pirsch costs less and does exactly that.
If you switch
Run both for a short overlap if you want to compare totals, and expect them to differ. The cause will be definitions, not a bug: Pirsch counts a visitor once per 24 hours and drops requests it takes for bots, and Peeko's People number is a daily hash with crawlers on a separate path. The free analytics checker shows which of 18 analytics tools a page loads, which is a quick way to confirm that only the tags you meant to keep are still there afterward. For another head to head, we have written Peeko vs Plausible from the same kind of source material.
Everything about Pirsch above was read from pirsch.io and docs.pirsch.io in Nov 2026. Pirsch can change its prices and limits, so confirm them on its pricing page before you pay.