Last version of IMA player move the call to VPAID initAd from adsManager.init to adsManager.start

[Yohan Boutin]

Hi IMA Team

Since the last release of the IMA player 3.332.1, the call to the initAd method on VPAID creative has moved from Adsmanager.init() to AdsManager.start()

This is a major change, and there is strictly no information or documentation from your side on this.

The initAd() method in the VPAID specification is made to preload everything and to trigger the `AdLoaded` event when the ad is ready. Then when you receive the AdLoaded event, you can call startAd() safely.
The initAd() function can trigger an AdError event (used by many client side adsmanager when no ad, or simplify when something break inside the VPAID), or an AdLoaded event.

Now, in the IMA player, when you call init(), is no more call VPAID creative `initAd`. This mean there is no more initialisation of anything in the IMA player when the ad is a VPAID. The problem with that is 90% of the market is using VPAID, and now when deliver an ad with a viewability wrapper (IAS, MOAT, Google DBM wrapper, APX wrapper ...) you loose all the advantage of the preload.

Can you please communicate with us the motivation of this change ? Why introduce a major change just before Q4 ? Do you think about coming back to the previous flow ?

Keep us posted,

Thanks

[IMA SDK]

Hi Yohan,

Thank you for reaching out to us and your concern has been acknowledged.
Our team is fully aware of this issue, and is currently working on the documentation updates regarding the VPAID preloading.

In the meantime, please refer to future releases of the IMA SDK for HTML5 for further updates.


Regards,
Sherwin Diesta
IMA SDK Team

ref:_00D1U1174p._5001UHHJCI:ref