GA4 alternatives and comparisons
Peeko vs Vercel Web Analytics for sites that already deploy on Vercel
By Theo Marsh · Nov 17, 2026 · 10 min read
Vercel Web Analytics is a feature of the Vercel platform, not a standalone product. That shapes every comparison below. Everything about Vercel here comes from its own documentation and pricing pages, read in November 2026, and each claim links to the page it came from. We did not run both tools on one site, so nothing here is a measured difference in counts. Where the two tools count differently, we explain it from their documented definitions.
Setup: a Vercel project versus one script tag
Vercel's quickstart lists a Vercel account and a Vercel project as prerequisites. You enable Web Analytics in the dashboard, add the @vercel/analytics package or a script tag, and deploy to Vercel. Enabling it adds new routes under /_vercel/insights/* after your next deployment. The same page includes a ready-made agent prompt, so a coding agent can do the install. That is a real convenience if your agent is already deploying to Vercel.
Peeko is one script tag with a site key. It sets no cookie and needs no configuration once it is on the page. Nothing in that install depends on where the site is hosted, so the same tag works on a Vercel site, a Cloudflare Pages site and a plain VPS. The practical difference is simple: Vercel's tool requires Vercel, and Peeko does not.
What an event is, and what it costs
Both tools bill by events, and both count a page view as one. Vercel says an event is either an automatically tracked page view or a custom event. Peeko counts a page view, an outbound click or a custom event, over the UTC calendar month.
Vercel's numbers, as of November 2026:
- Hobby: 50,000 events a month included, no additional events can be bought, and no custom events.
- Pro: no events included, then $0.03 per 1,000 events.
- Pro with the Web Analytics Plus add-on: the same $0.03 rate, plus $10 a month per team.
- Events are shared across every project in the team.
Pro itself is $20 a month, which includes $20 in usage credit that can be spent across all infrastructure resources. So the analytics line is not a clean standalone price. If you already pay for Pro hosting, analytics events draw from a credit you are already carrying.
Peeko is one plan on a slider from 100,000 to 10,000,000 events a month. As of November 2026 its pricing page shows $9 a month at 100,000 events and $49 at 1,000,000, with yearly billing at two months free. The slider tops out at $199. Every feature is on every size, and there are unlimited sites and team seats.
Source: Peeko, Peeko pricing, Nov 2026. Retrieved Nov 14, 2026.
The chart mixes plan prices that cover different things, so read it as a list of published numbers and not a ranking. Our arithmetic from the published rates, before any credit: 1,000,000 events at $0.03 per 1,000 is $30 on Vercel, against $49 on Peeko. At 10,000,000 events it is $300 on Vercel against $199 on Peeko. The two lines cross in between: at 2,000,000 events it is $60 on Vercel against $79 on Peeko, and at 5,000,000 it is $150 against $139, so the crossover sits between those two sizes.
Two behaviors at the limit differ. On Hobby, Vercel says that after a three day grace period collection stops until the next cycle. Peeko never stops recording when you pass your limit, and AI crawler hits are never billed.
Cookies and what identifies a visitor
Vercel says it does not use cookies: visitors are identified by a hash created from the incoming request, and the hash is valid for a single day before it resets. Its docs say this means visitors cannot be tracked between different days or different websites. The privacy page says the session lifespan is discarded after 24 hours.
Peeko also sets no cookie, and no IP address is ever stored. A visitor is the first part of a one way keyed hash of their address and browser string. 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 in that number.
Here is the difference you should know about. Peeko keeps a second hash without the date. It tells a returning visitor from a new one, strings page views into a journey, and is the identity behind goals, funnels and revenue. Vercel's design gives that up on purpose. If you want the strictest daily reset and nothing more, Vercel's model is the more conservative one. If you want to ask whether the same person came back on Thursday and bought on Saturday, you need the second hash.
Custom events, goals, funnels and revenue
Vercel's custom events need Pro or Enterprise. The custom events docs give you a track() function, a server-side track() for API routes and server actions, and key-value data on each event. Values can be strings, numbers, booleans or null, nested objects are not supported, and names, keys and values are capped at 255 characters. The limits page lists 2 properties per event on Pro and 8 with Web Analytics Plus.
Peeko records five kinds of click with no code: 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. That is less expressive than Vercel's.
Where Peeko goes further is on what you can do with the events afterward:
- 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. We cover the low-volume case in setting up a first goal when you only get a few signups.
- A funnel holds two to five steps, a completion window of 1 hour, 1 day, 7 days or 30 days, and follows a person rather than a visit. A two step funnel built from traffic you already recorded shows the shape.
- Revenue arrives through 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.
Vercel's API docs mention funnels as a use for event queries, but the pages we read describe event counts and visitor counts, not a funnel builder, a goal definition or revenue reporting. We may have missed a page, so check the docs for your case.
Bots and AI crawlers
Vercel's docs say Web Analytics does not count traffic from automated processes or accounts, decided by inspecting the User Agent header. That is a filter, and the docs describe nothing that reports what the filtered traffic was.
Crawlers do not run JavaScript, so a script-based tool cannot see them anyway. Peeko handles this on 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. It matches a 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.
That is extra setup compared with a script tag, and you need a server where middleware can run. To judge whether the numbers are worth the effort, read how to see which AI crawlers reach a new site in its first 30 days.
Visits that arrive from ChatGPT, Claude, Perplexity, Copilot and Gemini are a separate question. Peeko counts them from ordinary page views by their referrer. Vercel records the referrer too, and its Referrers panel shows the referring URL, but only for the initial page view and only if the referring link allows it. Counting visits from AI assistants by referrer explains what that does and does not capture.
Getting the data out
Vercel gives you three routes, all documented. The dashboard exports up to 250 entries per panel as CSV. A Web Analytics API queries page views, visitors and custom events with filters and group-by. And vercel metrics queries from a terminal, which the CLI docs say works without Observability Plus.
Peeko hosts an MCP server at usepeeko.com/api/mcp, read only except for one tool that creates a site. You reach it with a bearer API key, scoped by construction to the sites of the teams you belong to. The command line needs no install:
npx @usepeeko/cli
It speaks the same MCP endpoint an agent does, so a command and a tool call return the same numbers. See reading your traffic from a terminal with no dashboard open. Peeko also connects Google Search Console and Bing Webmaster Tools read only, and keeps their rows for sixteen months. The Vercel pages we read do not mention a search console connection.
On retention: Vercel's reporting window is 1 month on Hobby, 12 months on Pro and 24 months with Plus or Enterprise, and the docs say only the window is guaranteed to be stored. Peeko keeps page views, events and crawler hits three years by default, and the owner can set anything from 30 days to ten years.
Where Vercel Web Analytics is the better choice
Pick Vercel when most of these are true:
- Your site is on Vercel and stays there. There is no second vendor, no second bill, and one dashboard sits next to your deployments.
- Your traffic is low and you are on Hobby. 50,000 free events a month costs nothing, and Peeko's trial is fourteen days, after which the entry price is $9.
- You are on Pro already. At 1,000,000 events the published rate is about $30 before credit, below Peeko's $49. Add the $10 Plus add-on for UTM parameters and a 24 month window and it is still under $49.
- You need rich event data. Up to 8 properties per event, and server-side events from an API route, beat Peeko's one name and one optional string.
- You use Preview and custom environments. The dashboard can split Production, Preview and any custom environment such as staging. Peeko's facts do not include an equivalent.
- You want framework-level routes. Vercel can group by route pattern, such as
/blog/[slug], so many URLs roll into one row.
If that list describes you, you do not need a second analytics tool, and adding one is extra work for little gain.
Where Peeko fits better
- The site is not on Vercel, or is on several hosts. One script tag works anywhere you can edit a page.
- You need to know which AI crawlers are reading you. Vercel filters them out. Peeko counts them and never bills for them.
- You want goals and funnels over data you already have. A goal written today counts past months, and funnels follow a person across days.
- You sell something. Revenue from a webhook or one line call, with the sale tied to its page and source through a page token minted per page view and good for 48 hours.
- You expect high volume. At 10,000,000 events the slider ends at $199, below $300 at Vercel's published rate before credit.
- You keep several small sites. One plan covers unlimited sites and unlimited team seats, while Vercel's events are pooled across a team's projects.
A check before you decide
Before choosing either, find out what your pages already load. Sites built with an AI coding agent often carry more than one analytics script, and the free analytics checker shows which of 18 analytics tools a page loads, with no signup.
If the answer is one script, on Vercel, with a handful of custom events, keep Vercel Web Analytics. If you are missing crawler counts, funnels or revenue, those are the gaps Peeko was built to close.