See whether a deploy hurt conversion

A release goes out, and the next day signups are down. Was it the release? Add one call to the end of your deploy job and Clerion marks the deploy, then sets the 24 hours after it against the 24 hours before: sessions, the share that hit an error, and the share that converted, with the change in red when it went the wrong way. The briefing names the deploy behind a drop.

What you see

Column	What it means
Deploy	Your label and the time it was recorded
Sessions	Visits in the 24 hours before, then the 24 hours after
Error rate	The share of visits that hit a JavaScript error, before and after, with the change in points
Conversion	The share of visits that sent any custom event, before and after, with the change in points

A deploy less than six hours old is marked as still settling and is not judged yet.

How it works

curl -X POST https://api.getclerion.com/api/v1/deploys \
  -H "Authorization: Bearer $CLERION_KEY" \
  -H "Content-Type: application/json" \
  -d '{"websiteId":"site_...","label":"v1.8"}'

The key is the account key from Your model, the same one the MCP server uses. The call works from GitHub Actions, GitLab CI, a deploy script or a terminal. The docs page has each one written out.

Limits

Limit	What it means
Growth and above	The account key exists on Growth, Business and the trial.
24 hours each side	Two deploys on the same day share some of those hours.
Conversion means any custom event	It is the share of visits that sent one, not one goal in particular.

Set it up

Two minutes: copy the key, add the call to the deploy job. The docs page covers GitHub Actions, GitLab CI, Node, recording the real deploy time, and what each error response means.

Questions

Does marking a deploy change my analytics?

No. It adds a row to the Deploys card and a fact for the briefing. Nothing else is counted differently.

Can I mark a deploy by hand?

Yes. The same call from a terminal works; give it a label such as "pricing page copy".

What about preview deploys?

Mark production only. Previews get no real traffic, so their before and after would be empty.