Top Content
  • 15 Mar 2024
  • 3 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

Top Content

  • Dark
    Light
  • PDF

Article summary

The Top Content report in the Content section displays user metrics for all your content types, including Video, Audio, and Fast Channel. It offers valuable insights into how users interact with each content type.


 List of metrics

PlaysNumber of PLAY event. The "PLAY" event is triggered by the Player as soon as user clicks on a video and the video starts playing. 
Avg. Video Run-Time The total watch time of a video (in minutes).
Total Video Length = # Plays * video runtime
Avg. Video Run-Time = Total Video Length / # Plays
Avg. Play Duration

The average watch time for a video (in minutes).

Total Play Duration = Number of PING event * 30
Average Play Duration = Total Play Duration / # Plays

% Play-ThroughPercentage of a video being played from beginning to end.
Calculated as:
Avg. Play Duration / Avg. Video Run-Time

Note: The Content report export now includes an additional "Video ID" column.

FAQs -  Top Content 

Q. Play-Through% is exceeding 100%.

Play-Through% exceeding 100% could be due to two reasons:

  • We are getting duplicate records. 
  • We are not getting PLAY event for many streams.

This table helps you analyze how missing or duplicate PING events might affect the "Total Play Duration" metric.

To confirm the information on your end, you would need to request the data from us as this data is fetched from the BE. Feel free to raise a Support ticket.

Q. In the Top Content Report, what is the Avg. Video Run Time, Avg. Play duration and their interplay with % play through?

Warning
Always set an approximate runtime (duration of the game) when configuring the live object that you plan to convert to VOD. This practice aids in accurately calculating playthrough and average play duration metrics.

On a Live object page, the default setting for the Running Time field in the File Details section is 0. When the live video is later converted into VOD, a proper runtime may be assigned. However, let's assume that 200 people watched the live video for 60 minutes each, the total play duration is calculated as (200 * 60) = 12000. 

Once it is converted to VOD (full replay) and the runtime is updated as 60 minutes and 100 people had watched the replay for 30 mins each, the total play duration is calculated as (100*30) 3000, and the total runtime of the video is 6000.

Below are the calculations:
Total play duration = 12000 + 3000 = 15000
Total Plays = 100 + 100 = 200
Total runtime = 0 + 6000 = 6000

Average play duration = total play duration/total plays  = 15000/200 = 75

Playthrough = total play duration / total runtime   = (15000 / 6000) * 100 = 200 % = 100% (playthrough value is maxed to 100)

That's the reason you are seeing 100% playthrough and high average play duration for some of the videos. 

Q. Is Play Duration based on minutes? 

Total Play duration is based on minutes. We receive beacons from the web and apps every 30 seconds. So if we receive 2 pings (at 30th second and 60th second) then it is considered as 1 minute. So if the user watches for 60 seconds, then it is considered as 1 minute. If the user watches 65 seconds, then it is considered as 1 minute. If the user watches 90 seconds, then it is considered as 1.5 minutes.

Q. The Avg. Video Run Time is showing 0.
Please check if you have set the runtime for the videos. 

Note also that the Play Through percentage might display as 100% if the runtime is not specified for the video, livestream, or fast channel. To ensure an accurate Play Through percentage, it is recommended to set the runtime of the content. By providing the correct runtime, the Play Through percentage will reflect the actual playback progress and may be less than 100%.

Q. Why is the same content appearing twice, one capitalized, and another in title case?

The content may have originally been ingested with lowercase titles from the feed and then updated later. As a query/request groups the number of plays by series title, it reflects as two different entries.


Was this article helpful?