|
||||||
Hi Damian,
Thanks for your response. Could you please elaborate on the issue with regard to the incorrect SRC property of HTML5 video element on Android Chrome? It would be great if you could give more details so we could check further.
Regards,
|
||||||
Hi Damjan,
Thanks for getting back to us and for sharing additional information regarding your concern. I was able to replicate this behavior using our advanced sample app for HTML5. I’m going to share this with the team to check further and will let you know once we have an update.
Regards,
Hi Damjan,
Just an update. I received feedback from the team about the src attribute being added inside the video element when on iOS but not with Android. The team confirmed that the IMA SDK doesn’t cause this behavior but it seems to be how the Chrome browser handles the different environments. Do you have any specific issues related to this behavior?
Regards,
Hi Damjen,
Thanks for your response. Just wanted to clarify your concern on view through rate (VTR) tracking. Is this about your implementation of replaying the video from the ad without triggering an ad impression? Or is it about the src attribute not being added inside the video element on Android Chrome?
If this is regarding the former, then I’m afraid we can’t tell if this may affect the VTR since this is a custom implementation. I would suggest reaching out to your ad account manager to check the numbers of completed views of ads over the number of impressions.
However, if this is regarding the latter, then this shouldn’t have an effect on the VTR for Android Chrome considering that this is the common behavior (as per testing by the team) as compared with the iOS where it does update the video tags src. As a side note (for iOS Chrome). If you added playsinline to the video element, this will stop updating the video tag's src attribute.
Please let me know if you have further questions or clarifications.
Regards,