Choose one path
Use the installation path that matches how your storefront is built:- Script tag: fastest setup when you want browser-only initialization and no package imports
- npm package: best default when you control storefront application code directly
- React: use when your storefront already renders through React
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
- open the page after the script loads
- confirm
window.cevoidexists - send one test call such as
window.cevoid.trackSale(...)or listen for a gallery browser event
npm package
Use the package entry point when you want full control over initialization from your storefront code.- confirm your app starts without SDK import errors
- trigger one supported tracking call
- if
emitBrowserEventsis left on, confirm the matching browser event appears onwindow
React
Use the React entry point when your storefront already renders through React.- mount the
Analyticscomponent once near your app root - trigger one supported tracking call from React code
- confirm the event path works before layering in session tracking or consent handling
Configuration
Callinit() once before sending events. The React component uses the same props.
Repeated
init() calls after the first successful initialization are ignored.