> ## 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 Marketplace Connector
> Install the Bronto connector from the Vercel Marketplace to create log, trace, Speed Insights and Web Analytics drains for every project in a Vercel team, with no endpoints or keys to copy.
## When to use the connector
The connector is the **recommended** way to send Vercel's platform data to Bronto. Connect your account once, and Bronto creates the ingestion API key and a [drain](/integrations/vercel-drains.md) for each data type in every project of your Vercel team.
Use [drains you configure yourself](/integrations/vercel-drains.md#create-a-drain-yourself) instead when you want drains for only some projects, a different dataset layout, or drains managed in your own infrastructure code.
| Drain | What it contains | Schema reference |
| - | - | - |
| Logs | Runtime, build, edge, static, firewall, redirect and external-rewrite logs | [Log Drains reference](https://vercel.com/docs/drains/reference/logs) |
| Traces | Vercel's spans for each request, and spans from your functions | [Traces reference](https://vercel.com/docs/drains/reference/traces) |
| Speed Insights | Core Web Vitals from real users | [Speed Insights reference](https://vercel.com/docs/drains/reference/speed-insights) |
| Web Analytics | Page views and custom events | [Analytics reference](https://vercel.com/docs/drains/reference/analytics) |
## Prerequisites
* A **Vercel Pro or Enterprise** plan. See [Vercel's drain documentation](https://vercel.com/docs/drains/using-drains) for plan details.
* A Bronto account. You can also create one during the connect flow. The connector creates its own ingestion API key, so you don't need to make one first.
***
## Connect your account
The whole flow in 43 seconds, from the Marketplace listing to the drains in Vercel and the first logs in Bronto
**1. Open the Bronto listing on the Vercel Marketplace**
Go to [vercel.com/marketplace/bronto](https://vercel.com/marketplace/bronto) and select **Connect Account**.
You can also reach the listing from inside Vercel at **Team Settings → Drains → Add Drain → External Integrations**, or from Bronto at **Ingestion → Cloud platforms → Vercel**.
**2. Choose the Vercel team and approve access**
Select the Vercel team whose projects you want to stream into Bronto, then approve the access Bronto requests. Bronto uses it to list your projects and create drains on your behalf.
**3. Sign in to Bronto**
Vercel redirects you to the Bronto sign-in page. Sign in to the organisation you want the data to land in, or create an account if you don't have one yet. Bronto links the two accounts.
**4. Return to Vercel**
When you see **Vercel Account Linked Successfully!**, select **Back to Vercel**. Drain creation continues in the background.
> [!NOTE]
>
> The Bronto organisation you sign in to is the one the drains are created against, and its region decides which ingestion endpoint they use. If you manage more than one Bronto organisation, make sure you're signed in to the right one before you connect.
***
## What the connector creates
Once the accounts are linked, Bronto:
* Creates a Bronto API key named **Vercel Drain Ingestion API Key** with the **Ingestion** role. Every drain it creates authenticates with this key, and you can see it under [API Keys](/Account-Management/API-Keys.md).
* Lists every project in the connected Vercel team.
* Creates four drains per project (Logs, Traces, Speed Insights, and Web Analytics), already pointed at the ingestion endpoint for your Bronto account's region, with the correct encoding and headers.
Each drain is named `Bronto Drain - -`, so they're easy to find and edit under **Team Settings → Drains** in Vercel:
| Vercel drain name | Data | Encoding | Where it lands in Bronto |
| - | - | - | - |
| `Bronto Drain - -log` | Logs | NDJSON | Dataset `log`, collection `` |
| `Bronto Drain - -speed_insights` | Speed Insights | NDJSON | Dataset `speed_insights`, collection `` |
| `Bronto Drain - -analytics` | Web Analytics | NDJSON | Dataset `analytics`, collection `` |
| `Bronto Drain - -trace` | Traces | Protobuf (OTLP/HTTP) | [Explore Traces](/tracing/explore-traces.md), no dataset or collection |
For the log and event drains, the **dataset** tells you which signal the data is and the **collection** tells you which Vercel project it came from. To look at one project in isolation, filter on its collection; to compare projects, query the `log` dataset and group by collection. Traces don't use datasets or collections: find them in Explore Traces and filter by `vercel.projectId`.
> [!NOTE]
>
> Drains are created in the background and retried to stay within Vercel's API rate limits, so on a team with many projects it can take a few minutes for all of them to appear under **Team Settings → Drains**.
## After connecting
Everything the connector creates is an ordinary Vercel drain that you own from that point on:
* **Sources and environments**: each drain forwards all the data it covers. Edit a drain in Vercel to narrow its log sources or environments. See [Vercel Drains](/integrations/vercel-drains.md) for what each drain contains.
* **Projects added later**: the connector provisions drains for the projects that exist when you connect. For a project created afterwards, [contact support](mailto:support@bronto.io) to re-run provisioning.
* **Audit logs**: audit log drains apply to the whole team rather than to individual projects, so the connector doesn't create one.
***
## Verify Data Flow
Once the drains appear under **Team Settings → Drains**, data from your projects begins flowing into Bronto. For Logs, Speed Insights, and Web Analytics, open the `log`, `speed_insights`, or `analytics` dataset in Log Search and filter on the project's collection. For Traces, open [Explore Traces](/tracing/explore-traces.md) and filter by `vercel.projectId` or `vercel.deploymentId`.
## Correlate telemetry across drains
With every drain flowing into Bronto, you can look at frontend and backend data side by side instead of switching between tools. The payloads share a few identifiers that make that work:
| Field | Present on | Use it to |
| - | - | - |
| `projectId` / `vercel.projectId` | Logs, Traces, Speed Insights, Web Analytics | Scope every signal to one Vercel project |
| `deploymentId` / `vercel.deploymentId` | Logs, Traces, Speed Insights, Web Analytics | Compare a deployment before and after a release |
| `traceId` / `spanId` | Logs, Traces | Jump from a log line to its distributed trace and back |
| `route` | Speed Insights, Web Analytics | Line up a slow Web Vital with the pages and traffic behind it |
For example, when a **Speed Insights** regression shows up on a route, filter **Logs** and **Traces** by the same `deploymentId` to find the release that introduced it, then use the `traceId` on an error log to open the exact span behind it.
## Next steps
* [Dashboards, monitors and saved searches](/integrations/vercel-templates.md) built on this data
* [Tracing into other services](/integrations/vercel-tracing.md) outside Vercel
* [Deployment webhooks](/integrations/vercel-webhooks.md) for deploy markers
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.