See Vercel Analytics for multiple projects at once

Why it’s awkward today

Vercel Web Analytics is per project: each project has its own Analytics page. Vercel’s own CLI documentation lists team-wide reporting among the queries the dashboard doesn’t offer. If you run a few dozen sites, “which ones grew this week?” means a lot of tabs. There are four ways to see multiple projects together, each with its own cost.

1. Click through each project’s Analytics tab

Open a project, then Analytics in the sidebar, pick the timeframe and read the numbers (Vercel’s guide). This is the most detailed view there is: filters, pages, routes, referrers, UTM parameters on plans that have them, custom events, bounce rate, CSV export.

The cost is time and memory. Comparing ten sites means ten page loads and a notepad, and the comparison is gone once you close the tabs. It works well for two or three projects.

2. Query them with the Vercel CLI

vercel metrics reads Web Analytics from the terminal. According to the same documentation, it can query every project in the current team at once: pass --all and group by projectId, for example page views per project for the last 7 days.

It’s free and quick for one question. The trade-offs: it covers one team per run, the output is a table in a terminal, a change against last week is a second query you compare yourself, and nobody without the CLI and access to the team can see it. It’s a good tool for developers and a poor one for the person who asked.

3. Write a script against the API

Vercel’s Web Analytics API returns visitors and page views per project, as totals or grouped by day, country, referrer and more. A script can list your projects, query each one and write the results wherever you like: a spreadsheet, a Slack message, your own dashboard.

You own all of it, though: a token per team, one request per project per question, the previous period, rate limits, caching and somewhere to show the result. The Web Analytics API guide walks through what that involves.

4. Use a dashboard built for it

Lookout reads the same data through the same API and puts multiple projects on one screen: visitors, page views and pages per visit for each, against the previous period, with top referrers and countries. You see them as a grid of cards, a sortable table, or a chart comparing up to five projects, for the last 24 hours, 7 days, 30 days or a custom range. It handles several Vercel teams in one workspace, up to 100 tracked projects.

Beyond the view itself, you can group sites into boards (one per client, say), send a client a read-only link to their board, and put a board on an office TV. It shows less per site than Vercel: no filters, one custom event per site (as a goal), and pages per visit instead of bounce rate. For those, you still open Vercel.

Side by side

These aren’t exclusive. A common setup is Lookout for the daily overview across multiple projects, and Vercel’s own tab when one site needs a closer look. Lookout is free; try the demo with 12 sample projects first, or read how it compares with Vercel’s built-in Web Analytics.