Express
One app.use, above your routes and below your authentication.
“Merchant SDK · staging” already reports from here. Another one gets its own write key and lands in the same table.Open
Take the write key
Everything this install sends is tagged with it, so one key per environment keeps staging out of your production numbers.
Generating…Install
One package, in the service you are instrumenting.
npm i @clearplane/expressAdd it to Express
Paste this where the request path is assembled. The account callback is the only part you have to fill in — it is what turns a request into a customer.
ts
import { clearplane } from "@clearplane/express";
app.use(authenticate);
app.use(clearplane({
writeKey: process.env.CLEARPLANE_KEY,
account: (req) => req.user?.orgId,
}));Name this install
Name it for the deployment rather than the framework. Two Next.js apps in one workspace is the normal case, and “Next.js” twice helps nobody.
Environment
Events land in events_express and are queryable from Chat, models, and SQL.