Use the installation path that matches your storefront stack. All paths use the same configuration shape and send events to Cevoid’s telemetry service.Documentation Index
Fetch the complete documentation index at: https://docs.cevoid.com/llms.txt
Use this file to discover all available pages before exploring further.
Configuration
Callinit() once before sending events. The React component uses the same props.
| Option | Type | Default | Description |
|---|---|---|---|
publishableKey | string | — | Required workspace publishable key. |
enableSessionTracking | boolean | false | Enables Cevoid session tracking after consent checks pass. |
cookieDomain | string | — | Sets the domain on the cevoid_sid session cookie. |
emitBrowserEvents | boolean | true | Emits CustomEvents such as cevoid:post.click on window. |
apiHost | string | https://telemetry.cevoid.com | Overrides the telemetry host for development or controlled environments. |
The SDK ignores repeated
init() calls after the first successful initialization.Script tag
Use the script tag when you want the fastest setup and do not need package imports.data-* attributes:
data-publishable-keydata-enable-session-trackingdata-cookie-domaindata-api-hostdata-emit-browser-events
window.cevoid.initwindow.cevoid.resetwindow.cevoid.identifywindow.cevoid.trackEventwindow.cevoid.trackSale
npm package
Use the package entry point when you want full control over initialization and access toreset().
React
Use the React entry point when your storefront already renders through React.AnalyticstrackEventtrackSaleidentify
Analytics to CevoidAnalytics for clearer component naming.
Initialization checklist
- Use
publishableKeyfor initialization. - Initialize the SDK before your first tracking call.
- Turn on
enableSessionTrackingonly if you want Cevoid-managed session IDs. - Leave
emitBrowserEventsenabled if you want to consume SDK events in GTM or another browser-side layer.