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 {{ site.product_short }} Studio.
Yes. The analytics reports have links that can be used to download the report data to .csv and .xlsx files.
Normally, the close-to-real-time data is delayed approximately 15 minutes. That time may vary depending on the volume of data currently being received by the data collection system, however, and in some cases the delay may be up to 3 hours.
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.
There is a Reference ID field available as a video property that you can use to map your internal id to videos in {{ site.product_short }}. 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.
No. A video view is counted only after the main content starts playing.
The ability to filter out IP address ranges is not available at this time.
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.
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.
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.
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.
Yes. The Performance Report offers the ability to view video analytics by display domain.
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).
The number of unique viewers can be seen in the Performance Report.
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.
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:
For more details on how we calculate video engagement, watch the training video Calculating Video Engagement.
There are a couple of factors which can cause the discrepancy in the two numbers:
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:
reconciled data, since the data will all be historical.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.
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.
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 displaying a video ID or name.
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.
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.
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.
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.
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 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.