Install on WooCommerce

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.

Install once through WordPress

WooCommerce runs on WordPress. Follow the WordPress guide to add this tag to your existing site-wide header integration. If Seean is already installed there, keep that installation; do not add a second WooCommerce-specific copy.

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

Save the header configuration and clear relevant caches. This is standard browser tracking, not a Seean WooCommerce plugin.

Storefront and checkout scope

Product pages, categories, cart and checkout can be measured only where the site’s rendered document actually includes the tag and permits collection. Check each surface separately: a checkout extension, custom template or headless storefront may use a different document. For a headless frontend, install in that frontend’s framework instead of assuming WordPress header code reaches it.

An off-site payment page is outside the storefront installation. Returning to an order-confirmation page can record a pageview; it does not prove payment, value or refund status. Do not send order revenue from a browser confirmation page alone.

Orders and refunds

Seean has no native WooCommerce order connector. A developer can connect verified server-side order events to the order API. WooCommerce provides webhooks, but configuring one does not automatically transform its payload into Seean’s API contract. Your server must verify the event, map stable order IDs and supported fields, handle retries and forward full or partial refunds with the provider’s refund ID. Orders must be sent in the website’s reporting currency in minor units; other currencies are rejected, not converted.

Publish and verify

Check product → cart → checkout navigation, direct loads and the return from your payment provider. Do not use a real purchase merely to test browser pageviews.

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.