Next.js

One provider in the root layout, plus server actions attributed automatically.

“Hosted checkout” 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/next

Add it to Next.js

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.

tsx

import { Clearplane } from "@clearplane/next";

export default function RootLayout({ children }) {
  return (
    <html>
      <body>
        <Clearplane account={await currentOrg()}>{children}</Clearplane>
      </body>
    </html>
  );
}

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.

Name

Environment

Events land in events_nextjs and are queryable from Chat, models, and SQL.