Install on Vercel v0

Copy your token from Seean → Settings → Installation. You need edit access to the v0 project and permission to publish to its connected Vercel project.

Add Seean to the generated app

Open the Code tab in the preview toolbar. Inspect the framework and edit the source layout, rather than a generated build file. Save your changes. v0 code editing.

For a Next.js App Router project, import Script from next/script in app/layout.tsx or src/app/layout.tsx, then add this beside the existing content in <body>:

<Script
  id="seean-tracker"
  src="https://app.seean.io/k.js"
  data-site="YOUR_SITE_TOKEN"
  data-api="https://app.seean.io"
  strategy="afterInteractive"
/>

Replace the token and preserve your providers and metadata. The Next.js guide includes complete App Router and Pages Router examples. For a different framework, choose its installation guide instead of adding a Next.js dependency.

Prompt for v0

Add Seean analytics once to this web app. Inspect the actual framework.
For Next.js use next/script in the shared root layout with
id="seean-tracker", strategy="afterInteractive",
src="https://app.seean.io/k.js", data-site="YOUR_SITE_TOKEN",
and data-api="https://app.seean.io". For another framework, use its
shared document and a classic deferred external script.
Preserve providers, metadata and analytics consent handling.
Avoid a second installation or manual pageviews on route changes.
Show the diff and how to verify the production URL after publishing.

Publish the production version

Use Publish and complete the project’s flow; use Publish Changes for later updates. A working branch preview does not by itself update production. Connected GitHub projects may require their branch checks or reviews before publication. Verify the final deployment status and the production domain you intend to measure. v0 deployments.

Verify and troubleshoot

Open that production URL and follow installation verification. Check direct load, client navigation to another pathname and Back/Forward in Seean Events. Keep Preview traffic on a separate test site/token if you need clean production reports.

If tracking exists only in the preview, confirm the published commit contains the layout change. If a script or request is blocked, check consent, browser privacy settings and CSP. This installation does not connect payment-provider sales or grant an AI agent access to your analytics.

Remove or rotate

Remove the Script component and its unused import, then publish to stop future collection. When rotating a token, update data-site and republish. Existing report data remains. See custom events for measuring application actions.

Something unclear? Contact support.