Radiant Media Player

Ad waterfalling

Supported waterfalling modes (a.k.a. fallback or mediation)

Radiant Media Player supports two modes for ad waterfalling:

  • Waterfalling based on adTagWaterfall player setting: adTags for waterfalling are passed to the player as a configuration option. The player will sequentially run through all available adTags until it finds a suitable VAST tag or has no more adTag to waterfall upon.
  • VAST-embedded waterfalling: known as VAST redirects (VAST Wrapper) and described in the VAST 3 specification. The player will follow any redirect information it finds in a VAST response until it locates a suitable VAST tag or has no more redirect to follow.

Why do you need waterfalling?

It is all about fill-rate. At a given point in time an ad-server may or may not have inventory to return a VAST response with an available creative included. Your ad-server may have specific agreements to provide VAST redirect information to maximise fill-rate but event with that it is not guaranteed that a VAST response including a creative will actually be returned. On top of that one must account for potential network errors as the VAST process typically requires several HTTP requests to complete.

As such you can use the player adTagWaterfall setting to maximise fill-rate and thus revenue. Using this setting generally implies using different ad-servers to waterfall between one another.

Waterfalling based on player setting

adTagWaterfall: Array

Specifies an array of backup adTagUrls if the first adTagUrl produces an error or if no ads are available at the time of request (auction based ads). The player will cycle through all available adTag (in order) in adTagWaterfall until one is available or will resume content if none are available. Default: [].

When the player tries to load a new VAST tag with the adTagWaterfall setting, a adclientsidewaterfallrequested API event fires

Player code example:

<!-- Include Radiant Media Player JavaScript file in your <body> or <head> -->
<script src=""></script>
<!-- Player container element -->
<div id="rmpPlayer"></div>
<!-- Set up player configuration options -->
  // Streaming source - HLS in this example
  var src = {
    hls: 'https://your-hls-url.m3u8'
  // Player settings
  var settings = {
    licenseKey: 'your-license-key',
    src: src,
    width: 640,
    height: 360,
    ads: true,
    adTagUrl: 'https://your-ad-tag-url',
    // Here comes our waterfall array with fallback adTag urls  
    adTagWaterfall: [
    contentMetadata: {
      poster: [
  var elementID = 'rmpPlayer';
  var rmp = new RadiantMP(elementID);

VAST-embedded waterfalling

The player will automatically follow any VAST redirect information (VAST Wrapper) until it finds a suitable VAST response or has no more redirect to follow.

If you use DoubleClick for Publishers refer to this article for more information on ad waterfall. This is the preferred way to implement ad waterfall for Google Ad Manager VAST redirect creative types.

When no valid VAST response after one or more Wrappers is available the player will fire an aderror event. The getAdVastErrorCode method shall provide the error code 303 specific to this case scenario. See VAST 3 video error codes.

The player will always look for VAST-embedded waterfall before using data in the adTagWaterfall setting when both waterfalling options are available.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 3.0 License.

©2015-2021 Radiant Media Player. All rights reserved.