Vercel Web Analytics
Vercel Web Analytics connection fields, team projects, credential overrides, capabilities, and common connection errors.
The quickstart covers first-time setup. This page is for looking up Vercel-specific requirements, fields, and capabilities.
About Vercel Web Analytics
Vercel Web Analytics reports traffic to a Vercel project. This package reads what Vercel has already collected and shows it in Umbraco. It does not add tracking to the public site.
Requirements
The connection needs a Vercel access token scoped to the account or team that owns the project. The token lives in server-side configuration and is never stored in Umbraco.
Connection fields
| Field | Value |
|---|---|
| Credential setting | WebAnalytics__Providers__Vercel__AccessToken |
| Project ID | Vercel project identifier beginning with prj_... |
| Team | Optional for a personal project; for a team-owned project, use its team_... ID or slug |
Add these values in Settings → Web Analytics. For connection errors such as 401, 403, or 400, see Vercel troubleshooting.
Capabilities
Vercel connections report core totals, history, traffic breakdowns, UTM dimensions, event lists, event-property drill-downs, and feature flags.
Vercel cannot apply an event or event-property filter to a global report, and cannot change the metric a breakdown is ordered by. The backoffice hides both controls on a Vercel connection.
Connection-specific credential
Use a connection override only when one connection needs a different credential from the shared Vercel token. The Settings screen shows the exact secret key:
WebAnalytics__ConnectionAccessTokens__{connection-guid}The override stays server-side and wins over the shared provider credential.