allAdsCompleted

345 views
Skip to first unread message

Arik Bron

unread,
Sep 1, 2019, 12:35:14 PM9/1/19
to Interactive Media Ads SDK
Hi,

We are trying to use standard VPAID unit within IMA Player.

In both real-time running as well as in the IMA VAST Inspector page (https://developers.google.com/interactive-media-ads/docs/sdks/html5/vastinspector) when the ad ends the player doesn't continue to the regular content.

It looks like the player is missing allAdsCompleted event.

Can someone please help us understand what this event is? It is not VAST nor VPAID event, and it is absolutely not clear under what conditions the player decides that All Ads Completed.

IMA SDK

unread,
Sep 2, 2019, 3:33:23 AM9/2/19
to arkad...@gmail.com, ima...@googlegroups.com
Hi Arik,

Thank you for reaching out to us. Let me do the best I can to assist you on this.

With regard to your concern, the ALL_ADS_COMPLETED event fires when all ads managed by the current ads manager have finished playing. 
On the other hand, could you please provide us your Ad tag so we could check the issue on our end as well? Please use the "Reply to Author Privately" option to share the details privately.

Regards,
Teejay Pimentel
IMA SDK Team

 

ref:_00D1U1174p._5001UHFMOT:ref

Arik Bron

unread,
Sep 2, 2019, 4:09:48 AM9/2/19
to Interactive Media Ads SDK
It looks like the IMA SDK is expecting to receive AdStopped event after AdVideoComplete event - in order to reach allAdsCompleted status.

IMA SDK

unread,
Sep 2, 2019, 6:59:40 AM9/2/19
to arkad...@gmail.com, ima...@googlegroups.com
Hi Arik,

Thank you for providing your Ad tag privately. 

As per checking, it seems that your Ad tag is not accessible anymore (please see attached file). With this, could you please contact your Ad provider regarding this?
Screen Shot 2019-09-02 at 6.41.30 PM.png

Arik Bron

unread,
Sep 2, 2019, 7:15:43 AM9/2/19
to Interactive Media Ads SDK
Hi,

The server side code was upgrading - it is up now.

From what we saw the SDK expects to receive AdStopped event after AdVideoComplete - only then it reaches the conclusion that allAdsCompleted.

I would appreciate your help with the additional post here about SDK making 2 requests to the VPAID Ad Tag provider prior actually playing the ad: https://groups.google.com/forum/?hl=us#!topic/ima-sdk/_WAV1MFqLE8

IMA SDK

unread,
Sep 3, 2019, 2:44:47 AM9/3/19
to arkad...@gmail.com, ima...@googlegroups.com
Hi Arik,

Thank you for getting back to us.

I tested your Ad tag using our sample app and I'm getting this error (please see attached file). I've raised your concern with the rest of the team to get an insight on this. As per discussion, it appears that the issue is on ad creative as the ad doesn't send allAdsCompleted event. With this, I would suggest to contact your ad provider for further assistance on this.

On the other hand, I've checked the other forum thread that you mentioned and it appears that my colleague have already responded there. Please continue the discussion there instead for better tracking of the issues.
add tag logs.png

Arkady Bron

unread,
Sep 3, 2019, 5:20:48 AM9/3/19
to IMA SDK, ima...@googlegroups.com
Thank you for investing the time into this,

allAdsCompleted is not a standard event. It is an internal state of the IMA SDK invented on top of VAST or VPAID specifications. As such, it cannot be fired by a standard VPAID ad.

The problem was that the VPAID ad was not firing AdStopped VPAID event, and therefore IMA SDK was not reaching allAdsCompleted state.

It was resolved in the VPAID ad implementation.
Reply all
Reply to author
Forward
0 new messages