Install on Kajabi

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 Header Page Scripts

Open Settings → Site Details → Page Scripts → Header Page Scripts in Kajabi. Paste the tag, preserve existing scripts and save:

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

Kajabi documents this site-header field for third-party tags. Its availability on a particular page depends on the page/template: not every system or account-creation page includes the global header. Kajabi site-script guidance.

Use this shared installation once. If you also have page-template scripts or Google Tag Manager, check that they do not load another copy. The standard Seean tag does not require installing Tag Manager first.

Website and landing-page scope

Check a website page and each kind of landing-page template you use. If a separate template does not include global Header Page Scripts, inspect its supported custom-code setting and add a tag only where the global one is absent. A page’s visible design does not prove that its document shares the same scripts.

Checkout, account-creation and course/player surfaces need separate checks; do not assume site-wide tracking covers all of them. Native apps and emails are outside this browser guide.

Save, publish and verify

Save your script setting and publish any page/template changes, then open the public URL outside the editor.

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.

Kajabi purchases and recurring payments are not imported automatically. Use a verified server-side order API integration for revenue; a landing-page or confirmation-page visit alone does not prove a paid order.

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.