Install on Webflow

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.

Check custom-code access

You need permission to edit site settings and a site or workspace plan that includes custom code. If the field is unavailable, review Webflow’s current plan requirements. Webflow custom code.

Add site-wide Head code

Open your site’s Settings → Custom code and paste the complete tag into Head code. Keep any existing entries and save changes.

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

Do not include another <html>, <head> or <body> wrapper in this field. Site-wide code is the shared installation; adding the same script under an individual page’s custom code creates a duplicate.

Publish and verify

Publish to the actual domain you want to measure, including the production domain if you also use a Webflow staging domain. Editor or preview behavior alone does not verify publication. Check both a static page and a CMS-generated page if your site uses collections.

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.

Forms, ecommerce outcomes and interactions are not automatically custom events or verified sales. Add intentional custom events to your own interactions, and use a verified server integration for revenue.

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.