FAQ: Analytics Module
1. What is the Analytics module?
The Analytics module is a user-interface module you can use to view close to real-time analytics information on your videos and players. The Analytics platform uses the latest innovations in big data technology and is architected for massive scale. The analytics platform offers fast, close to real-time access to analytics data and includes a powerful open API to allow developers to create custom analytics solutions and reports in addition to those included within Beacon Studio.
2. Can I export report data from the analytics module?
Yes. The analytics reports have links that can be used to download the report data to .csv and .xlsx files.
3. How frequently is the data updated in the analytics module?
Normally, the close-to-real-time data is delayed approximately 3-4 hours. That time may vary depending on the volume of data currently being received by the data collection system, however.
Note that the Analytics system compiles data from multiple sources, and close-to-real-time data is an approximation based on data gathered so far. Numbers may vary from one report to another, and should be viewed as trends rather than hard figures.
4. Can the standard reports that are available in the Analytics module be customized?
The data displayed in the Performance and Engagement reports cannot be customized. However, the Analytics module provides the ability to create custom analytics reports allowing you to select the data to display. There is also an Analytics API which can be used to access the analytics data programmatically.
What data is available?
5. Is there a way to include our internal video IDs into reporting or your API?
There is a Reference ID field available as a video property that you can use to map your internal id to videos in Beacon. The reference ID field can be displayed when creating a custom report. For more information on custom reports, see Creating Custom Analytics Reports in the Analytics Module.
6. How can you report on customer engagement and drop off of a particular video?
The Engagement Report shows this information. When you select the Engagement Report and select the Video dimension, you will see a graph showing overall engagement for your account. If you select a video, you will see a graph displaying the engagement for that video over time.
7. Can I report on URL? For example, if we have the same video hosted on Page A and Page B, can we compare the performance between the two placements?
Yes. The Performance Report offers the ability to view video analytics by display domain.
8. Can I run a report to show the number of unique viewers for my account?
The number of unique viewers can be seen in the Performance Report.
9. Are analytics for deleted videos included?
The Analytics reports do include analytics for videos that have been deleted from your account. However, you cannot search for deleted videos in the Analytics module to see a report on a particular deleted video. To get such a report, you will need to know the video id for the deleted video and use the Analytics API to generate the report. Note that if report data is exported, data for deleted videos may appear without some of the video metadata.
10. What is the earliest date that I can get analytics data?
The earliest date for any analytics data is 28 December 2010. Some data items were not collected until later, so the earliest date you can see data will depend on exactly what you are looking at. Video views are available back to 28 December 2010. Note that when navigating dates using the calendar control, it will only navigate back to January 2013, however, earlier dates can be entered manually.
11. Does analytics track players with live event streaming?
Analytics tracks viewed minutes as part of the Performance report. Live seconds viewed can be displayed when creating custom reports or through the Billing module. Live event bandwidth is not displayed.
12. Is it possible to filter out IP address ranges from our analytics?
The ability to filter out IP address ranges is not available at this time.
13. Can I exclude employee views from analytics reports?
There is no easy way to do this, and for high-traffic videos, employee views are probably such a small percentage that their effect on analytics is negligible. However, for low traffic videos where you think it's important to do this, the simplest solution is to duplicate your production player(s) and have employees test/view videos on the copies. You can then use filters to create reports on your production player(s) only, using either the Custom Reports feature in the Analytics module or the Analytics API.
14. How do I find information on a specific video through the analytics module?
The search feature can be used to search for a specific video. The video name, short description, long description, tags, video ID, reference ID and any custom text fields you have will be searched. Clicking on a result will display the performance or engagement for that video. Custom reports can also be created to display analytics for a given video ID.
15. Can I search for a specific video using reference ID in the analytics module?
Yes. The search feature can be used to search for a video based upon the reference ID field. The video name, short description, long description, tags, video ID and any custom text fields you have will also be searched.
Understanding the data
16. What happens if there is a pre-roll ad before a video and a viewer watches the ad for a few seconds and then leaves. If the viewer didn't watch the main content at all, is that counted as a video view?
No. A video view is counted only after the main content starts playing.
17. If a video is looping, does that count as one video view or multiple views each time the video plays?
Video views are counted only once per viewing session when the stream starts. Note that the Views at x% in the Engagement Report is not the same as a Video View in the Performance Report. A video view is counted when a video first starts playing back. The views at 1% is recorded when the first percent is watched. The difference here is that if the first percent is watched multiple times (if the video is set to auto-replay, for instance), the count increases, whereas a video view is counted when the video first starts playing back but is not counted on a replay (unless the user reloads the page or watches another video in the playlist, etc).
18. Why are some engagement scores very high, greater than 100?
It is possible for the engagement score to be greater than 100. Scrubbing and re-watching a video doesn't trigger new video_view events, but it does track video_engagement. For example, say we have a video in a single video player on a page somewhere. The following events show how the video engagement could vary widely:
- No watches yet. Engagement Score: 0.
- A viewer loads the page and watches the video all the way through. Engagement Score: 100 (100 percent viewed / 1 view).
- The same viewer scrubs back and watches it all the way through again (browser was not reloaded). Engagement Score: 200 (200 percent viewed / 1 view).
- Another viewer loads the page and watches the entire video. Engagement Score: 150 (300 percent viewed / 2 views).
For more details on how we calculate video engagement, watch the training video Calculating Video Engagement.
19. Why is the metric for Views at 25% higher than Views at 1%?
There are a couple of factors which can cause the discrepancy in the two numbers:
- Views at 1% and Views at x% are two different metrics. Views at 1% is unique per viewing session and does not include rewind and replay. When a viewer replays or rewinds to a previous part of a video, the % point will increase the audience count but not video view.
- The Views at % and engagement curve are stored in daily granularity using UTC time, so a specific date might sometimes include 2 days worth of data if UTC and reporting time zone crossover.
20. Why do the number of video views for a given day vary over time?
The analytics system provides unreconciled recent metrics collected each hour, and automatically reconciles with actual metrics reported at the daily level. This reconciliation happens as soon as possible, usually in 3 to 5 days. We never reconcile data collected at the hourly level. Since publishers value hourly data, we make the hourly unreconciled data available for 32 days. Some further details on the reconciliation:
- Players send data to the Data Collection API
- The Data Collection API does its best to write to the real-time database AND it writes the events to log storage
- As we collect additional data from CDNs and other sources, the analytics data is updated; this is the reconciliation process
- A nightly batch system looks at the raw log events and builds historical data import files
- The data import files are loaded into the historical database. When you make an API call, you can choose whether to see only reconciled data (most accurate) or to see both reconciled and unreconciled data by using the reconciled parameter. See the Analytics API Overview for more information.
- All historical data is reconciled; realtime data (available for 32 days) may or may not have been reconciled yet. If the time period you are getting data for ends more than 32 days ago, there is no need to use the
reconciled data, since the data will all be historical.
21. Why do some metrics return a null value or have no value?
This will happen if a metric is not available for the time period you have requested. Some metrics have 2 - 3 days of latency, so if, for example, you asked for this data over the last 30 days (including today), these metrics may be null since the requested range includes days that do not yet have this data. To avoid this when requesting data, make sure that the range requested is outside of the latency period.
We have also added additional metrics and dimension combinations over time. So, for example, if you are running a multi-year report, some of the metrics may be blank, or partial, due to the fact that we did not track that metric for the entire reporting date range. For information on valid dates and dimension combinations, see the Analytics API Overview document.
22. Why does destination domain data from 2013 not match other performance data?
The destination domain feature was not turned on until January 2014. Data from March 2013 to January 2014 was partially backfilled, but only some destination data is available for this time period. Data from January 2014 forward is complete.
23. Why don't I always see whole numbers for engagement?
It is possible for engagement numbers to return with decimal points. The reason is because engagement is normalized which means that it's a ratio of "video_percent_viewed * (video_engagement_25 / video_engagement_sum)" so based on the time range selected for the query you may see floating point numbers in cases where they don’t divide exactly.
24. Why do some reports display only the video ID, or why do some videos not appear at all?
If there are no views for a video during a period, there will not be extensive data on it in the report (e.g. just the video ID and nothing else). If no data is downloaded at all (i.e. not even image data), then the video will not appear in the report.
25. Should the Analytics module and the Analytics API give me identical data for the same date range?
Yes, but they may be different if you are comparing data that is relatively recent, and you obtain data from Studio and the API at different times:
- The data is less than 3 days old. Analytics data less than 3 days old is provisional and subject to change at any time.
- Data for same period is looked at when it was less than 32 days old, and again after it is 32 days old. After 32 days, data is moved to a separate "historical" repository, and at that point we discard some data, especially detailed engagement data. This means calculated fields such as engagement score may change slightly, because the calculation is being made on less granular data.
26. Why are my video views in the Analytics module higher than the amount of views in the Campaign module?
The Analytics & Campaign modules are two separate systems and it should not be expected that the view events are 1:1, as each captures separate use cases.
The Campaign lead form requires a
video_view event to have triggered before it can display a lead form. These
video_view events trigger when a user initiates playback, which is done by having the user manually click the Play button. As a result, even though it may not look like any content has played back, a
video_view has been registered and will appear for your video in the Analytics module.
If you are seeing a higher number of video views in the Analytics module compared to view events in the Campaign module, the most likely reason is that a user was presented your lead form, but did not fill it out to continue through with playback.