Skip to main content

Tracking conversions with ClickBank

AtomicPlayer does not currently ingest ClickBank purchases into conversion.fired. The implemented event represents a player CTA click, not an approved order, and contains no monetary value.

Verified workflow​

  1. Configure the checkout URL on a player CTA under Customize, then publish the player.
  2. Open Integrations & APIs → Webhooks, add your HTTPS endpoint, and subscribe to conversion.fired from the live catalog.
  3. When the CTA is clicked, use its videoId, sessionId, buttonId, buttonLabel, and trackingId as intent metadata in your own system.
  4. Verify any later payment independently with ClickBank's own supported webhook or API. Do not send order data back to AtomicPlayer or expect AtomicPlayer revenue attribution from this workflow.

AtomicPlayer does not currently document a purchase-ingestion endpoint, reportConversion method, refund synchronization, or unattributed-revenue workflow.

Frequently asked questions​

Does AtomicPlayer record ClickBank 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.