You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using the client Web SDK in JavaScript to be able to send OMID tracking.
When we are about to close an Ad, due to an User Interaction, we call the method adContext.finish() before closing the Ad. The issue is that we do not know "how long" to wait before closing the Ad to be sure the Track is sent.
On a documentation I found on a Java Client, it is said 1 second. However, we found this a bit random when using this approach.
Is there a way to get a kind of promise to be sure when the track is sent ? Such as:
await adContext.finish();
closeAd();
The text was updated successfully, but these errors were encountered:
Thanks for reporting this. We have actually recently had some discussion about this exact feature in the OM Working Group, and we agree that a promise or callback-based API would be better. It will not be a trivial feature to implement because currently there is no way for verification scripts to signal back to OM SDK that they are finished sending all pings. We may first introduce a promise-based API that just waits 1 second and then later improve it to actually wait for scripts to finish. I will keep this issue updated with any progress.
We are using the client Web SDK in JavaScript to be able to send OMID tracking.
When we are about to close an Ad, due to an User Interaction, we call the method
adContext.finish()
before closing the Ad. The issue is that we do not know "how long" to wait before closing the Ad to be sure the Track is sent.On a documentation I found on a Java Client, it is said 1 second. However, we found this a bit random when using this approach.
Is there a way to get a kind of promise to be sure when the track is sent ? Such as:
The text was updated successfully, but these errors were encountered: