Skip to main content

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.

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.

​
Choose your path

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

Add Cevoid session IDs to events when consent allows it.

Understand consent rules

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

​
Quick answers

​
I embedded a Cevoid gallery or card. Do I need to call trackEvent()?

Usually no. 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 CustomEvents like cevoid:post.click by default, so you usually listen for them instead of duplicating the tracking calls.

​
I am rendering Cevoid interactions in my own storefront code.

Use Manual Event Tracking and send the supported Cevoid event names yourself.

​
I want to track completed purchases.

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

​
I need Cevoid session IDs on events.

Use Session Tracking and Consent. Session tracking is optional and only attaches session_id when consent resolves to granted.