Quality of experience (QoE) metrics

The QoE metric in FastPix quantifies the Quality of Experience (QoE) of video streaming using a single numerical value ranging from 0 to 100. A score of 100 indicates an entirely satisfying experience for all viewers, while a score of 0 signifies a universally frustrating experience. This score is derived from four key performance elements: Playback Success, Startup Time, Playback Stability, and Render Quality. Each video view is assigned an experience score based on these elements, which are then averaged to calculate the Overall Viewer Experience Score.
Why QoE is important?
The Overall Viewer Experience Score is crucial for assessing the effectiveness of video streaming services from the viewer's perspective. It provides a holistic view of how well content is delivered and received, allowing platforms to identify strengths and weaknesses in their streaming performance. By understanding this score, content providers can prioritize improvements that enhance user satisfaction, reduce churn, and ultimately drive viewer engagement.
Using QoE to build video better
To utilize the Overall Viewer Experience Score effectively, analyze it alongside the individual component scores (Playback Success, Startup Time, Stability, and Quality) to pinpoint specific areas for improvement. Monitor changes in the Overall Viewer Experience Score over time to evaluate the impact of optimizations or new content releases.
Additionally, you can compare scores across different videos or time periods to identify trends in viewer satisfaction and make informed content strategy decisions. By focusing on improving this score, you can enhance the overall service quality and deliver a better viewing experience.
The formula for the Overall Viewer Experience Score is given by:
Overall Experience Score = Playback Success Score * (w1 x Stability Score + w2 x Render Quality Score + w3 x Startup Score)
Using API to get QoE score
You can get the Quality of Experience score for your videos in two scenarios. One for an individual view session and other one for the entire set of video content in your platform or selected workspace in FastPix. In the second scenario, the score is derived as the average of all the QoE scores of each view session. You can get the score as per the timespan specified and filter by any dimensions as required.
QoE score for one view session
Use the Get details of video view API to retrieve detailed information about a specific video view. You would need to pass the viewId
for the particular view session that you need details for. Once you send the request, the qualityOfExperienceScore
attribute in the response will give you the QoE score for the required view session.
curl --request GET \
--url ‘https://v1.fastpix.io/data/viewlist/viewId' \
--header 'accept: application/json' \
--user '{Access_Token}:{Secret_Key}
QoE score for all content
Using the List overall values API you can retrieve overall values for a specific metric. It gives you a summary statistics so you can understand the performance of your content.
This would be a GET request where you need to pass the metricId
along with other query parameters to receive a response containing the overall value of the metric you are looking for. In this case, use quality_of_experience_score
as the metricId
.
curl --request GET \
--url ‘https://v1.fastpix.io/data/metrics/quality_of_experience_score/overall' \
--header 'accept: application/json' \
--user '{Access_Token}:{Secret_Key}
Refer to our API reference for details on additional query parameters.
You can use this API to also get the overall value for all other metrics. But, first you would need to know the metricId
for the metric that you are looking for.
You can also filter the metric values using the filterby[]
attribute. Simply pass the dimensions and their corresponding values you want to filter the views by. An easy way to do that is first calling the List dimensions endpoint to retrieve all available dimensions that can be used in your query.
curl --request GET \
--url ‘https://v1.fastpix.io/data/dimensions' \
--header 'accept: application/json' \
--user '{Access_Token}:{Secret_Key}
Updated 3 days ago