RE: [ima-sdk] Large number of errors from omweb

[IMA SDK]

Hello Kevin,

 

Michael here from IMA SDK Team. Thank you for reaching out to us.

 

I have tested the VSI link you shared and it seems that the ad and content are playing as expected. Additionally, the error logs you are referring to are not reproducible using our sample tags, thus it appears not to be an SDK issue. Having that said, we would ask you to reach out to your ad provider and confirm if this is an ad tag issue as we do not have full visibility and knowledge on configuration of ad tags. You may come back here any time if they confirmed that the ad tag in question has no issues.

As a side note, I have removed your post from the forum thread as it contains sensitive information. Rest assured that we have a copy of that message and will be used for future references if needed.

Regards,

Michael Angelo IMA SDK Team

ref:_00D1U1174p._5004Q2by3NP:ref

[R Baudisch]

I reported that also but got deleted.

Michael, please take that serious!

MfG R.Baudisch

[Kevin Brogan]

Michael, your sample tags DO NOT TEST the Open Measurement functionality.



 Please reopen the ticket and pass it off to someone familiar with the sdk's implementation of the omweb-v1.js file.

The tag in question:


IMA Sample tags - missing AdVerifications tag

Kevin Brogan Senior Developer, STN Video 250.590.1991   |  TF: 1.855.590.1991 kevin....@stnvideo.com

--
You received this message because you are subscribed to a topic in the Google Groups "Interactive Media Ads SDK" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ima-sdk/VHsINvCvJcY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ima-sdk+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ima-sdk/d0484504-e350-4b51-b40e-be4ee1d1c210n%40googlegroups.com.

[IMA SDK]

Hello Kevin,

 

Thank you for further clarifications. With this, I have raised the concern to our wider team for further investigation on the reported behavior. We will get back to you on this thread as soon as we have received sufficient information. Your patience is highly appreciated.

 

@R.Baudisch, we are taking seriously all reported behavior of the SDK. I can see that the forum thread where you reported the same issue was deleted, but know that I have already responded to you there privately and again on the new generated forum thread. You may check your spam messages if you are having trouble receiving private responses from us.

Regards,

 

[R Baudisch]

Hi Michael,

I'm concered that since this is not only related to the imasdk but to OMID that could be on the page, while the imasdk uses it and expirences an error, what makes it just related to not causing this issue.

That why I complained get this taken serious. It may end in the IAB has to change OMID but we first have to figure out what exactly happens here.

Best 

René 

[IMA SDK]

Hi René,

Teejay here. I understand your concern here. This has been flagged to a wider team, and confirmed that the issue is reproducible on our end as well. We'll update this thread the soonest the team share their investigation findings.

Regards,

Teejay Wennie IMA SDK Team

ref:_00D1U1174p._5004Q2by3NP:ref

[IMA SDK]

Hello Kevin,

 

Hope you are doing well.

 

Our team responded back to us that this seems to be an implementation issue.

 

Adding the following lines to the adsRequest resolved the error:

adsRequest.omidAccessModeRules = {};

adsRequest.omidAccessModeRules[google.ima.OmidVerificationVendor.OTHER] = google.ima.OmidAccessMode.DOMAIN;

 

You can get more info on this from the OM SDK HTML5 guide. It looks like the tag linked is using doubleverify, which can be specified as a vendor as well (see the OMID verification vendor values).

 

Let me know if you have feedback.

Regards,