> ## 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.

# Overview

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

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](../analytics-sdk/installation), [SDK API](../analytics-sdk/api), or [Event Types](../analytics-sdk/events/index).

## Choose your path

<CardGroup cols={2}>
  <Card title="Using Cevoid galleries or cards" icon="layout-grid" href="/developer-docs/analytics/using-cevoid-galleries">
    Gallery and card widgets already initialize Cevoid UGC tracking and emit browser events automatically.
  </Card>

  <Card title="Forward events to GA or GTM" icon="arrow-up-right" href="/developer-docs/analytics/forward-events-to-ga">
    Listen to Cevoid browser events on `window` and forward them into your existing analytics setup.
  </Card>

  <Card title="Track Cevoid events manually" icon="mouse-pointer-click" href="/developer-docs/analytics/track-events">
    Use [`trackEvent()`](../analytics-sdk/api#trackeventname-data) when you render Cevoid interactions yourself and need to send widget-style events manually.
  </Card>

  <Card title="Track sales" icon="badge-dollar-sign" href="/developer-docs/analytics/track-sales">
    Shopify uses the checkout web pixel path. Non-Shopify storefronts use the manual sales-tracking path.
  </Card>

  <Card title="Enable session tracking" icon="cookie" href="/developer-docs/analytics/setup-session-tracking">
    Add Cevoid session IDs to events when consent allows it.
  </Card>

  <Card title="Understand consent rules" icon="shield-check" href="/developer-docs/analytics/consent">
    See when `ca_session` is created, when it is not, and how denied consent affects events.
  </Card>
</CardGroup>

## Quick answers

### I embedded a Cevoid gallery or card. Do I need to call [`trackEvent()`](../analytics-sdk/api#trackeventname-data)?

Usually no. 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](./forward-events-to-ga). 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](./track-events) and send the supported Cevoid event names yourself.

### I want to track completed purchases.

Use [Track Sales](./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](./setup-session-tracking) and [Consent](./consent). Session tracking is optional and only attaches `session_id` when consent resolves to granted.

## Related

* [Using Cevoid Galleries](./using-cevoid-galleries)
* [Forward Browser Events to GA](./forward-events-to-ga)
* [Manual Event Tracking](./track-events)
* [Track Sales](./track-sales)
* [Session Tracking](./setup-session-tracking)
* [Consent](./consent)