Install on Shopify

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 tag to the storefront theme

Open Online Store → Themes, find the theme you intend to publish, and choose Edit code from its action menu. Back up or duplicate your theme before editing. Open layout/theme.liquid and place the tag before the existing </head>:

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

Save the file. If you edited a draft theme, publish it when ready. Editing a trial paid theme can require purchasing it first. Theme updates may need your custom code reapplied. Shopify theme-code guidance.

What this covers

The tag covers storefront pages that use that layout. A separate theme layout or headless storefront needs its own installation. Shopify admin pages are not part of your storefront.

With the standard snippet in the theme, the tracker also writes its attribution into the cart attributes so paid orders imported through the Shopify revenue connector can be attributed; this is automatic for the cart → checkout flow and not for Buy It Now or other cart-skipping buttons. Theme placement does not install a checkout pixel or import paid orders. Shopify custom pixels run in a sandbox with a different API and page context; do not paste this regular document tracker into the custom-pixel editor and assume equivalent results. Shopify custom pixels.

The native Shopify webhook connector lives under Settings → Integrations → Payment providers; see the Shopify connector guide. Alternatively, a custom server integration can verify order events itself and use the order API.

Publish and verify

Check the published domain, a product page and a collection page. Test checkout separately to establish where the storefront tag stops running. Confirm your custom code follows the store’s customer-privacy settings; installing the tag does not configure consent integration for you.

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.