Tracker configuration
Every supported script attribute and what it controls.
On this page
Attribute reference
| Attribute | Behavior |
|---|---|
| data-project-id | Your site's UUID; required for correct scoping |
| data-host | Collection origin; otherwise derived from the script URL |
| data-mode | cookieless by default; persistent enables a consented stored visitor ID |
| data-consent | banner for Weeveo's UI; external for your CMP |
| data-privacy-url | Public, valid HTTPS notice; required for collection |
| data-recording | true offers optional recording consent; server recorder settings still apply |
| data-identification | true offers optional identity consent; persistent mode is needed |
| data-auto-track | false disables automatic pageviews and declarative click tracking |
| data-domains | Comma-separated hostname allowlist |
| data-track-localhost | true opts into localhost tracking for manual development |
Legacy aliases data-website-id and data-host-url are recognized. New installations should use data-project-id and data-host.
Browser exclusions
The tracker respects Do Not Track, Global Privacy Control, browser automation detection, and localStorage["weeveo.disabled"] (also the legacy umami.disabled). A hostname allowlist can further restrict collection. Localhost is excluded unless explicitly enabled. Server exclusions and collection settings still apply.
URLs and custom domains
Use Settings → Installation to get the active host. When a custom tracking domain becomes active, reinstall the updated snippet. See tracking domains. Keep data-host and the script host aligned with the intended collection origin.
Automatic navigation
Automatic tracking follows pathname changes through History API navigation. The SDK's track() sends a manual pageview. track({ url: "/pricing" }) sends a pageview for that path. Do not combine both approaches for the same visit.
Still looking for an answer? Try troubleshooting or get in touch.