Install on Wix

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 the published site

Wix custom-code setup requires a published site with a connected domain and appropriate editing access. Wix security and consent rules can restrict third-party code, so confirm this installation on your actual site before relying on it. Wix Custom Code.

Add Custom Code

In your site’s dashboard, open Settings → Development & integrations → Custom Code → Add Custom Code. Name the entry Seean and paste the complete tag:

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

Choose All pages, load the code once per visit, select Head, and apply. Keep the script classified and controlled according to your site’s analytics-consent policy. Do not install a second copy through a page embed or custom element.

Wix has dedicated marketing integrations for some tracking products. Their setup instructions do not establish Seean compatibility: this guide uses custom code and requires the checks below. If Wix blocks or rewrites the script so its attributes or execution context are lost, contact support with the published URL and browser error.

Publish and verify

Test your connected public domain after applying the change. Visit a direct nested page and navigate between different paths. An editor preview is insufficient. Recheck after a domain change: Wix associates custom snippets with a domain and may remove them when that domain is replaced.

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.

Wix stores, bookings and payment events are not native Seean revenue integrations. A working storefront pageview only confirms that browser collection works on that page.

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.