Install on Replit

This guide covers Replit web apps that serve pages in a browser. The Seean tracker does not instrument a backend API by itself or a native mobile application. Copy your token from Seean → Settings → Installation.

Choose the file your app serves

Open the Project Editor and inspect the app’s files, or ask Replit Agent which framework serves the HTML document. Replit can host different application types, so there is no single filename for every project. Replit Project Editor.

For a plain HTML or Vite app, add this before </head> in the entry HTML file actually used by its build:

<script defer src="https://app.seean.io/k.js"
  data-site="YOUR_SITE_TOKEN"
  data-api="https://app.seean.io"></script>

Replace the token. For Next.js, Astro or React Router Framework Mode, use the linked root-layout instructions. For a server-rendered template app, use the base template included by all pages you intend to measure.

Prompt for Replit Agent

Install Seean in the browser pages of this project. Inspect the
framework and the HTML/template used by the published build first.
Add exactly one classic external script loading
https://app.seean.io/k.js, with data-site="YOUR_SITE_TOKEN" and
data-api="https://app.seean.io". Use defer in HTML, or the framework's
documented script loader. Respect existing analytics consent.
Do not put the script in backend handlers or add route-change
pageview calls. Show the file changed and verify another pathname
as well as the initial page after publishing.

Publish and verify

Review the change in Preview, then use your app’s publishing flow. Keep the deployment type appropriate to your existing app: a server application needs its server, even if the tracker itself is a static script. Wait for the deployment to succeed and open its public URL. Replit publishing.

Development URLs and published URLs are different environments. Follow installation verification against the published version: script load, collection POST, matching Events path, internal navigation and Back/Forward. Test a direct nested URL too.

Troubleshooting and removal

If only Preview works, check that the changed source is in the published build and that its root HTML contains the tag. A native/backend-only app needs a different measurement approach. Consent, privacy preferences, an incorrect token or a blocked POST can explain missing browser data; support checks cover them.

Remove the one script and republish to stop collection. For local tests using localhost, add data-local and use a separate site token. See script options for supported navigation and storage behavior.

Something unclear? Contact support.