When <amp-video> is used inside of AMPHTML ads, a common usecase is the ability to fire an event on every quartile. Currently, this doesn't seem possible in <amp-video> analytics.
https://github.com/ampproject/amphtml/blob/master/extensions/amp-analytics/amp-video-analytics.md
Seems like a good feature to have鈥攏ot sure who would own this in the end between UI & Analytics, so /to @lannka as well. Pending discussion between @lannka and @aghassemi
@jasti this particular feature was considered in the initial design as a video-percent-played trigger but was deprioritized because it is technically possible to get the same behaviour using the existing video-seconds-played trigger if duration of the video is known ahead of time. For quartile, simply configuring video-seconds-played trigger with totalDuration/4 would behave the same. Is that work-around acceptable in the use-case where this request came up in?
@aghassemi right, issue is that the publisher who is implementing the ads doesn't have an idea about the length of the video.
@aghassemi I saw this was put in "higher priority with low effort" bucket. Did we prioritize for the next sprint?
@lannka no, we can though if a priority for Ads.
(stuff in "higher priority with low effort" bucket does not get planned, it is meant for "if you feel like fixing something, here is a list of candidates")
@alanorozco Since you have been doing video analytics recently, do you think you can fit this request in your schedule? It is needed for A4A. Should be fairly similar to the current video-seconds-played which takes in an internal param.
Maybe we can call it video-segment-played and take in a segments:<n>. So to get quartile tracking, segments = 4 (maybe it can also default to 4 if not provided)
Other naming options I can think of are video-percent-played with a segments:<n> param.
/cc @cvializ for thoughts as well.
thx @aghassemi . to be even more flexible, does it make sense to let it take an array of percent numbers ?
{
on: "video-persent-played",
spec: {
segments: [25, 50, 75, 100]
}
}
naming TBD
I like that, doesn't enforce segments to be equal which is good.
Just for naming consistency:
{
"on": "video-percentage-played",
"spec": {
"percentages": [25, 50, 75, 100],
}
}
hi @alanorozco , just a status check, is this on track?
Hi @lannka. Not yet, expect to be prioritized for next sprint.
This is a high priority issue but it hasn't been updated in awhile. @alanorozco Do you have any updates?
Most helpful comment
Just for naming consistency: