Analytics SDK

Use this page first when you are deciding how to implement Cevoid analytics on a storefront. If you already know the exact SDK method or event payload you need, skip to Installation, SDK API, or Event types.

• Using Cevoid galleries or cards

  Gallery and card widgets already initialize Cevoid UGC tracking and emit browser events automatically.

• Forward events to GA or GTM

  Listen to Cevoid browser events on window and forward them into your existing analytics setup.

• Track Cevoid events manually

  Use trackEvent() when you render Cevoid interactions yourself and need to send widget-style events manually.

• Track sales

  Shopify uses the checkout web pixel path. Non-Shopify storefronts use the manual sales-tracking path.

• Enable session tracking

  Keep the Cevoid session ID across page loads when consent allows it.

• Understand consent rules

  See when ca_session is created, when it is not, and how denied consent affects events.

Usually you do not need trackEvent() for them. Cevoid galleries and cards initialize the UGC SDK internally and send the core widget, post, product, and gallery events automatically.

Use Forward browser events to GA. The SDK emits browser CustomEvent⁠s like cevoid:post.click by default, so you usually listen for them instead of duplicating the tracking calls.

Use Manual event tracking and send the supported Cevoid event names yourself.

Use Track sales. Shopify storefronts use the checkout web pixel path only; non-Shopify storefronts use the manual trackSale() path.

Use Session tracking and Consent. Every event carries a session ID for the current page runtime. Session tracking is optional and only keeps that session_id across page loads, in the ca_session cookie, when consent resolves to granted.