Adobe-Marketing-Cloud/media-sdks

Chromecast | Adobe | Heartbeat | Ad event calls are not in sequence

sunilvishwakarma-nbcuni opened this issue · 6 comments

sunilvishwakarma-nbcuni commented

Hi,
When we play a VOD asset and while playing when the adbreak starts below are the Hearbeat methodes I am calling:
ADBMobile.media.trackEvent('adBreakStart', info);
ADBMobile.media.trackEvent('adStarted', info);
ADBMobile.media.trackPlay();

Now, If I track the Heartbeat calls in a proxy then the s:event: type sequence for ads should be like - start, aa_ad_start and play but in actual these events are in a random sequence.
Please help me in fixing this issue.

Thanks,
Sunil Vishwakarma
CC: @dipanmajumder-nbcuni

cacheung commented

Hi Sunil,
Usually the platform might send http requests out of order, but it is not an issue as we record the timestamp in each http call.

Best Regards,
Calise Cheung
Adobe Engineer

sunilvishwakarma-nbcuni commented

Hi Calise,
Below is one more scenario where I want you to confirm if it's an issue or not:

  1. Cast the application to the chromecast.
  2. Played a VOD asset.
  3. Scrubbed from Chapter 1 to Chapter 3.
  4. Scrubbed again from Chapter 3 to 2.
  5. Now, a midroll ad will be played and after ad completion, a new chapter 2 will start and in this scenario, sometimes we are seeing one play call in between AdBreakComplete and Chapter_Start calls in Heartbeat.

Here is the sequence of Heartbeat methods we are calling:
ADBMobile.media.trackEvent('AdBreakComplete', info);
ADBMobile.media.trackEvent('ChapterStart', info);
ADBMobile.media.trackPlay();

Thanks,
Sunil Vishwakarma
CC: @dipanmajumder-nbcuni

cacheung commented

Hi Sunil,
Can you tell me what's the timestamp/time for AdBreakComplete, Play and Chapter_Start calls when you have this case?

Thanks,
Calise

sunilvishwakarma-nbcuni commented

Hi Calise,
Below are the request and response time details:

AdBreakComplete:
Request Start Time : 3/10/19 17:1014
Request Complete Time : 3/10/19 17:1014
Response Start Time : 3/10/19 17:1014
Response Complete Time: 3/10/19 17:1014

Play:
Request Start Time : 3/10/19 17:1014
Request Complete Time : 3/10/19 17:1014
Response Start Time : 3/10/19 17:1014
Response Complete Time: 3/10/19 17:1014

Chapter_Start:
Request Start Time : 3/10/19 17:1014
Request Complete Time : 3/10/19 17:1014
Response Start Time : 3/10/19 17:1014
Response Complete Time: 3/10/19 17:1014

You see the timings in the below screenshots as well.
AD_Complete:
AD_Complete
Play:
Main_Play
Chapter_Start:
Chapter_Start

Thanks
Sunil Vishwakarma
CC: @dipanmajumder-nbcuni

cacheung commented

Hi Sunil,
Thanks for detailed info. It shows all of three events had the same timestamp. Since we can't guarantee the order of the http request, so it is possible sometime Play event sent right before the Chapter Start event in this case. This is fine and should not affect the reporting.

Best Regards,
Calise Cheung
Adobe Engineer

sunilvishwakarma-nbcuni commented

Thanks, Calise!
Now, I will consider both the scenario as not an issue and if in future I will notice any mismatch sequence scenario with different timestamp I will raise a new bug.

Thanks,
Sunil Vishwakarma