Viewability Control

The ads player has a few Aniview Ads Player has several features that can be used in order to control and increase viewability

Some controls of them are in the player Player’s configuration:

• startOnView: The entire player is loaded only when in view. This means that only when the player player’s position is in view, the player will load and start.
  This flag requires using player templates/studio
  (Note that inventory the Inventory metric will be sent only after the player is in view and loaded)
  After Once it loads, the player loads it continues 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 waits till its in view and will resume, it will wait until it is and then it will resume the process.
  This flag do does not requires using player templates/studio
  (Subject , but it is subject to other configurations such as midrolltime).

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

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

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

There are some Other controls that can be set per ad sourceAd Source.
When those settings are used, when the waterfall runs, using the settings in the Ad Source, the waterfall will run, yet if the player is not in view, the ad source is specific Ad Source will be skipped and not used but the . The player will continue running and might finish all waterfall cycles (errorlimiterrorLimit) without ever calling those ad sources if the player is not reaching in view.

Ad source These settings are available at the ad source page, player settings tabin 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, dont don't call the ad source Ad Source when not in view.

  • If not set, the ad source Ad Source will be called but startAd will be called only when in view.
    If the ad source respond and waiting for view, and the player finished handline all other ad sources that does not require 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 and if not in view the player 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 viewable impression metric am Impression is Viewable (Viewable Impression metric) according to the MRC guidelines: When the ad is 50% or more of the player in view for at least 2 consecutive seconds.