GPT/DFP Ad-Tag Embed

Pulse can run as a video creative inside a Google Ad Manager (GPT/DFP) slot. It detects that it’s running inside a GAM iframe, climbs up to the publisher’s own page, and mounts itself there — Pulse is the on-page player, not a banner, so it doesn’t stay trapped inside the ad slot’s iframe.

Paste this into the creative’s HTML field:

<script>
  window.seeen = {
    playlistId: "1d5531f5-a5f6-4104-828a-3daea73a6966",
    options: { stayVisible: true, position: "bottom-right" },
  };
</script>
<script src="https://imasdk.googleapis.com/js/sdkloader/ima3.js"></script>
<script src="https://code.seeen.com/pulse/latest/seeen-pulse-loader.js"></script>

How it works

1. The loader script detects it’s inside a Google Ad Manager iframe (by window.inDapIF/window.inGptIF, or by walking up the DOM looking for a div-gpt-ad-* ancestor).
2. It creates a <seeen-pulse> element on the publisher’s root page — sized to the ad slot, configured from window.seeen — and appends it next to the ad slot.
3. It ensures the IMA SDK and the Pulse CDN bundle are loaded on the root page (skipping either if already present, so multiple ad units on one page only load them once).
4. Once the CDN bundle registers <seeen-pulse>, the browser automatically upgrades the element the loader already inserted, and it mounts.

Config

Same fields as the CDN config reference, read from window.seeen inside the creative iframe.