# Analytics SDK

> Choose the right Cevoid analytics integration path for your storefront.

Breadcrumb: Analytics SDK › Overview · Updated: 2026-10-18
Docs index: https://docs.cevoid.com/developers/llms.txt

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](https://docs.cevoid.com/developers/analytics-sdk/installation.md), [SDK API](https://docs.cevoid.com/developers/analytics-sdk/api.md), or [Event types](https://docs.cevoid.com/developers/analytics-sdk/events.md).

## Choose your path

- [Using Cevoid galleries or cards](https://docs.cevoid.com/developers/analytics-sdk/using-cevoid-galleries.md): Gallery and card widgets already initialize Cevoid UGC tracking and emit browser events automatically.
- [Forward events to GA or GTM](https://docs.cevoid.com/developers/analytics-sdk/forward-events-to-ga.md): Listen to Cevoid browser events on `window` and forward them into your existing analytics setup.
- [Track Cevoid events manually](https://docs.cevoid.com/developers/analytics-sdk/track-events.md): Use `trackEvent()` when you render Cevoid interactions yourself and need to send widget-style events manually.
- [Track sales](https://docs.cevoid.com/developers/analytics-sdk/track-sales.md): Shopify uses the checkout web pixel path. Non-Shopify storefronts use the manual sales-tracking path.
- [Enable session tracking](https://docs.cevoid.com/developers/analytics-sdk/setup-session-tracking.md): Keep the Cevoid session ID across page loads when consent allows it.
- [Understand consent rules](https://docs.cevoid.com/developers/analytics-sdk/consent.md): 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 you do not need [`trackEvent()`](https://docs.cevoid.com/developers/analytics-sdk/api.md#trackeventname-data) for them. Cevoid galleries and cards initialize the UGC SDK internally and send the core widget, post, product, and gallery events automatically.

### I want those gallery events in GA4 or GTM.

Use [Forward browser events to GA](https://docs.cevoid.com/developers/analytics-sdk/forward-events-to-ga.md). The SDK emits browser [CustomEvent](https://developer.mozilla.org/en-US/docs/Web/API/CustomEvent)s 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](https://docs.cevoid.com/developers/analytics-sdk/track-events.md) and send the supported Cevoid event names yourself.

### I want to track completed purchases.

Use [Track sales](https://docs.cevoid.com/developers/analytics-sdk/track-sales.md). 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](https://docs.cevoid.com/developers/analytics-sdk/setup-session-tracking.md) and [Consent](https://docs.cevoid.com/developers/analytics-sdk/consent.md). 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.

**Recent changes**

No Analytics SDK changes yet.

[Open the changelog](https://docs.cevoid.com/developers/changelog.md)

---

Canonical: https://docs.cevoid.com/developers/analytics-sdk