Install on Squarespace

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 Code Injection access

Open the Code Injection panel in your site’s settings. Squarespace makes this feature available on eligible plans, including Core, Plus and Advanced and certain legacy plans. It is not included on Basic. Check your site’s current eligibility before editing. Squarespace Code Injection.

Add the Header tag

Paste this into the Header field, preserve existing entries and save:

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

Use the global Header field once. Page-level injection is separate and can duplicate the global installation. Do not add the tag to a content block or repeatedly insert it through page-change handlers.

Page and checkout scope

Global Header injection covers site pages that render it. Squarespace checkout pages do not support Code Injection. Separate order-confirmation or order-status code fields are not a substitute for a verified payment integration. Seean does not automatically receive Squarespace orders.

A Squarespace cookie banner does not automatically gate every injected third-party script. If your policy requires consent first, ensure your site’s consent implementation actually controls this code; verify both acceptance and refusal.

Publish and verify

Open the live site outside the editor after saving. Test a direct nested URL, navigation and any collection pages you use. If collection disappears after a plan change, check whether Code Injection remains active.

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.

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.