Install on Framer

Create or select your website in Seean, then copy its snippet from Settings → Installation. Replace YOUR_SITE_TOKEN below with that website’s public token. Keep the external script and both data attributes; never put a server order API secret in this code.

Add a script in project settings

Open Project Settings → Custom Code, then choose Add Script or the + control. Name it Seean, choose the start of <head> as placement, apply it to all pages, and set it to run once. Paste the full tag:

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

Framer distinguishes running once from running on every page visit. Use once: Seean observes supported history navigation itself, and repeatedly reinstalling it can double count. Save the entry. If custom code is unavailable, check your project’s plan and editing permissions. Framer custom-code instructions.

Publish and verify

Publish the project, then visit its public domain. Test the homepage, a direct nested URL and a Framer link between different paths. If only certain pages collect, inspect the script’s page scope and whether those pages are part of the same project.

Open the published site in a browser and follow installation verification: confirm k.js loads, a collection request is sent, and the correct website and paths appear in Events. Check a direct page load, a link to a different pathname, and Back/Forward. Setup health shows the last received pageview time and offers a published-homepage check; it does not certify every page.

If events are missing, check the published HTML, consent settings, content blockers, CSP and exclusions. Install the tracker only once: a second tag, plugin or tag-manager installation can double count. Supported pathname navigation is automatic; do not add another pageview tag for every history change. Hash-only changes are not distinct pages.

Keep only one installation across project scripts, page-specific code and embedded components. A script inside an embed may see the embed document instead of the top-level page; use the project setting for site analytics.

Events and sales

An interaction is not automatically a custom event. Use custom events where you control the handler. An external checkout does not become a native revenue integration when the Framer script is installed; follow the server order API for verified sales.

Changes and removal

To change the site token, update this installation and publish again. To stop future collection, remove the same tag and publish; existing reports remain. Recheck installation after platform, theme or routing changes.

See script options, custom events and technical privacy. Loading this script must follow your site’s analytics-consent policy; a platform cookie banner does not necessarily control custom code automatically.

Something unclear? Contact support.