> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bronto.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Vercel Web Analytics

> Send Vercel Web Analytics page views and custom events to Bronto with the Web Analytics drain, including event data and query parameters.

Web Analytics records page views and custom events (`track()` calls) in your visitors' browsers. Each event carries the path and route, device, browser, OS, country, deployment and, for custom events, the event name and its data.

## Recommended method

[**Marketplace connector**](/integrations/vercel-connector.md): it creates the Web Analytics drain. Web Analytics has to be enabled on the project (Project → Analytics); the drain is available on Pro and Enterprise.

## Alternatives

* [**Drains you configure**](/integrations/vercel-drains.md) with the `analytics` schema (version `v2`).

## Worth knowing

* Events carry `queryParams`, for example `{"utm_source":"newsletter"}`. In Bronto you can group and filter by them on any plan; in Vercel's own dashboard, UTM dimensions need Web Analytics Plus or Enterprise.
* Custom events carry `eventName` and `eventData` (JSON).
* `referrer` and `queryParams` are left out when a visit has none.
* Web Analytics doesn't collect from browsers that report `navigator.webdriver = true`. Synthetic visits from a browser without that flag are counted like any other.

The [Vercel Web Analytics dashboard](/integrations/vercel-templates.md#vercel-web-analytics-web-analytics-drain) is built on this data.

See [Ingesting Vercel Data into Bronto](/integrations/vercel.md) for the full mapping.

## References

* [Web Analytics Drains reference](https://vercel.com/docs/drains/reference/analytics)
* [Vercel Web Analytics](https://vercel.com/docs/analytics)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.