Install on Bubble

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 the application header script

Open the Bubble editor’s Settings → SEO / metatags → Advanced settings. Paste the tag into Script/meta tags in header. If that control is unavailable, check the app’s plan and your editing permissions. Bubble application settings.

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

Keep the full script tag and its attributes. Use the application header once; an HTML element inside a page or reusable element is not a replacement for the shared document header and may create duplicates.

Deploy the live version

Save the change and deploy your app’s live version through your normal Bubble workflow. A development or version-test URL is a separate verification target, not proof of the published app. Choose a separate Seean website for test traffic if you need to keep production reports clean.

This guide covers Bubble browser apps. It does not establish tracking in a native mobile app or every plugin’s embedded webview.

Pages and workflows

Open a direct page URL and use the app’s actual navigation workflows. Changes to a pathname can produce pageviews through supported history navigation. Showing a group, updating application state or changing only a URL hash is not necessarily a new pageview. Use custom events for meaningful actions you explicitly instrument.

Verify the published app

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.

Check custom domains and login-dependent pages individually. If the header setting appears saved but the live document has no tag, check deployment state and whether another plugin rewrites the document before adding more code.

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.