Lookout vs. Vercel's built-in Web Analytics
How Lookout relates to Vercel Web Analytics: it reads from it and adds a cross-project view, client links, alerts, reports and an API. When to use which.
Last updated October 21, 2026
Not a replacement: a view on top
Lookout doesn’t collect analytics itself. Vercel Web Analytics does the collecting on your sites, and Lookout reads it through Vercel’s API. So the question isn’t which one to use: you keep Vercel Web Analytics, and add Lookout when you have more projects than you want to open one by one.
Side by side
| Vercel Web Analytics | Lookout | |
|---|---|---|
| Where the data comes from | Collected by Vercel on your sites | Read from Vercel Web Analytics; it adds no events to your Vercel bill |
| Scope | One project at a time | All tracked projects side by side, across teams, grouped into boards |
| Compare projects | Open each project | Grid, sortable table and a chart of up to five projects |
| Visitors and page views | Yes | Yes, with the change on the previous period |
| Referrers, countries, pages | Yes | Yes, per project |
| Devices, browsers, operating systems | Yes | Yes, per project |
| Filters | Yes, by page, referrer, country, device and more | Search by name, domain, tag or team, and a movers filter; no per-visit filters |
| UTM campaigns | With Web Analytics Plus or Enterprise | A Campaigns card per project, when Vercel has the UTM data |
| Custom events | Pro and Enterprise | One per site, as a goal with its conversions and rate |
| Bounce rate | In Vercel’s dashboard | Not in Vercel’s API; Lookout shows pages per visit |
| History | 1 month on Hobby, 12 on Pro, 24 with Web Analytics Plus | What your plan keeps; a dash, not a misleading change, where the previous period is missing |
| Alerts | Usage and error alerts, not visitor changes | An email when a project’s visitors drop or spike past your threshold |
| Reports | No scheduled reports | A weekly digest, and PDF or CSV reports by email; PNG, PDF and CSV exports |
| API and AI assistants | REST API and MCP tools, one project per query | A read-only API, an MCP server and webhooks across every tracked project |
| Who can see it | Your Vercel team; Pro’s free Viewer seats see every project in the team | Workspace members, without a Vercel seat |
| Share with a client | Make them a Viewer, which shows them all of the team’s projects | A read-only link to their board only, with an optional password and expiry |
| Wall display | No | Monitor mode: a full-screen board for a TV or office screen |
When Vercel’s dashboard is enough
If you have one or two projects, or you need to dig into a single site (filter by page or device, follow a custom event through its properties), Vercel’s own dashboard is the right place. It has more detail per project than Lookout shows.
When Lookout helps
- You run many projects, for clients, campaigns or products, and want to see which ones grow or drop at a glance.
- You want to compare projects against each other, not just against their own past.
- A client should see their own numbers and nothing else. A Vercel Viewer seat is free on Pro, but it opens every project in the team; a share link shows one board.
- You’d rather hear about a drop than find it: alerts and a weekly digest come by email.
- You want the numbers on a screen in the office: monitor mode shows a board full screen and keeps it current.
- You want to ask about your traffic in Claude or Cursor, or pull it into your own tools, across every project at once: Lookout’s API and MCP server.
Agencies are the typical case: here’s how agencies use Lookout. Or try the live demo with sample data.
Cost and access
Lookout is free for up to 100 projects and 5 members per workspace. It only reads, so it adds no events to what Vercel bills you for Web Analytics. It needs a Vercel access token with read access to the team (how to create one), and the projects need Web Analytics enabled in Vercel. It works on Hobby too, within the month of data Hobby keeps.