ArrivlArrivl
Vercel integration

Your logs already see every AI agent.
Point them at Arrivl.

Vercel's request logs record every hit, including the AI crawlers that never run JavaScript. Forward them with a Log Drain and Arrivl classifies the agents server-side — no code changes, no impact on your site.

Available today

Configured entirely in the Vercel dashboard. Arrivl generates the endpoint, the signing secret, and the routing header for you — paste three values and you're live.

No codeOutside your request pathSigned deliveriesVercel Pro & Enterprise

Install guide

Install Vercel, start to finish

Forward Vercel's server-side request logs to Arrivl with a Log Drain. There are no code changes; you configure it entirely in the Vercel dashboard, and it runs outside your application's request path, so there is no impact on site performance. Start from Add a site > Vercel in Arrivl — it generates the endpoint URL, the signature secret, and the routing header you paste below. Log Drains require a Vercel Pro or Enterprise plan.

01Install guide

Prerequisites

  • 01An Arrivl project (Add a site > Vercel generates your endpoint, signature secret, and X-Arrivl-Website-Key header)
  • 02A Vercel project that is deployed
  • 03A Vercel Pro or Enterprise plan (Log Drains are not available on Hobby)

02Install guide

Setup

  1. Open Drains settings

    In the Vercel dashboard, go to Team Settings > Drains and click Add Drain. Choose Logs as the data type.

  2. Choose Custom Endpoint

    Pick Custom Endpoint as the destination and choose the JSON (or NDJSON) delivery format.

  3. Set the endpoint URL

    Paste the Arrivl intake URL:

    text

    https://arrivl.ai/api/v1/intake/vercel-log-drain

  4. Set the Signature Verification Secret

    Paste the signature secret from Arrivl (Add a site > Vercel) into Vercel's Signature Verification Secret field. Vercel signs every delivery with it (HMAC-SHA1), and Arrivl rejects any request whose signature does not match.

  5. Add the routing header

    Under Custom Headers, add this line. It tells Arrivl which project the logs belong to:

    text

    X-Arrivl-Website-Key: ak_YOUR_WEBSITE_KEY

  6. Select sources, environment, and create

    Select the request log sources (all except Builds), set Environment to Production and Sampling Rate to 100%, then click Add Drain. Vercel tests the endpoint and starts forwarding immediately.

03Install guide

How it works

  1. 01Vercel streams server-side request logs to the Arrivl endpoint, batched for delivery.
  2. 02Arrivl verifies the x-vercel-signature header (HMAC-SHA1 of the raw body with your secret) and routes by the X-Arrivl-Website-Key header.
  3. 03It reads each request's path, host, User-Agent, referer, and client IP from the log's proxy fields, classifies the bot server-side, and surfaces it in the dashboard, including AI bots that never run JavaScript.
  4. 04Delivery happens outside your application's request path, so your site's response time is unaffected.

04Install guide

Verify

After the drain is created, load a few pages on your Vercel site. The requests appear in Agent Analytics within a minute or two (delivery is near real time, not instant). The project flips to Connected on the first batch Vercel forwards. AI-discovery paths like robots.txt and llms.txt are kept; static assets are skipped.

05Install guide

Troubleshooting

Still stuck? Write to hello@arrivl.ai.

01No events appear after adding the drain

Check that the X-Arrivl-Website-Key header value is your exact key (starts with ak_), that the selected sources include request logs (not only Builds), and that the Environment matches where your traffic runs (usually Production). Load an actual page; static-asset requests are skipped.

02Vercel reports the drain is failing (403)

A 403 means the signature did not match. The Signature Verification Secret in Vercel must be exactly the one Arrivl generated for this project (Add a site > Vercel). Re-copy it, paste it into Vercel, and save.

03Log Drains is missing in my Vercel settings

Drains require a Vercel Pro or Enterprise plan. On Hobby it is unavailable; use the Next.js integration instead, which captures the same traffic from your app with one middleware file.

04Some visitors are missing or share an IP

Vercel has a team setting that hides client IPs in drains (Security & Privacy > IP Address Visibility). With it on, Arrivl cannot record the real client IP, which weakens IP-based crawler verification. Keep IP visibility on for the most accurate results.

Values shown as ak_YOUR_WEBSITE_KEY are placeholders. Sign in and the in-dashboard version of this guide fills in your real key and per-project values for you.

Next step

Forward the logs and see who's reading your deploys

Start freeRead the full install guide

See all the ways to connect →