Skip to main content
Version: 11.7.0

How to subscribe to ad events on Web

When building a custom UI, or when logging events to an analytics service, app developers often need to be able to listen (and react) to ad events. For example, if an ad break starts, they want to draw a countdown on top of their UI. Alternatively, when an ad error occurs, they want to log this to an analytics server.

This article explains how you can programmatically subscribe to ad-related events.

Subscribing to an event​

This subsection explains how you detect ad-related events. The other subsections zoom in on particular use-cases, such as detecting the beginning and end of an ad.

If you are scheduling client-side advertisements, then you use the Ads interface to detect ad events.

The Player API exposes an ads property which belongs to the Ads interface. Because this Ads interface inherits from EventDispatcher<AdsEventMap>, you can leverage event listeners in this interface.

The ad-related events are documented in AdsEventMap.

To subscribe to an event, you select an event from this page, use the Ads interface, call the addEventListener method, and set the event as the first parameter, and the callback as the second parameter.

For example, if you want to track the start of an ad break, you could use the following snippet:

player.ads.addEventListener('adbreakbegin', function (event) {
  console.log(event);
});

The following snippet should log most events to the console.

player.ads.addEventListener(
  [
    'adbegin',
    'adbreakbegin',
    'adbreakchange',
    'adbreakend',
    'adbuffering',
    'addad',
    'addadbreak',
    'adend',
    'aderror',
    'adfirstquartile',
    'adimpression',
    'adloaded',
    'admetadata',
    'admidpoint',
    'adskip',
    'adthirdquartile',
    'removeadbreak',
    'updatead',
    'updateadbreak',
  ],
  console.log
);

Note that when dealing with client-side advertisements, you have different types of integrations, as explained at How to set up VAST and VMAP ads. The impact of this is that some events are not available throughout all integrations.

For example, if you schedule https://cdn.theoplayer.com/demos/preroll.xml, which is a single linear VAST ad, through the "Google IMA integration" on our advertisement tester, the above snippet will trigger the following events:

addad, updateadbreak, updatead, adloaded, adbreakbegin, adbegin, adimpression, adfirstquartile, admidpoint, adthirdquartile, adend, adbreakend, removeadbreak

When you do the same for the csai ad integration, you get the following events:

adloaded,adbreakchange,adbreakbegin,adbegin,adend,adbreakend

Ad begin and end​

Detecting the start and stop of ad breaks and individual ad pods is a common requirement.

This use-case is an application of Subscribing to an event, and relates to the following events:

  • adbegin
  • adbreakbegin
  • adbreakend
  • adend

For example, the following snippet would trigger the callback when an ad break begins:

player.ads.addEventListener('adbreakbegin', function (event) {
  console.log(event);
});

You can swap adbreakbegin for the other events, or supply an array instead:

player.ads.addEventListener(['adbegin', 'adbreakbegin', 'adbreakend', 'adend'], function (event) {
  console.log(event);
});

Ad error​

Ad error events might be triggered when an ad blocker is active, or when an "empty" ad is returned. As an app developer, you might want to detect and possibly react to this.

This use-case is an application of Subscribing to an event, specifically the aderror event.

The following snippet would trigger the callback when an ad error occurs:

player.ads.addEventListener('aderror', function (event) {
  console.log(event);
});

Server-side ads​

If you're scheduling server-side ads, you might need to use a different interface than the Ads interface which you use when scheduling client-side ads.

  • Google DAI: if you're using Google DAI, you can use the same API as the one for client-side ads, as described in the sections above.
  • Yospace: if you're using Yospace, you must use the Yospace interface. You can read more about detecting ad-related events with Yospace at our Yospace documentation.
  • Uplynk: if you're using Uplynk, you can use the same API as the one for client-side ads, as described in the sections above. For now, you can also use the Uplynk Ads API. You can read more about detecting ad-related events with Uplynk at our Uplynk documentation.

If you're building a custom server-side ad insertion solution, you might be interested in using our TextTrack API to detect id3/emsg/EventStream/EXT-X-DATERANGE cues, and the timeupdate event in the Player interface to determine the current playhead position.

Ad block detection​

Refer to the article on ad block detection for more information on detecting (and responding) to ad blockers.

Resources​