# Using Cevoid galleries

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

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

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](https://docs.cevoid.com/developers/analytics-sdk/track-events.md) or [Track sales](https://docs.cevoid.com/developers/analytics-sdk/track-sales.md).

## 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()`](https://docs.cevoid.com/developers/analytics-sdk/api.md#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 the Cevoid session ID to last across page loads and want to verify consent behavior

In those cases:

- use [Manual event tracking](https://docs.cevoid.com/developers/analytics-sdk/track-events.md) for custom Cevoid interaction tracking
- use [Track sales](https://docs.cevoid.com/developers/analytics-sdk/track-sales.md) for non-Shopify completed purchases
- 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) for session behavior

## Recommended next step

If you want these events in GA4 or GTM, continue with [Forward browser events to GA](https://docs.cevoid.com/developers/analytics-sdk/forward-events-to-ga.md).

## Related articles

- [Forward browser events to Google Analytics](https://docs.cevoid.com/developers/analytics-sdk/forward-events-to-ga.md)
- [Session tracking](https://docs.cevoid.com/developers/analytics-sdk/setup-session-tracking.md)
- [Consent](https://docs.cevoid.com/developers/analytics-sdk/consent.md)
- [Event types](https://docs.cevoid.com/developers/analytics-sdk/events.md)

---

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