Vercel Web Analytics
Vercel's cookie-free visitor analytics for projects deployed on Vercel, enabled per project in the dashboard.
Vercel Web Analytics is the visitor analytics built into Vercel. For each project it shows visitors, pageviews, bounce rate, top pages, referrers, countries, operating systems, browsers and devices, and on Pro and Enterprise also custom events and feature flag usage. It doesn't use cookies: a visitor is identified by a hash of the incoming request that resets every day.
You enable it on a project in the Vercel dashboard, which adds tracking routes to your next deployment, then add the @vercel/analytics npm package: an <Analytics /> component for Next.js, React, Remix, Vue and Astro, a Nuxt module, or an inject() call elsewhere. Plain HTML sites add a script tag pointing at the project's own path instead. The script and its data intake are served from paths on your own domain, and custom events can also be sent from server code.
A small team gets visitor analytics inside the platform it already deploys on, with no separate account or script vendor. Hobby includes 50,000 events a month; on Pro every event is billed, and a Web Analytics Plus add-on adds UTM reports and a longer reporting window.
It is built for projects deployed on Vercel: enabling it adds the tracking routes to your next Vercel deployment. Hobby keeps one month of history and, once its monthly allowance is used up, pauses collection after a 3-day grace period; Pro keeps 12 months. Events are counted across every project in the team. Custom events need Pro and carry at most 2 custom properties (8 with Web Analytics Plus), with no nested objects and no name or value longer than 255 characters.
Where it fits
Who uses it
No maker's live product on record yet, and 105 open-source projects that declare it in their code.
We haven't found a maker's live product that uses Vercel Web Analytics yet — only the open-source projects below, which declare it in their code.
Open source: a project that declares Vercel Web Analytics as a dependency in its public code — verifiable, but not necessarily a live product.
Alternatives to Vercel Web Analytics
All alternatives by situation →Questions makers ask about Vercel Web Analytics
Does it use cookies?
No. Visitors are identified by a hash created from the request, valid for one day, so they can't be followed across days or across websites. source ↗
What data is stored for each pageview?
A timestamp, URL and dynamic route, referrer, filtered query parameters, location, OS, browser and device type; no IP address or personal identifier is attached. source ↗
Can I track custom events on the Hobby plan?
No. Custom events, from the browser with track() or from server code with @vercel/analytics/server, are available on Pro and Enterprise. source ↗
Do I need Next.js?
No. There are integrations for Next.js, SvelteKit, Remix, Nuxt, Vue, Astro and React, an inject() function for other frameworks, and a plain script tag for static HTML, though the last two don't track route changes. source ↗
Can I keep personal data out of URLs?
Yes. A beforeSend function lets you rewrite page view and event URLs before they are sent, for example to strip names or IDs from paths. source ↗
What happens when a Hobby project runs out of events?
Hobby can't buy more events. After a 3-day grace period collection pauses until the next billing cycle, or until you upgrade to Pro. source ↗
Is Vercel Web Analytics free?
Yes — there is a free tier a small product can run on; paid use starts at $0.03 per 1,000 events on Pro. source ↗
Is Vercel Web Analytics open source or self-hostable?
Not open source, and hosted only.
Can AI coding agents work with Vercel Web Analytics?
No llms.txt, official MCP server or CLI found yet.
Who uses Vercel Web Analytics?
No maker's live product we track yet; 105 open-source projects declare it in their code. source ↗