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 sequentially run through all available adTags until it finds a suitable VAST tag or has no more adTag 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 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.
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:
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 DFP 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.