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 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 or 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. 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 CustomEvents automatically
  • if you want GA4 or GTM forwarding, you listen to those browser events on window
In that setup, you do not call trackEvent() 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: