---
title: Vercel Web Analytics
description: Reference for Vercel Web Analytics connection fields, reports, team projects, credential overrides, and common connection errors.
seo:
  image: /og/providers/vercel.png
---

The [quickstart](/quickstart) owns the first-time setup flow. Use this page to look up Vercel-specific requirements, connection fields, and capabilities.

## About Vercel Web Analytics

[Vercel Web Analytics](https://vercel.com/docs/analytics) is Vercel's analytics product for understanding traffic to a Vercel project. This package reads the reports Vercel already collects and makes them available in Umbraco; it does not add tracking to the public site.

## Requirements

The connection needs a [Vercel access token](https://vercel.com/kb/guide/how-do-i-use-a-vercel-api-access-token) scoped to the account or team that owns the project. Configure the token server-side; it 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](/reference/troubleshooting#vercel).

## Capabilities

Vercel connections provide core totals, history, traffic breakdowns, UTM dimensions, event lists, event-property drill-downs, and feature flags.

Vercel does not support applying an event or event-property filter to a global report, and does not support selecting the ordering metric for a breakdown. The backoffice adapts to those capabilities.

## Connection-specific credential

Use a connection override only when this connection needs a different credential from the shared Vercel token. The Settings UI shows the exact secret key, in the form:

```text
WebAnalytics__ConnectionAccessTokens__{connection-guid}
```

The override remains server-side and takes precedence over the shared provider credential.