Install on Lovable

First copy your website token from Seean → Settings → Installation. You need permission to edit and publish the Lovable project. This is a tracker installation in your app, not a native Seean connector or MCP connection.

Identify your project’s framework

Ask Lovable which framework the project uses, or inspect its files in the Code tab. Newer Lovable projects use TanStack Start; older projects may use React with Vite. Installing in a guessed index.html is not correct for every project. Lovable’s framework guidance.

Ask Lovable to install Seean

Replace the token in this prompt before sending it:

Install Seean analytics once in this web app using:
src: https://app.seean.io/k.js
data-site: YOUR_SITE_TOKEN
data-api: https://app.seean.io

Inspect the actual framework first. For React/Vite, add a deferred
classic script to the root index.html head. For TanStack Start, add
it to the existing root document head in src/routes/__root.tsx
(or this project's actual root document). Preserve existing head
components and respect the app's analytics consent flow.
Do not import k.js as a module or install it inside every route.
Do not add manual pageview calls on navigation or migrate frameworks.
Show the changed file and explain how to test a direct page load,
navigation to another pathname, and Back/Forward.

Review the resulting change. The public site token belongs in the browser; never include a revenue secret or account credential in this prompt.

Manual installation

For React/Vite, follow the React Router HTML installation.

For TanStack Start, locate the existing document <head> in src/routes/__root.tsx or the root route configured by your project. Insert this beside its existing HeadContent; preserve the rest of the file:

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

The root route owns the shared document in TanStack Start. TanStack root route. Lovable’s Code tab supports browsing files; manual editing requires an eligible paid plan. You can also request the change through chat. Code editor access.

Publish and verify

Save your change, open Publish, and publish the project or choose Publish changes for an existing publication. A preview or accepted draft is not the published version. Lovable publishing.

Open the live URL outside the editor and follow installation verification. Match your path in Events, then test an internal link, Back and Forward. If no data arrives, check that the right framework document was changed, the version was published and consent/privacy settings allow collection. Queries and fragments are not distinct page paths; session and campaign changes follow the script navigation rules.

Update or remove

Ask Lovable to remove this one script, review the diff and publish to stop future collection. Existing reports remain. After changing the framework or rotating the Seean token, repeat the installation checks. See script options and custom events.

Something unclear? Contact support.