Page MenuHomePhabricator

Introduce a new AQS endpoint to expose video plays
Open, Needs TriagePublic

Description

Part of getting T198628: Count the number of video plays done. We currently show number of plays and loading of poster image in the existing AQS endpoint. Since most people don't click on videos, this has drastically diluted the data rendering it useless for measuring video plays.

There is a patch that would start ignoring loading of poster images but that would mean the definition of data will change halfway through. So a better solution would be to add a column splitting poster load vs. actual play, sum them in the old endpoint but introduce a new endpoint in AQS that would provide both numbers separately (so people can also measure click-rate ratio).

Event Timeline

Ahoelzl added subscribers: GGoncalves-WMF, Ahoelzl.

@Ladsgroup we need to understand priority and scope. @GGoncalves-WMF will reach out to you.

The question is do our readers watch videos on our platform? This is a question we do not know the answer to as we have never had this data. Getting this data is key to increasing video efforts within our movement. I highly support this work as being of top priority. @Yaron_Koren has done some work within this area.

Having spoken to @Ladsgroup this morning (thanks!), here's my notes on this task.

There are three potential quality issues in how we surface video plays:

  1. As previously pointed out, AQS counts both poster views and videos being served as "mediarequests", which is not usable for counting video plays. The proposed new endpoint, semantically capturing video plays and capturing poster vs plays as dimensions, sounds like a good idea to me. This should be the scope of this task, and I think is the highest priority.
  2. The incoming rollout of MPEG-DASH, driven mainly by reliability, will also mean we need to adapt our video play metric. This belongs in a separate ticket at medium priority, and @Ladsgroup is the point of contact to coordinate with. It will take a few weeks for MPEG-DASH to actually happen.
  3. There is a suspicion that Apple devices are requesting video chunks at a time for playback (probably due to their HLS implementation), each of which already is being counted as a separate mediarequest. We haven't quantified this yet, and pending that, I'd put this at lowest priority of the three. Further investigation also belongs in a separate ticket.

Why is all of this important? T198628#10567446 is a good summary from WMDE (who depend on this metric for strategic partnerships).

What about timelines? We'll need input from @Ahoelzl, but this doesn't look like a very complex task and we can try to get started in a couple of weeks.