Connect Vercel to ShipVitals
Usage cost, production deploys, domains and Web Analytics per project
Beta: this connector is new in the beta, and we're still checking it against more accounts.
What it reads
- Access token scoped to the team
- Lists projects, production deploys and domains, and reads billing and analytics
Not read-only at Vercel. Vercel's tokens can't be limited to reading: one scoped to a team can also deploy and change its settings. ShipVitals only reads projects, deploys, domains, billing charges and Web Analytics.
What ShipVitals keeps: The access token, encrypted, and the Team ID if you enter one.
How to connect
- In Vercel, open Account Settings → Tokens.
- Create a token named ShipVitals, scoped to the team that owns your projects, with an expiration you're happy to renew.
- Copy the token. Vercel shows it once.
About 2 minutes.
How to revoke
Removing the connection in ShipVitals deletes the stored key at once.
What it powers
Dashboard tabs: Costs, Usage, Health, Obligations.
Figures it fills
- Page views
- Visitors
Sync
- Free: Daily
- Indie: Hourly
- Studio: Every 15 minutes
- Agency: Every 15 minutes
Vercel reports a day in full after 1 day; ShipVitals waits for it.
Troubleshooting
Each error a connection can hit, and its fix. The connection's health page names the one it hit.
- Access refused
- Vercel didn't accept the token: it may have expired or been deleted. Create a new one in Account Settings → Tokens and paste it.
- A permission is missing
- Vercel refused part of the team's data. Billing needs the token's owner to be an Owner, Member, Developer, Security or Billing member of the team.
- Access removed
- ShipVitals' access was removed in Vercel. Connect it again; the history it brought in is kept.
- Rate-limited
- Vercel asked ShipVitals to slow down. Nothing to do: the sync carries on by itself and catches up.
- Quota reached
- The account used up a Vercel quota. The sync resumes when the quota resets.
- Not found
- Something the connection reads is gone from Vercel: renamed, moved or removed. Review the connection's resources, or connect again.
- Vercel is unavailable
- Vercel is having trouble on its side. Check its status page; ShipVitals retries by itself.
- Couldn't reach Vercel
- The request didn't get through. ShipVitals retries by itself; if it keeps failing, check that Vercel is reachable.
- An answer ShipVitals didn't expect
- Vercel answered in a shape ShipVitals didn't expect, usually after a change on its side. We're told, and the data you have is kept.
- A setting doesn't work
- Vercel needs to know which team to read: create a token scoped to that team (not to one project), or enter the team's ID.