Amagi Analytics is the platform that helps you make better decisions regarding your programming, content selection and monetization for FAST channels. Amagi ANALYTICS platform has been designed to provide deep insights into attributes that influence business decisions.

The platform gives a comprehensive view of viewership metrics such as unique viewers, number of viewer sessions, average viewing time, total viewership, concurrent viewers, content related metrics and more. It also highlights advertising metrics such as ad breaks, ad requests, responses, total number of ad assets received, impressions, completion rates and ad drops.

· Understand the viewing patterns of your viewers across different regions, device types or streaming platforms, for a particular content asset or a linear channel.

· Make better programming decisions basis performance metrics of different content on the channel at different time slots

· Measure Real-Time performance of your channel using concurrent viewers metrics streamed in real-time

· Measure Monetization performance of your channels with detailed ad metrics

· Download comprehensive data on your FAST channels to integrate with other sources in your BI environment. Use Amagi Analytics API to get programmatic integration with your Analytics tools of choice.

Amagi Analytics uses the data generated by beacons that are inserted into a linear feed by Amagi Thunderstorm (Amagi server side ad insertion offering) . Once a viewer starts watching the stream using the Amagi Thunderstorm endpoint, the periodic beacon urls hit Amagi origins and this way the Viewer is identified. A beacon is inserted every 5 segments for channels on Thunderstorm version 1 and every 3 segments in Thunderstorm version 3. The length of a segment varies by channel and is typically 5 - 6 seconds.

In short, a beacon acts like a heartbeat spaced apart by 15s-30s giving a highly accurate picture of the viewers' watching behavior.

For Ad Analytics, data is generated by Amagi Thunderstorm and Ad- Router.

Viewership Analytics provides a comprehensive view of your channels' and content performance on multiple dimensions. It helps in making critical scheduling and content selection decisions in order to increase viewer engagement.

Viewership details are available at two levels - channel and content asset level. Channel viewership metrics give a view of your channel’s real-time and historic performance. Content Analytics gives visibility into individual asset level performance.

Note : For VOD channels/deliveries, Content Level Analytics is not available

Homepage

Overview Tab

On the overview tab, user can see a bird’s eye view of the performance of all the linear channels. It can be used to further drill down into a specific channel or a timeframe.

The first block titled “Reporting Dimensions” shows the different dimensions on which user can slice and dice the data to arrive at desired insights. One can filter by Channel, device type, region (country, city) etc as seen in the attached screenshot. Each selection made filters the data along those dimensions.

The second block gives the aggregated summary of the different performance metrics as per the selections made in the first “Reporting Dimensions” block for the entire time duration selected.

The block pane that follows gives a visual representation of the performance metrics for the time-interval selected at every point in the time-period selected. For ex, in the snapshot below, one can see the session count for each hour of the selected channel during the last 24 hours (as per time-period selected in “Reporting Dimensions” section)

Concurrent Viewers Tab

Concurrent Viewers gives the user a near real-time view of how many viewers are viewing the channel simultaneously over the recent past. The latest data point is delayed by ~15 min (the right most point on the graph).

A summary of the selected time duration (1 hr, 12 hrs, 24 hrs) can be seen in the Summary Tab. The graph gives data for each 1 min interval for the selected time duration.

Concurrent viewers data can be leveraged to understand real-time performance of content/channel, which channel pulls in how many simultaneous viewers, what is the trend of viewer engagement (ex: are a number of viewers dropping off after some time) etc.

Unique Viewers Tab

The Viewership data in the Overview tab conveys the spread of viewership - how many unique viewers are contributing to the overall viewership minutes/session count for a channel. (to get unique viewers at a content level please refer to the reports section).

Definitions of Viewership Metrics

This section defines the different viewership metrics available in the dashboard/reports/api in Amagi Analytics. The definitions of these metrics can be seen in the portal by hovering over the small i icon beside the metric name.

· Sessions : Total number of sessions (session count). A session is started when we receive a playlist request from the viewer's device. Since beacons are spaced apart by 15-30 seconds, when the viewer continues watching for atleast 15-30 seconds, the session duration gets added to viewership mins.
A session is considered broken if the viewer has not watched the content continuously for about 90 seconds (i.e. we don't receive beacon signals for 90 s). If the viewer changes a channel then the session is terminated immediately.
Note : The beacon spacing is dependent on the Thunderstorm version as well as network and player side delays. Hence the above mentioned numbers are approximate ranges.

· Unique Viewers : Number of unique viewers. A unique viewer is counted based on the unique combination of IP address + User agent string passed by the player of the viewer. To be counted, viewer has to be active for minimum 1 session or 30 seconds. Unique viewers metric is relevant at a channel level only - not across channels (this will imply that same viewer watching two channels across a time period like a day or a month will be counted as 2 unique viewers - 1 on each channel).

Let’s take a few examples to better understand this -

o A viewer is watching the channel on Desktop Chrome browser from a certain IP address and then logs out. If the same viewer with same IP now access the same channel from a different browser or from his/her mobile then viewer gets counted as 2 unique viewers even though its the same viewer

o A viewer watches content on Samsung CTV and then watches again after 2/3 days and his/her IP has been refreshed then still the viewer will be counted as unique even though the device (Samsung CTV) has not changed (retail viewers mostly have dynamic IP addresses)

Note: Unique viewers data across different time intervals such as hour, day, week, month cannot be added up. For Ex: A viewer Joe watches a Channel A from 6:05 am - 6:42 am then the resumes watching from 7:35 am - 8:45 am. (refer to diagram below).

The unique viewers calculation would look like the table below. Note that summation of unique viewers for two sub-time periods, row #1 and row #3, does NOT equal the unique viewers for the total time period in row #4. This is to be expected as per definition of uniqueness.

· Viewership Minutes : Total viewership minutes are calculated as sum of all session durations counted in minutes.

o Ex: 5 unique viewers watched a channel X in the last hour registering 7 sessions (same viewer can disconnect and restart watching after some time hence generating more than 1 session). Let’s say the duration of the 7 sessions was 2 min, 4 min, 10 min, 20 min, 15 min, 27 min, 42 min. Then for Channel X the total Viewership minutes would be 7+2+4+10+20+15+27+42 = 127 min.

· Aggregated Viewers (derived metric) : Aggregated viewers is the total of the unique viewers for each of the time interval selected.

For ex: if user selects “hourly” in the duration section and period as 24 hours (screenshot above), then the aggregated viewers is calculated as : unique viewers in hour 1 + unique viewers in hour 2 ….. + unique viewers in hour 24. This implies that a viewer A watching Channel X for 2 hours during the 24-hour period will be counted as 2 unique viewers and not 1 in “aggregate viewers” metric.
(For unique viewers across time please refer to the unique viewers tab on the left hand navigation pane in the Analytics portal)

· Average Session Duration (derived metric) : Average is calculated as the total viewership minutes divided by total number of sessions. The number shall be shown up to two decimal places.

· Average session count (derived metric) : Calculated as a total session divided by number of days/hours as per selected time interval and time period

· Average number of viewers (derived metric) : Calculated as a number of unique viewers divided by number of days/hours as per selected time interval and time period

· Average viewership minutes (derived metric): Calculated as a total viewership in minutes divided by number of days/hours as per selected time interval and time period

· Average Session per viewer (derived metric): Average session is the total number of sessions divided by total number of unique viewers (a viewer can have multiple watch sessions if they switch-out of the channel and come back again after the minimum time-out of 60s as per the definition of session above).

· Average Session Duration Per Viewer(Minutes): Total Session Duration/Total Unique Viewer

· Concurrent Viewers : Concurrent viewers are those that are watching a particular stream simultaneously at a point in time. This metric is available only at minute level for a time period of past 24 hours. The definition of last 24 hours is always as per UTC timezone and NOT the user’s local time zone.
​Note: The display in the concurrent viewers graphs (time displayed on the horizontal-axis) is currently in India Standard Time (IST) only. This is a known bug and we are working to make an option to make a timezone filter available in the Concurrent Viewers tab.

· Average Concurrent Viewers: Number of viewers watching simultaneously for the past 1/12/24 hours time periods averaged over the time period. (every data point considered for the average is 1 min apart. So for an hour, it is the average of concurrent viewers watching for each of the 60 min data intervals)

· Maximum Concurrent Viewers : Maximum number of simultaneous viewers watching at any given minute during the selected time period

· Minimum Concurrent Viewers : Minimum number of simultaneous viewers watching at any given minute during the selected time period

Different Dimensions available to slice your data

Dimensions are qualitative factors which describe your data ex: the country in which viewing occurred, name of a channel or a content studio etc. These can be used to drill-down into the watch behaviour of your viewer for a specific channel, geography, content title etc.

The following dimensions are available to slice and filter the data -

· Channel

· Time Period

· Time Interval - These are pre-defined standard time intervals such as hour, day, week and month.

· Device Type

· Device Name

· Studio

· Content (asset id) - This is the name and the unique id of the content assets as per the EPG

· Country

· City

· Time-zone - Currently we support UTC, US East and US/Pacific time-zones. Not all timezone options are available in the

Note: Not all filters are currently available on each section/tab. We are continuously adding more filtering options to help our customers get a more granular picture of their ad and viewership performance. Some filters are available only in the Reporting Section and not on the UI.

Ad Analytics section allows a user to see the performance of the ads via different metrics such as ad-opportunities detected, errors/drops, impressions generated etc. Users can slice the ad metrics across different dimension to understand which channel, content, ad-tags are performing well.

Note: Amagi Analytics does not supply ad-targeting/retargeting and CPM related data. A separate access to Springserve portal will be shared with eligible customers as per the Eligibility matrix below.

It is important to understand the kind of monetization arrangement that a channel is deployed in (Inventory vs Revenue Share) as it determines the analytics that will be shown on the Ad Analytics Tab of the product.

Note: The Ad Analytics Tab shows the summary of all the channels that the customer has with Amagi SSAI - inclusive of Inventory Split and Revenue Share. So if an Inventory Share channel is selected using the filters option in the Ad Analytics Tab, it will show up 0s in the ad metrics. However, if there are some revenue share channels also, then the main Ad Analytics tab will show a summary of their Ad Metrics. (screenshot below)

Note: For Revenue share channels, ad analytics tab shows metrics for the entire inventory.

· Total Ad Opportunities Detected : This is the number of viewers that were watching the content during the last 60 seconds of SCTE trigger time when an ad break got detected. So if there are 100 viewers watching the channel when an ad-break comes up then it converts to 100 ad opportunities detected

· Total Ad Requests Sent: The number of Ad-requests that Thunderstorm made to the Ad-network configured. This number will be greater than or equal to Total Ad Opportunities Detected. It can be greater than Ad Opportunities due to fact that we invoke same ad-tag multiple times as per the Waterfall mechanism in Thunderstorm (if the first request does not get a valid response from the servers then subsequent calls are made as per the configuration).

· Total Ad Responses Received : Valid VAST responses received for the ad requests sent by Amagi Thunderstorm

· Total Ad Assets Received : Total Ads received after discounting any of the error metrics (ex: duration mismatch responses where we get an ad asset that is of a different duration than the ad-slot duration).

· Total Impressions Recorded : Number of impressions we fired to ad-network (Impression tracker URL is fired when we serve the first ad-segment of each ad to viewer. So if a viewer starts watching the ad, an impression is recorded. To understand ad completion rates please refer to the Quartile metrics' definitions)

· Average Conversion Rate : This is calculated as Total Ad Assets Received divided by Total Impressions Recorded

Ads Error Related Metrics :

o Ads Dropped Due to Duration mismatch : Ads from the ad-server response having a duration not matching what Amagi SSAI requested.
​Example: We asked ads for 60 seconds, and we get a response containing 2 ads - one of duration 30 seconds and another one 70 seconds. In this case, we drop one ad (of duration 70 seconds) and pick one ad (of duration 30 seconds) only.

o Ads Not Transcoded: For performance and latency reasons, Amagi Thunderstorm does not use an ad asset when it is received for the first time from the server. These are pushed to transcoding, and counted here as Ads not transcoded. These ads will be transcoded in the background by Amagi Thunderstorm and get used during subsequent ad-breaks.

o Invalid Ad Responses : Responses having other errors like invalid VAST XML, encoded/encrypted XMLs, malformed attributes in the XML etc.

o Empty Ad Responses : These are the number of empty VAST responses received from the ad servers

o Users Dropped : From the time an ad-request is received, manifest is prepared and sent back (with ads), viewers may have dropped off the channel. This is calculated by the beaconing mechanism described above.

o Transcoding Failure : Ads dropped due to transcoding engine failures.

o Ads Overflow : There are some miscellaneous reasons for why an ad received might not get inserted in the stream (dropped) which are counted under this error metric. Some of the reasons are -

§ Thunderstorm requires each ad segment of a standardized duration (5 sec) If we receive an ad with a segment of duration 7 seconds, we will pad the ad-segment with filler for 3 seconds to arrive at 2 segments of 5 second duration each (total 10 seconds). So if we receive two ads of 7 seconds and 23 seconds for ad-break of 30 seconds, we will end up dropping one ad (Due to filler padding). This case is counted in this metric.

§ If we receive 2 ads of duration 15 seconds and 20 seconds each for a ad-break duration of 30 seconds, even though both ads were of duration less than duration requested, total duration is greater than ad-break duration. So we dropped one here as we don’t show partial ads to viewer. These dropped ads are also counted in this metric.

· Usable Ads : This is calculated as Total Ad Assets Received - Ads Dropped Due to Duration mismatch - Ads Not Transcoded - Transcoding Failures

· Ad Completion Metrics :

o 25% Completion/ First Quartile: We fire the tracker for 25% quartile when we serve the ad-segment which serves atleast 25% of the total ad content to viewer.

o 50% Completion/ Mid Quartile: We will fire the tracker for 50% quartile when we serve the ad-segment which serves atleast 50% of the ad content to viewer.

o 75% Completion/ Third Quartile : We will fire the tracker for 75% quartile when we serve the ad-segment which serves atleast 75% of the ad content to viewer.

o 100% Completion/ Complete Quartile : We will fire the last tracker for an ad when we serve the last ad-segment to the viewer.

Ad analytics tab also shows a breakdown of the ad metrics at content level.

Amagi Analytics provides comprehensive report generation feature for downloading your data and conducting any further analysis as needed. There is support for creating time-based schedules at which users subscribed to the schedule will get an email for the selected reports.

There are two reporting options available in Amagi Analytics -

1. On Demand: This enables the user to download the data on as-needed basis.

2. Scheduled : This allows the user to get via email, selected reports at a selected frequency.

On-Demand Report Download

On-Demand report functionality enables the user to download data on as-needed basis.

There are two categories of reports that are available -

1. Viewership

2. Ad-Analytics

Viewership reports

Viewership report is for downloading channel/content viewership related data. For different data available for download please refer to the Viewership Metrics section under Product Overview

Time Parameters : This tab allows the user to select -

1. time-interval at which to see the data (the level of drill-down)

2. time-period for which to fetch the data (using the level of drill-down selected in the time-interval parameter)

3. time-zone in which to fetch the data

Example : If one wants to look at the “Daily Unique Viewers for a Channel X for the past 30 days as per the Universal Time-zone” then the selections will be “Daily” in the time-interval parameter, “Last 30 Days” in the Date Range parameter and “Universal” in the time zone parameter.

Content Parameters (Available only if Content Analytics has been opted for by the customer) : This filter set allows the user to

1. download data with content parameters in the report (selecting “all” option adds columns in the report with all the respective available channel names/studio names/content titles )

2. download data for specific channels/studios/content titles

Note: Selecting a time interval of hourly, aggregates content metrics at an hour level, daily aggregates at day level and so on. Some examples to understand this -

1. If a show ABC played 2 times during a day and time-interval has been selected as daily, then the generated report will contain a single entry for the show ABC with the metrics added up for both the runs during the day.

2. A show ABC played 3 times during week 1 and 4 times during week 2. If user downloads a report with Date Range (Time Period) covering week 1 & 2, and ‘Interval’ as weekly, then the generated report will have 2 entries for show ABC - First entry for the 3 runs of the show in week 1 and the second entry for 4 runs of the show in week 2. The Metrics would be a summation of the runs at each week level. Other combinations of ‘Interval’ and ‘Date Range’ will behave in a similar manner.

3. Cumulative option for Interval field : The other 'Interval' options available to the user are pre-fixed to a standard hour/day/week/month. If aggregated data is needed for longer and/or non-standard durations like 10 days or 45 days then user can select the ‘Cumulative' option.
​Cumulative adds together the metrics for all runs of each show (identified by distinct content id) as calculated at daily level. Please note that this does not re-calculate the unique viewers and sessions count across all the runs of the show uniquely for the entire time period selected but uses a summation of the ‘daily’ interval.
Ex: A Show ABC has 1 run per day during a 30-day period for total 30 runs. If user selects ‘cumulative’ option with date range as that 30 day period, then the unique viewers, viewer minutes and sessions count will be sum of the metrics for each of the 30 days.
​

Note: This implies that an hourly time-interval report for the same 30 day period (date-range) may show a different value for the metric when added up than a cumulative report for the same 30 day period. Same analogy will hold for other combinations of time-interval and date range.

Note: Some fields like Studio, Series Name might appear blank if the EPG shared by the customer does not contain that metadata.

Note : For VOD channels/deliveries, Content Level Analytics is not available. Only delivery level analytics are available.

Device Parameters

The device parameters option gives the user an ability to drill into the “device on which content was viewed”.

There are 2 device parameters -

1. Device Type : This is a broad grouping of devices in logical categories like smart tv, mobile phone tablet etc

2. Device Name : This is a sub-classification under the device type such as Amazon Fire TV ( a type of Smart TV) etc

Device parameters are inferred from the “user agent” string passed by the viewers' player.

Note: The “Others” category in the device type is a catch-all bucket. If we receive a response from the viewer’s player where we cannot identify the exact device type or if we receive an erroneous response then it is classified as “Others”

Note: If you have an app and you want to collaborate with Amagi on the right UA string to pass to Thunderstorm to identify viewer metrics accurately for your device , please contact amagi support or your account manager and we will get in touch with you.

Region Parameters

Region parameters are for slicing your viewership data by geography. Country, city level of granularity is provided. Specific countries and cities can be selected to understand the geographic distribution of your viewers.

Data Metrics

User can select various data metrics that they want to download as per the options selected in the Time, Content, Device and Region Parameters. Please refer to the Definition of Viewership Metrics Section for the various metrics available.

Ad-Analytics Reports

Ad Analytics report generation allows the user to download monetization related data. This works in very similar fashion to the analytics reports.

For definitions of the various dimensions and ad metrics please refer to the Product Overview> Ad Analytics section. User can slice their data by multiple parameters like channel, studio, content, device and region.

Note: Ad Analytics reports, unlike viewership reports, can only be downloaded at a granularity of 'daily'. The time periods available are similar to viewership analytics reports.

Scheduling Reports

Scheduling functionality enables users to get specified data report at custom intervals.

The email sent to the user will contain a link for the user to download the data. Since file sizes can be large depending upon the options selected while generating the schedule, and most email services permit relatively small sized attachments (~25 mb max), we do not support attachment of the actual data in the email.

3 types of scheduled reports are available -

1. Viewership

2. Ad Analytics

3. Concurrent Users

All scheduled reports have similar functionality to On-Demand reports. The major difference is the addition of a 'Scheduling Parameters' Tab (in screenshot below) that enables the user to additionally name the schedule, define the frequency at which they get the scheduled report via email and add email recipients.

Users can opt for viewership metrics reports delivered to their email ids (and any other email ids they require) every day/week/month.

There is also an option to download data for ‘cumulative’ period

Note: Please expect a few hours of lag in reports to be delivered to your email inbox esp. for the weekly and monthly reports as data needs to be prepared once the previous time-period gets over (day/week/month).

Ad Analytics scheduled reports work similar to the on-demand reports with the added ability to have it delivered to the user's email inbox at a frequency chosen by the user. Since, ad analytics reports are available at an aggregation of a day only hence the data-interval option is greyed out. Rest of the options/metrics are similar to the Ad-Analytics On-Demand reports.

Concurrent viewer report is available only for the last 24 hours at a granularity of 1 min only - hence report interval and data interval options will be greyed out.

Amagi Analytics enables users to access their data via REST based APIs. All the dimensions, metrics and filters available on the UI / Reports Section can be pulled via API calls using common API tools like Postman, cURL etc.

Please reach out to your customer success manager/account manager for the detailed API Documentation.

The account management section is accessed from the “Account Preferences” tab on the left pane. User can change their password and generate a personal token (which is used for API access).

To add or modify a user to the your Amagi Analytics portal please contact Amagi Support or get in touch with your Customer Success Manager.

Please note that currently User Management is not supported via api. Please contact Amagi support for user related requests.

· I have an idea/feature request for Amagi Analytics
Please do share your ideas. You can create a support ticket with the title “feature request” in Amagi Support OR intimate your account manager/customer success manager. Someone from Product teams will get in touch with you to understand your requirement in more detail.

· I cannot find my channel in the analytics portal
For getting analytics, channel needs to be using Amagi SSAI system - Thunderstorm. If your channel has gone live on Amagi Thunderstorm and you cannot find it on the portal, please raise a ticket with Amagi Support Desk or get in touch with your customer success manager.

· Ad Analytics shows blank for my channel
Please refer to the Ad Analytics sections above. If you are entitled to Ad Analytics a per the matrix covered in the Ad Analytics section of this document, please raise a ticket with Amagi Support Desk or get in touch with your customer success manager.

· I find some data missing/incorrect for my channels on the Analytics Portal
Please raise a support ticket in Amagi Support Desk - https://support.amagi.tv/ with clear description of the issue observed, the expected/correct state according to you, attached CSVs of the data and how you generated that report (metrics, dimensions and filters selected). Our support team will need these details to diagnose the issue and help resolve it.

· Dimension refers to an attribute of a dataset. For example: A dimension can be geographical region, a device, or channel name etc.

· Metric refers to the actual datapoint or the measurable value that is used to understand the performance of the system with respect to a dimension. ex: unique viewers, session count, viewership minutes etc.

· Dynamic vs Static IP Address : When a device is assigned a static IP address, the address does not change over time. Typically companies/organizations have static IP addresses Ex: www.amagi.com. Most devices use dynamic IP addresses, which are assigned by the viewer’s Internet Service Provider (ISP) when they connect to the internet and change over time. The change period varies from ISP to ISP and are dependent upon a number of factors.

· Channel : A Channel name in Amagi Analytics covers a single unique feed going to a platform in a specific region. The general format of the names is CustomerName__ChannelName_DistributionPlatform_DistributionRegion. This implies that a Channel X going to Roku US and the same Channel X going to Samsung US will be two different entities in the Amagi Analytics portal.

· User : A “user” in this document refers to the person using the Amagi Analytics Portal as a customer of Amagi. This is NOT the end viewer watching the content.

· Viewer : A viewer is defined as the person watching the actual channel

· Time Period (or Date Range): Time-period refers to the historic range for which data can be viewed/downloaded at the granularity defined by the time-interval parameter.
Ex: Viewership data at the ‘daily’ granularity for a ‘time-period’ of past 6 months.

· Time-Interval (or Interval or Data Interval) : This is the granularity or the aggregation parameter for the data. Ex: Hourly, Daily, Weekly level data.
Ex: Viewership data for weekly time-interval and for last 2 months (time-period) will show viewership metrics for the last 2 months aggregated( grouped) at a 'week' level i.e. 4*2 = 8 line-items.

To start creating tickets, you will need an account in the service desk. Send an email to the support team requesting for an account creation. Please use your official mail ID to send the request. You can raise a ticket in the service desk to create a login for your colleagues in case you already have an account created. The user will receive an activation link in the email. Activate the account by following the link received in the email. You would have received a detailed Amagi Service Desk User Manual during the onboarding process as well.

Amagi Service Desk URL: https://support.amagi.tv/

Alternatively, to get support please reach out to your Amagi Customer Success Manager or Account Manager. An email introduction would have been made during the onboarding process identifying your customer success manager .