Skip to main content

Ad tracking

Verified browser events​

The runtime dispatches bubbling DOM CustomEvent signals named atomicplayer:play, atomicplayer:pause, atomicplayer:complete, atomicplayer:cta, and atomicplayer:convert. Listen with standard DOM APIs:

document.addEventListener("atomicplayer:complete", (event) => {
  console.log(event.detail.videoId);
});

document.addEventListener("atomicplayer:cta", (event) => {
  console.log(event.detail.buttonId);
});

The current runtime does not expose player.on(...) or player.reportConversion(...). The CTA event carries button metadata, not purchase value or currency. Map verified engagement signals to pixels only after applying each ad platform's current consent and event requirements.

Server-side, use only events displayed by Integrations & APIs → Webhooks. Do not claim automatic click-ID/UTM preservation, purchase payloads, or browser/server deduplication IDs from AtomicPlayer.

Frequently asked questions​

Which browser API should I use?

Use standard document.addEventListener with the verified atomicplayer:* CustomEvent names.

Does conversion.fired contain purchase value?

No. It represents a CTA click and contains button metadata only.