Last updated on July 21, 2017.
Radiant Media Player supports two modes for ad waterfalling:
adTagWaterfallplayer setting: adTags for waterfalling are passed to the player as a configuration option. The player will run through all available adTags until it finds a VAST response including an ad or has no more adTags to waterfall upon.
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 including an ad. 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 an ad is actually being returned. On top of that one must account for potential network errors as the VAST process generally requires several HTTP requests to properly 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.
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: .
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 DFP VAST redirect creative types.
Player code example:
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.
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.
While the default options provided by Radiant Media Player should cover most basic waterfalling needs you may want to build something more advanced to better fit your use case. This can be done through our ads API.
In this case you would not be using the
adTagWaterfall setting but you would rather listen to various API events and use the
loadAds API method to request new ads when needed. Complete documentation for our ads API can be
To help you get started we are providing an example of custom waterfalling implementation that we have often seen requested by our customers. In this example we provide the player with an array of VAST tags to waterfall upon and we set the target of displaying 3 prerolls in a row before the content can begin. For each preroll request the player will run through the waterfall array to maximize the chance of an ad load success.