GA4 alternatives and comparisons
Peeko vs PostHog when you only need traffic and when you need the whole product suite
By Nora Blake · Nov 16, 2026 · 9 min read
We did not run both tools on one site, so nothing below is a benchmark. Every claim about PostHog comes from its own docs and pricing page, read in November 2026, and those pages change. Every claim about Peeko comes from what Peeko does and what its pricing page says.
What you are choosing between
PostHog's pricing page lists product analytics, session replay, feature flags and experiments, surveys and error tracking, each with its own free tier. Web analytics is part of the first one: "Web Analytics is included with Product Analytics at no extra cost." The web analytics dashboard shows visitors, pageviews, sessions, average session duration and bounce rate, and it runs on the $pageview events the PostHog SDK sends.
Peeko is one script tag with a site key. It sets no cookie and needs no configuration once it is on the page. The scope is narrower on purpose: page views, clicks, goals, funnels, revenue, search data from Google and Bing, and AI crawler hits.
The question is whether the extra products are something you will use. If the answer is no, you are choosing between two ways to read traffic. If the answer is yes, that decides it.
Price, as of November 2026
PostHog has a free plan with no card, 1 project and 1 year of data retention. The paid plan has a $0 base price, 6 projects and 2 years of retention, and you pay only for usage above each product's monthly free tier. There are no per-seat charges. These are the free tiers and first paid rates on the pricing page:
- Product analytics: the first 1,000,000 events each month are free, then $0.00005 per event for the next 1,000,000.
- Session replay: the first 5,000 recordings are free, then $0.005 per recording up to 15,000.
- Feature flags and experiments: the first 1,000,000 requests are free.
- Surveys: the first 1,500 responses are free. Error tracking: the first 100,000 exceptions are free.
Peeko has one plan on a slider from 100,000 to 10,000,000 events a month, $9 to $199 monthly, and yearly is two months free. Its pricing page lists $49 a month for 1,000,000 events. Every feature is on every size, with unlimited sites and unlimited team seats. The trial is fourteen days with no card and covers one site. AI crawler hits are never billed, and nothing stops recording when you pass your limit.
On cost alone, a site under 1,000,000 events a month pays $0 for PostHog analytics and at least $9 for Peeko. That is a real difference and we will not argue around it. One caution: the two tools do not count the same thing. A Peeko event is a page view, an outbound click or a custom event, counted over the UTC calendar month. Check what your PostHog project actually sends before you assume the volumes line up.
Source: PostHog, PostHog pricing, Nov 13, 2026. Retrieved Nov 13, 2026.
Retention is the other number on both pricing pages. 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. PostHog's free plan keeps data one year and its paid plan two. If you want to compare this month with the same month two years ago, check that your plan keeps the data.
Cookies and visitor identity
PostHog's JavaScript SDK defaults persistence to localStorage+cookie, per its configuration reference. It has a cookieless mode, and you turn it on in the SDK:
posthog.init('<ph_project_api_key>', {
api_host: '<ph_client_api_host>',
cookieless_mode: 'always',
})
The data collection docs say this mode "never stores PostHog data in cookies or local/session storage" and counts users with a privacy-preserving hash calculated on PostHog's servers. You must also enable it in the project's Web analytics settings, because "if this setting is off, PostHog discards cookieless events." The same page lists limits: alias() is not supported, events lose their IP address before transformations run so they get no GeoIP or bot detection enrichment, and you "should avoid identifying users in this mode."
Peeko has no mode to switch on. A visitor is the first part of a one way keyed hash of their address and browser string, and the address itself is never written to a database or a log. The hash behind the People number mixes in the date and is re salted every day, so nobody can be followed from one day to the next. A second hash without the date tells a returning visitor from a new one and strings page views into a journey. That second hash is the identity behind goals, funnels and revenue. Whether that design fits your own privacy position is your call. We are describing the mechanism, not giving legal advice.
AI crawlers and bots
This is where the two designs differ most. PostHog's bot traffic docs say: "Most bots and AI agents never run JavaScript, so the SDK never sees them." To measure them you forward server or CDN logs as $http_log events, and each needs $raw_user_agent set. The HTTP logs page also requires $current_url and does not say whether those events are billed like regular events. The Bots tab "is in alpha and rolling out gradually," and may not be enabled for your project yet.
PostHog's classification uses a user agent pattern list plus operator-published crawler IP ranges, and sorts traffic into AI Agent, Bot, Automation or Regular. It also says some crawlers, such as ChatGPT-User browsing and Bing preview fetches, send real browser user agents, so the source IP is the only reliable signal.
Peeko handles crawlers on a separate server side path, because crawlers do not run JavaScript. You add 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 a crawler 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 that path at all. The raw user agent is kept up to 512 characters, so old hits can be reclassified as the list grows.
The tradeoff follows from that design. Peeko's crawler path has no address, so it cannot use IP ranges. A fetch that arrives with an ordinary browser user agent is outside what a user agent list can recognize, and PostHog's docs name exactly that case. In exchange, there is nothing to forward and nothing to bill. Separately, Peeko counts visits from ChatGPT, Claude, Perplexity, Copilot and Gemini from ordinary page views by their referrer, with no middleware involved. If you add either tool's crawler counts to a report, read how one scanner in costume can inflate an AI crawler count first.
Goals, funnels and revenue
PostHog's web analytics setup tells you to define a conversion goal as an action, and recommends capturing an explicit event like user_signed_up rather than relying on autocapture. It also lists marketing analytics, in beta, which pulls cost, clicks and impressions from ad platforms such as Google, Meta and LinkedIn.
On Peeko a goal is a definition rather than a counter, so a goal written today counts over months before it was written, and a site can hold twenty. Five kinds of click are recorded with no code: outbound, phone, email, whatsapp and form. Anything else is a data-peeko-event attribute or a window.peeko.event call. A funnel holds two to five steps and follows a person rather than a visit, and a two step funnel works from traffic you already recorded. Revenue arrives through a one line window.peeko.revenue call 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.
Where PostHog is the better choice
Pick PostHog in these cases:
- You need session replay. PostHog gives 5,000 recordings free each month. This post describes nothing like it on the Peeko side.
- You need feature flags or experiments. PostHog gives 1,000,000 requests free each month, billed together. Peeko is not a product for shipping flags.
- You are under 1,000,000 events a month and want to pay nothing. PostHog's free plan covers that. Peeko's smallest size is $9 a month.
- You want product analytics on signed in users. PostHog supports
identify()and lists surveys and error tracking beside analytics, all under one bill. - You want to self host. PostHog's open source release can be self hosted, but its own disclaimer says it is "unlikely to scale past a couple 100ks events" and that it can offer only limited support. For most companies it recommends PostHog Cloud. If self hosting is the point, our Umami comparison covers a tool built for it.
A suite also costs you attention. More products means more settings, such as the cookieless project toggle above, and more to read before the traffic numbers mean something.
Where Peeko fits better
Peeko fits when the job is "tell me what my traffic is doing" and you would rather not configure anything. It is one script tag. Every feature is on every size, including goals, funnels, revenue and the AI crawler tab. Crawler hits are never billed. Google Search Console and Bing Webmaster Tools connect read only, with encrypted tokens, and their rows are kept for sixteen months.
Both tools can be read from a coding agent. PostHog lists an MCP server for Cursor, Claude Code and VS Code. Peeko hosts one at usepeeko.com/api/mcp, read only except for one tool that creates a site, and npx @usepeeko/cli speaks the same endpoint, so a command and a tool call return the same numbers. Setup is in connecting Claude Code or Cursor to your traffic and installing analytics in one agent session.
How to decide
Ask three questions in order:
- Do you need replay, flags, experiments or surveys this quarter? If yes, use PostHog.
- Do you need to see AI crawler hits without forwarding logs and without a bill that grows with them? If yes, that points to Peeko.
- Will you run under 1,000,000 events a month and read only traffic? Then price favors PostHog and setup favors Peeko. Weigh which one you will actually feel.
If you are not sure what a site already loads, the free analytics checker lists which of 18 analytics tools one page loads, with no signup. It reads the HTML your server sends, so it cannot see tags added later by a tag manager or held back by a consent banner.