In this article
Vercel Web Analytics comes with every Vercel plan, sets no cookies and, for a Next.js app that's already on Vercel, takes a switch in the dashboard, one package and one component. For a lot of sites that's all the analytics they need. Several of the features you might go looking for elsewhere depend on the plan.
So before you compare tools, check which of those things your plan leaves out, and whether a plan change would cover it. Everything about Vercel below comes from its own documentation, as of November 2026. Vercel changes its plans and features regularly, so check the current docs before you decide.
What Vercel Web Analytics does well
No cookies
Vercel says Web Analytics doesn't use cookies. A visitor is a hash created from the incoming request, and the hash is valid for one day, so nobody can be followed from one day to the next or from one site to another.
Part of the deployment
You switch it on per project, under Analytics in the Vercel dashboard, and the next deployment gets routes that serve the script and receive the data on your own domain. For Next.js, Vercel's quickstart adds the @vercel/analytics package and its Analytics component to the root layout or _app.
Page changes and routes
Vercel says page views are tracked on fresh page loads and on client-side page transitions. With its framework components, pages are also grouped by route, such as /blog/[slug]. The plain HTML version has no route support.
Filters and drill-downs
Clicking a row filters every panel: pages, routes, hostnames, referrers, countries, browsers, devices and operating systems. The Referrers panel drills down from a domain to the pages that linked to you. Clicking a t.co link opens a search on X that can lead back to the post it came from.
Traffic that Vercel identifies as automated, from the user agent, isn't counted. Pro plans add custom events, and the same data can be read through Vercel's API, its CLI and its MCP server, so an AI assistant can query it too. If your sites are on Vercel and pages, referrers and countries are what you look at, there may be nothing to switch from.
What depends on your plan
Vercel prices Web Analytics by events, and the plan decides which features you get. These figures are from its pricing page for Web Analytics.
| Hobby | Pro | Pro with Web Analytics Plus | Enterprise | |
|---|---|---|---|---|
| Events | 50,000 a month included. More can't be bought | $0.03 per 1,000, against Pro's monthly usage credit | $0.03 per 1,000, plus $10 a month per team for the add-on | Custom |
| History you can view | 1 month | 12 months | 24 months | 24 months |
| Custom events | No | Yes, with 2 properties each | Yes, with 8 properties | Yes, with 8 properties |
| UTM parameters | No | No | Yes | Yes |
An event is a page view or a custom event, and the count is shared by every project in the team, so one busy site uses up the allowance for the others. When a Hobby team reaches its limit, Vercel doesn't charge. It stops collecting after a three-day grace period.
Campaign tags need Web Analytics Plus or Enterprise
If you share links in newsletters, social posts or ads, UTM tags are how you tell those visits apart. In Vercel's list of filters, UTM parameters are marked as available with Web Analytics Plus and Enterprise.
On Hobby, and on Pro without the add-on, there's no way to pick out a tagged campaign in the dashboard. Vercel's Pages panel shows the address without its query string, so a visit from a tagged link is counted by its page and by its referrer, if the browser sent one. Links opened from email apps, PDFs and chat apps often arrive with no referrer at all, so those campaigns blur into one another and into what most tools call direct traffic.
If you're on Pro, the add-on is the direct fix. On Hobby it means moving to Pro first. Whichever tool reads your tags, they only help if they're consistent, and a small naming convention keeps them that way.
AI assistants: referrers, and a separate bot view
A click from ChatGPT, Perplexity or Claude reaches Web Analytics like any other visit. If the browser sends the assistant's address as the referrer, it shows up in the Referrers panel under that domain, among all the others. Vercel's Web Analytics docs don't describe a separate group for AI assistants, so adding them up is up to you.
Some of those visits carry no referrer, because links opened from apps often arrive without one. For ChatGPT there's a second signal: OpenAI says ChatGPT adds utm_source=chatgpt.com to referral links from its search results. That tag is a UTM parameter, so on a plan without UTM parameters it can't be used, and a visit that has only the tag looks like any other visit without a referrer.
Vercel does have an AI Traffic tab, under Observability rather than Web Analytics, added in October 2026. It shows requests from AI bots, split into crawlers that index or train on your pages and assistants that fetch a page on a user's behalf, with the paths each requests most. Those are fetches, not people who clicked through, and an assistant can read a page many times without sending a single visitor. The guide to AI referral traffic explains why crawls are not clicks.
A page an assistant fetched is not a visitor it sent. Read the AI Traffic tab and the Referrers panel as two different questions.
It runs where your deployment runs
Web Analytics is built for projects deployed on Vercel. Switching it on adds routes to your next deployment, and those routes serve the script and receive the data. A site hosted somewhere else doesn't get those routes. Vercel also advises against putting a reverse proxy in front of Vercel, because a proxy can affect the country data and how visitors are identified.
That's convenient when everything you run is on Vercel. If you also have sites elsewhere, their numbers live in another dashboard. One setup detail from Vercel's troubleshooting page is worth knowing too: if the tracking code was deployed before Web Analytics was switched on, the script can return a 404 and no data arrives. Switch it on, redeploy and promote the latest deployment to production.
Match the gap to the tool
You probably don't need a tool that does everything. You need one that fills the gap you actually have, and sometimes that's a different Vercel plan.
| If you're missing | Look for |
|---|---|
| Campaign tags | Web Analytics Plus on Pro, or a tool that records utm_source, utm_medium and utm_campaign without an add-on. Check its pricing page for which plan includes them. |
| More than a month of history | Pro keeps 12 months and Web Analytics Plus 24. Elsewhere, a tool whose documentation states its data retention. |
| Signups and button clicks | Custom events, which Vercel has on Pro and Enterprise. Or a tool with events or goals, and funnels if you want to see where people drop off. |
| Clicks from AI assistants | A tool that groups assistants by referrer and by utm_source, or a referrer filter you build yourself. |
| Sites on other hosts | A script-tag tool that works on any host, so every site ends up in one dashboard. |
| Revenue next to traffic | A tool that reads your payment provider, or one of the other ways to put the two on one chart. |
Run both before you switch
You don't have to switch in one go. Running both for a while is the safest way to decide.
- Leave Vercel Web Analytics on. It keeps counting while you try the other tool.
- Add the other tool's tag once, in the root layout or
_app. There's a step-by-step guide to where a script tag goes in Next.js. - Mind your Content Security Policy. Vercel's script loads from your own domain, so
'self'covers it. The second tool's domain needs to be inscript-srcandconnect-src. - Check on your production domain with ad blockers off, and look for your visit in the new tool's live or real-time view.
- Run both for two to four weeks. Compare page views day by day and note the ratio between the tools. A steady ratio means both are working, even if the totals differ.
- Don't expect unique visitors to match. Vercel's visitor hash resets every day, and other tools count people differently. The rest of the usual gaps are in why no two analytics tools agree on your traffic.
- Start a new trend line on the day you switch. Last month in one tool next to this month in another shows a jump or a drop that is only the tools disagreeing.
- Turn off the one you drop properly. For Vercel, its docs say to remove the
@vercel/analyticspackage, then choose Disable Web Analytics on the project's Web Analytics page.
Vercel Web Analytics is a sensible default for sites hosted on Vercel. If something is missing, find it among the gaps above first, since some of them are closed by a plan change rather than a new tool.
Lomen is one of the script-tag tools described above. It works on any host that can load a script tag, Vercel included, and today it reads UTM tags with no add-on. It recognises visits from nine AI assistants, including ChatGPT, Claude and Perplexity, by referrer and by utm_source, and can put revenue from Stripe, Shopify, Lemon Squeezy, Polar and Paystack on the same chart as visitors, added together rather than split by source. Lomen AI, a chat in the dashboard, answers questions about your site's own figures. It sets no cookies and never stores IP addresses. It has no custom events or funnels. If you need custom events, Vercel's Pro plan has them and Lomen doesn't. Lomen is free during its public beta, and the planned pricing on the pricing page is not final.