Re: [ima-sdk] Digest for ima-sdk@googlegroups.com - 4 updates in 2 topics

14 views
Skip to first unread message

Hoa Cao

unread,
Mar 14, 2025, 1:59:09 AMMar 14
to ima...@googlegroups.com

Vào 19:48 Th 3, 11 thg 3, 2025 <ima...@googlegroups.com> đã viết:
Krishna saini <krishnap...@gmail.com>: Mar 09 10:55PM -0700

Hi Team
We are using Exo player IMA extension for rendering video ads. We dont use
exo player controls and render our own webview on top of player. We have to
part this webview as friendly to support viewability.
To do that, we tried two things -
1. we have modified getAdOverlayInfos() method of PlayerView class & marked
our whole react app's webview as friendly & returning them via
playerView.getAdOverlayInfos(); This is done as suggested by this article
-
https://developer.android.com/media/media3/exoplayer/ad-insertion#ui-considerations
 
Screenshot is attached that telling which all views are returned by
getAdOverlayInfo.
 
2. we have tried marking our app's webview friendly via displayContainer.
registerFriendlyObstruction(overlayObstruction) too. we are doing this at
the time of `Ad_LOADED` event is fired. This is done as per this article -
https://developers.google.com/interactive-media-ads/docs/sdks/android/client-side/omsdk
 
still we are seeing that OMSDK firing geometry change event with 0 value of
percentageInView. we verified it via running its test script.
 
Questions-
1. what we are not doing correctly in approach 1
2. as per article 2, it was mentioned there `Any other views not related to
video controls must not be registered.` what kind of views is this talking
about. can a webview be marked as friendly ?
 
Requesting the team to futher guide us please.
IMA SDK <ima...@forumsupport.google>: Mar 10 10:42PM

Hi Krishna,
 
Thank you for contacting the IMA SDK support team.
 
The IMA SDK supports these platforms in which react is not listed. You may visit IMA SDK supported video player documentation for more information about the supported platforms. You can also check the Ads Developer Blog to keep up with the latest news and updates.
When ad viewability via the Open Measurement SDK is calculated, all views overlaying the media element are considered obstructions and reduce the viewability rate. In the case where a transparent tap overlay sits above the entire ad display container, it is possible for inventory to be declared completely unviewable.
 
The Open Measurement SDK makes provisions for video controls to be considered "friendly" obstructions that are essential to the user’s experience. Once registered as friendly, these controls are excluded from ad viewability measurement.
With IAB and MRC support, the IMA SDK introduces an API for registering these overlays with the Open Measurement SDK. These controls must be fully transparent overlays or small buttons. Any other views not related to video controls must not be registered.
 
 
Kindly check the OMSDK guide for more information. Also note that this team can best assist issues related to IMA SDK Integration and technical implementation.
 
Thanks,
 
IMA SDK Team
 
 
Feedback
How was our support today?
 
 
[2025-03-10 22:42:32Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH8HE:ref" (ADR-00293132)
ChangIL Yoon <ci....@altimedia.com>: Mar 06 04:41PM -0800

Hello,
 
I see that the following webview process begins to run whenever I run the
BasicExample of Google Ads IMA Android Examples
 
-
com.google.android.webview:sandboxed_process0:org.chromium.content.app.Sand
 
The webview process seems to be mantatory to use IMA-SDK on Android.
Is it correct?
If it is wrong, can you please let me know how to run the BasicExample
without webview?
 
Sincerely
Changil
IMA SDK <ima...@forumsupport.google>: Mar 10 06:43PM

Hi Changil,
 
Thank you for contacting the IMA SDK support team.
 
Based on the information I can confirm that the platform is Android, can you please confirm if the integration type is client side or server side (DAI)?
 
Yes, the Google IMA SDK on Android does utilize a WebView internally to render HTML5 ads. I ran a basicExample from client side and basicExample from server side with the IMA SDK v3.36.0 in the emulator Pixel 9 Pro XL API 35 and the reported issue "com.google.android.webview:sandboxed_process0:org.chromium.content.app.Sand" is not replicating. Can you confirm if the reported issue is replicating in our Google basicExamples mentioned above? If yes, Kindly provide the below details for further investigation so that we can check, find the root cause and may provide the solution:
 
Steps to reproduce
SDK version being used
Device affected if any
Sample project reproducing the issue (if possible)
 
You can provide the following details via reply privately to the author option or directly provide it to this link.
 
 
Thanks,
 
IMA SDK Team
 
 
Feedback
How was our support today?
 
 
[2025-03-10 18:43:50Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH8H9:ref" (ADR-00293131)
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to ima-sdk+u...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages