I am going to try to raise this issue with Doubleclick, with the following information. As we don’t have any Doubleclick account, we can’t raise the ticket directly, so I will try to raise this with GroupM.
Find the message below:
We have spotted an issue running Doubleclick Vpaid JS wrapper when the publisher has IMA pre-loaded on their side. See the error below that we are seeing:
23% of VAST error 901: linked to the presence of an IMA adapter in the tag which causes a conflict with the IMA (pre-loaded) in our player
The following Vpaid JS mediafile unit, contains a vpaid_adapter. See the screenshot below:
<MediaFile delivery="progressive" width="176" height="144" type="application/javascript" apiFramework="VPAID">
The adapter seems to be conflicting with the pre-loaded IMA.
We have thought about removing the Vpaid unit as they have already the IMA on their side. However, this won’t be the real solution, as it can prevent measuring viewability on the Advertiser’s side to compare potential discrepancies.
Have you heard about this issue? If so, what can be the potential solution to solve it?
--
You received this message because you are subscribed to the Google Groups "Interactive Media Ads SDK" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ima-sdk+unsubscribe@googlegroups.com.
To post to this group, send email to ima...@googlegroups.com.
Visit this group at https://groups.google.com/group/ima-sdk.
For more options, visit https://groups.google.com/d/optout.
https://developers.google.com/interactive-media-ads/docs/sdks/html5/vastinspector
This can occur when the "IMA Adapter" tag from Ad Exchange is used with the IMA SDK, and a VPAID ad is returned. You should use the "Direct SDK" tag from Ad Exchange when using the IMA SDK.
This can occur when the "IMA Adapter" tag from Ad Exchange is used with the IMA SDK, and a VPAID ad is returned. You should use the "Direct SDK" tag from Ad Exchange when using the IMA SDK.