In order for Developers to better understand all the enhancements and benefits that EdgeNet is bringing them, Alef has created data visualization pages with metrics specific to the service subscribed to. These data visualization tools will be updated in real time, so the Developer constantly has the latest insight possible into the performance of their services. The rest of this section will serve as a tutorial on how to navigate to these data visualization tools.
The first step in accessing the Analytics Page of the Service you want to view is to click “My EdgeNet” along the Horizontal Navigation. From the subsequent drop down that appears, select “My Services”. Please note, if you have not subscribed to an Alef Service, this page will be blank and there are no analytics to be shown. If you have multiple subscriptions to multiple Alef Services, please ensure the Product you are selecting is the Alef Video Notifications Service. There are additional usage analytics documents for different Alef Services.
Once on the “My Services” page, all EdgeNet services subscribed to will appear in a tabular fashion. Each row represents a service that is subscribed. On the far right of each row, there is a dashboard button. Please identify an Alef Video Services and click the first of the dashboard button on the right of the row.
The page that the user is taken to after clicking the first option is shown below. This is the “Content Analytics” page relevant to the Video Notifications Service at the location specified in the row previously selected.
In addition to the “Content Analytics” Page there is an “API Analytics” Page present for additional insight into the performance of the subscribed service. This is navigated to from the Vertical Navigation Bar on the left-hand side of the “Content Analytics Page”. There is a screenshot below for reference.
For each of the Subscription Service that is offered, there are two analytics pages provided to Developers for greater insight into the performance of their services. The first is the “Content Analytics” page and the Second is “API Analytics”. The following sections will provide greater insight into what each of the graphics on each of these pages mean.
The “Content Analytics” Page displays quantitative and qualitative data on the video delivery, video content and the device playing the content. Furthermore, there are campaign analytics being presented such as CTR and Video Campaign Summary.
This graphic is a line chart depicting the total number of videos served in a day over a set period of time. The period of time is able to be toggled such that it shows weekly, monthly or yearly information. This is not indicative of performance of Alef services but rather market interaction with the Video Notification. The X-axis represents the time variable and the Y-axis shows the number of videos that is served.
The expected value this graphic should show depends on the expected market interactions with the video. As aforementioned, this does not reflect on the performance of the Alef service. The higher number of videos played the more reach the video is obtaining.
This graphic is a line chart depicting the number of plays being served relative to the rate at which an individual will complete the video. For example, if someone watched the did not watch the video, watched half the video and the entire video, the completion rate would be 50%. The X-axis contains various groups of completion (0 % – not started, 25%, 50%, 75%, and 100% – video completed). The Y Axis shows the number of plays that fall within the aforementioned groupings.
This reporting metric again is not indicative of the performance of the Alef Service but instead the reaction of the market to your video. For example, if the video is getting a majority of the plays in the 75%-100% completion rate groups the video is being responded to well, as people are completing a majority of the video.
This graphic is a bar chart depicting the completion rate segmented by the type of devices the video is being played on. The X-axis contains the different device types that the videos are being played on. The Y-Axis shows the average completion rate for users of the specific device.
While this is not indicative of Alef performance, the higher the completion rates the greater the engagement. Additional insights can be found into the type of user that your video is catered to. As an example, if Apple Device Users have 100% completion rate and Android Users have 0% completion rate, it is likely due to the target audience.
This graphic is a pie chart that depicts the number of plays among the top 5 devices the video was played on. There will be a legend present on the graph that shows the color and the device associated with it.
The following graphic is a line chart that shows the number of stalls compared to the number of plays a video has. The X-axis represents the number of stalls and they Y-axis represents the number of plays.
This graphic is indicative of Alef Performance. As the video is being served from the Edge there should be significantly less stalls compared to the number of plays. If there is a 1:1 ratio between stalls and plays or greater, it is likely the Edge Site is having an issue.
This graphic is a bar chart depicting the average start up time by the device the video is being played on. The X-axis contains the different device groupings, and the Y-axis shows the average video start time for the specific device.
The video startup time is a reflection of the performance of the Alef Service. The video startup time should be relatively consistent among all devices. Furthermore, the video startup time should remain relatively low across all device types. As an example, a 4K UHD video whose duration is 1.5 minutes should not take more than 10 seconds to start otherwise, there may be an issue at the Edge Site.
This graphic is a bar chart depicting the click-through rate for Video Notifications specific to individual campaigns that are being run. The X-axis shows the campaign name, and the Y-axis shows the total CTR for the specific campaign.
This graphic is not indicative of the performance of the Alef Service. Instead, this graphic depicts the performance of the advertisement in generating additional interest by users clicking the Video Notification bringing them to the URL specified.
This graphic depicts the amount of Click through compared against the number of SMSs sent within a specific campaign. The X-axis shows Campaign Name, The Y-axis shows the number of clicks on the left-hand side and the number of SMS on the right-hand side. This graphic is not indicative of the performance of the Alef Service but instead the audience’s interaction with the Video Notifications.
This graphic is a line chart depicting the duration of the video being served relative to the rate at which an individual will complete the video. For example, if someone watched, did not watch the video, watched half the video and the entire video, the completion rate would be 50%. The X-axis showcases the video duration. The Y-Axis shows the completion rate for the specific video duration.
This reporting metric again is not indicative of the performance of the Alef Service but instead the reaction of the market to your video.
The Video Campaign summary gives a tabular overview of the campaigns. The metrics that are being tracked within the Video Campaign Summary are, Name, Start time, End time, SMS, Clicks, CTR, Plays, and # of times a video was entirely completed.
In order for Developers to better understand all interactions they are having with EdgeNet, Alef has created data visualization pages with metrics specific to the service subscribed to. These data visualization tools will be updated in real time, so the Developer constantly has the latest insight possible into their usage of their services. The rest of this section will provide insight into what each graphic shows.
The “API Analytics” Page displays quantitative data on the Developer’s interactions with The 5G Edge APIs.This data will be shown holistically to view total API usage of a given service, as well as on a per API basis.
This figure showcases the total number of requests by a developer in a given month. The X-axis will show what month is being displayed. The Y-Axis will show count, or the number of API calls that were made by a Developer.
This graphic depicts the number of requests, to all endpoints, completed by the Developer. The X-Axis will indicate what specific API is being used (i.e. GET: /get-all or GET: /get-appkey). The Y-Axis will show count, or the number of times that specific API was hit.
We are sorry that this post was not useful for you!
Let us improve this post!
Tell us how we can improve this post?