Skip to main content

Conversion tracking overview

Implemented meaning​

conversion.fired is an outbound webhook emitted when a viewer clicks a configured player CTA. Its data contains videoId, sessionId, buttonId, buttonLabel, and trackingId. It does not contain amount or currency and does not confirm that a payment occurred.

Verified workflow​

  1. Configure and publish an action button under Videos → video → Customize.
  2. Open Integrations & APIs → Webhooks, add an HTTPS endpoint, and select conversion.fired from the live catalog.
  3. Use Test fire to validate delivery and inspect Recent deliveries.
  4. Treat the event as CTA intent metadata. Verify purchases separately in the checkout provider or your own backend.

The current implementation provides no player.reportConversion API, server-side purchase-ingestion endpoint, revenue payload, refund synchronization, or unattributed-revenue workflow.

Frequently asked questions​

Does AtomicPlayer record a checkout provider purchases as revenue?

No. The current implementation emits CTA-click metadata only; verify and report purchases in your commerce or analytics system.

What does conversion.fired contain?

It contains player context and CTA button metadata. It does not contain amount or currency.