Ads Player Viewability

Viewability Control

The Aniview Ads Player has several features that can be used to control and increase viewability

Some of them are in the Player’s configuration:

  • startOnView: The entire player is loaded only when in view. This means that only when the player’s position is in view, the player will load and start. This flag requires using player templates/studio
    (Note that the Inventory metric will be sent only after the player is in view and loaded)
    Once it loads, the player will continue without validating viewability.

  • reqOnView: If set to TRUE, the player will call all ad sources (i.e. send a request to them) when in view. If the player is not in view, it will wait until it is and then it will resume the process.
    This flag does not require using player templates/studio, but it is subject to other configurations such as midrolltime.

  • playOnView: If set to TRUE, the player will call the ad sources also when not in view and initialize VPAIDs, but will initiate the Ads (startAd) only when in view.
    This flag requires using player templates/studio.
    (Note that due to the nature of some VPAIDs and SDKs, calling startAd does not guarantee an Ad Impression of the specific Ad Source)

  • vitab: If set to TRUE, Viewability validation will take into account if the tab is in view or not. The default is false.

  • playOnViewPerc: Defines the required % of view that defines if the player is in view or not. Default is 50%
    This applies to all features.

Other controls can be set per Ad Source.
When using the settings in the Ad Source, the waterfall will run, yet if the player is not in view, the specific Ad Source will be skipped and not used. The player will continue running and might finish all waterfall cycles (errorLimit) without ever calling those ad sources if the player is not in view.

These settings are in the Ad Source’s page, under the Player Settings tab:

  • Required Viewable Percentage(%): % of view required. Set to 50 for standard use

  • Don't request if not in view:

    • If set, don't call the Ad Source when not in view.

    • If not set, the Ad Source will be called but startAd will be called only when in view.
      In cases where the Ad Source does respond but is waiting for the player to be in view, the player will wait up to 3 sec for view once it is finished handling all other Ad Sources that do not require view. If the player is not in view after that period, it will discard the ad source and continue to the next waterfall cycle.

Viewable Impression

The player reports am Impression is Viewable (Viewable Impression metric) according to the MRC guidelines: When 50% or more of the player in view for at least 2 consecutive seconds.

 

Â