Web Tracking Keys
Create Web Tracking Key
Create a publishable key and get the install snippet for your site
POST
Create Web Tracking Key
Create a publishable key for the browser tracking SDK or the mobile SDKs and get the
<script> tag to install.
This is what turns on product views, cart activity, and browse abandonment for a site that is not Shopify or WooCommerce. Events start flowing once the snippet is deployed, and nothing is backfilled for the period before that - create and install it before building the sequence that depends on it.
Requires an API key with the integrations:manage scope.
Request
Origins allowed to use this key. A bare domain is read as
https. A leading
*. matches subdomains at any depth but not the apex. Maximum 50 entries.
Omitting this and allowedAppIds leaves the key unrestricted, so any site or
app can send events with it - a deliberate choice for a server-side caller
only.iOS bundle IDs and Android package names allowed to use this key from the
mobile SDKs, e.g.
com.example.app. Maximum 20
entries; duplicates are dropped case-insensitively. A key with app IDs and no
origins works only from your apps, never from a website.Behavior
Origins are normalized before storage: case is lowered, paths and trailing slashes are stripped, and default ports are dropped so the stored value matches what a browser sends inOrigin.
If any entry cannot be parsed as an origin, the whole request is rejected rather than saving the valid subset - a partial save would leave you believing a domain is covered when it was silently dropped.
After installing the snippet, mint an identity token from your authenticated backend and call sequenzy.identify(email, identityToken) when a visitor signs in or reaches checkout. Until then, their events are buffered in their browser. See Website Tracking.