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

# Using Cevoid Galleries

> Understand what Cevoid galleries and cards track automatically and when you still need custom analytics work.

Use this page when you embed Cevoid galleries or cards on a storefront and want to understand what happens automatically. If you are not using Cevoid widget surfaces, skip this page and go to [Manual Event Tracking](./track-events) or [Track Sales](./track-sales).

## What happens automatically

Cevoid galleries and cards already initialize the UGC tracking surface internally when a workspace publishable key is available.

That means the widget can automatically send the core Cevoid on-site events, including:

* `widget.load`
* `widget.view`
* `post.view`
* `post.click`
* `post.view.popup`
* `post.clap`
* `product.click.tag`
* `product.click.post`
* `product.click.card`
* `gallery.load_more`
* `gallery.upload_cta_click`

The widgets also emit the matching browser events by default, such as:

* `cevoid:post.click`
* `cevoid:product.click.tag`
* `cevoid:gallery.load_more`

The browser event payload is available on [`event.detail`](https://developer.mozilla.org/en-US/docs/Web/API/CustomEvent/detail).

## Default gallery path

If you use a standard Cevoid gallery or card, the normal setup is:

* Cevoid sends the gallery and card events automatically
* Cevoid emits the matching browser [CustomEvent](https://developer.mozilla.org/en-US/docs/Web/API/CustomEvent)s automatically
* if you want GA4 or GTM forwarding, you listen to those browser events on `window`

In that setup, you do **not** call [`trackEvent()`](../analytics-sdk/api#trackeventname-data) yourself just because you embedded a gallery or card.

## When you need a different path

Leave the default gallery path when one of these is true:

* you render Cevoid interactions in custom storefront code outside the standard widgets
* you want completed purchase tracking on a non-Shopify storefront
* you need Cevoid session IDs on events and want to verify consent behavior

In those cases:

* use [Manual Event Tracking](./track-events) for custom Cevoid interaction tracking
* use [Track Sales](./track-sales) for non-Shopify completed purchases
* use [Session Tracking](./setup-session-tracking) and [Consent](./consent) for session behavior

## Recommended next step

* Want GA or GTM forwarding: [Forward Browser Events to GA](./forward-events-to-ga)
* Want exact session behavior: [Session Tracking](./setup-session-tracking)
* Want cookie and consent rules: [Consent](./consent)
* Want payload details: [Event Types](../analytics-sdk/events/index)

## Related

* [Forward Browser Events to GA](./forward-events-to-ga)
* [Session Tracking](./setup-session-tracking)
* [Consent](./consent)
* [Event Types](../analytics-sdk/events/index)