Script and tracking options
Use the generated snippet in Settings → Tracking. The tracking token identifies a website; it is not an account password or order API secret.
Script attributes
| Attribute | Purpose |
|---|---|
data-site |
Required public website collection token. |
data-api |
API origin used for the collection endpoint. Use the generated value. |
data-local |
Allows local development on localhost or 127.0.0.1. |
defer |
Loads the script without blocking HTML parsing. |
Navigation
The tracker sends an initial pageview, observes history pushState, replaceState and popstate, and handles restored pages. It deduplicates repeated page notifications for the same session and pathname. Query strings and hash fragments are not distinct page paths.
Public methods
window.seean.track(name, properties) sends a custom event. window.seean.attribution() returns visitor and landing/converting path information for a server-side order integration.
Call these methods only after the tracker has loaded. Optional chaining can avoid an exception if collection is blocked, but it also means the event is not sent.
Storage and domains
Visitor identifiers use localStorage; sessions use sessionStorage. Storage is scoped to the website origin, so subdomains and separate domains do not automatically share one visitor identity. There is no cross-domain identity handoff. Use a separate site entry and token when you need separate reports.
Review exclusions and privacy before installing. Use feature availability for unsupported tracking modes.
Something unclear? Contact support.