Data Reporting

Prev Next

Whether using the listener tracking method or the CDN log file method, Triton Digital obtains log files for processing. Triton Digital’s log processor system transforms the various log files and formats into a single Triton Digital processing format prior to further processing. To reduce the potential for excluding data due to delays at the CDN in posting the log files for Triton Digital’s retrieval, and to provide reporting on longer sessions, Triton Digital processes log files four days in arrears.

During the initial log processing and transformation, an audit table is populated with information on logs retrieved, logs processed, and errors. Errors include: (a) situations where a compressed log file cannot be uncompressed, (b) invalid data, (c) any transform failures. In addition to being logged in the audit table as an error, these log files are removed from processing and held for manual intervention.

Additionally, streaming sessions that contain invalid or corrupted log data or are less than one minute in length are removed from processing. Triton Digital employs a deduplication process that ensures that duplicate records are rejected and not used for reporting. When log files are provided by the CDN, the deduplication process occurs when the file is uploaded from the CDN’s server. If the file already exists in Triton Digital’s local folder, it will be ignored. When data collection is performed through the listener tracking method, any redundant sessions are stripped out before being inserted in the final database table used by Webcast Metrics.

Once the data is processed, filtered, and aggregated, Webcast Metrics is updated, and stations may begin to review reports related to their streams.

Metrics Definitions

Webcast Metrics Reported Metrics Definitions

The following metrics are reported to clients with the Webcast Metrics web-based user interface at the publisher, group and station level. The Webcast Metrics reported metrics are calculated from sessions converted to the stations’ time zone.

  • Session Starts (SS): The number of sessions that were started in the reported period, after the application of Triton Digital’s general invalid traffic filtration techniques.
  • Active Sessions (AS Gross): The total number of sessions with any duration in the reported period, regardless of whether the session started in the period. This metric includes sessions that may subsequently be removed by Triton Digital’s general invalid traffic filtration techniques.
  • Active Sessions (AS) (Net): The total number of sessions with any duration in the reported period, regardless of whether the session started in the period, after the application of Triton Digital’s general invalid traffic filtration techniques.
  • Average Active Sessions (AAS): The average number of concurrent sessions that were active during the reported period, after the application of Triton Digital’s general invalid traffic filtration techniques. Calculated as Total Listening Hours (TLH) (net) divided by the number of hours in the reported period.
  • Total Listening Hours (TLH Gross): The total number of hours listened to in the reported period from active sessions. This metric includes the duration for sessions that may subsequently be removed by Triton Digital’s general invalid traffic filtration techniques.
  • Total Listening Hours (TLH) (Net): The total number of hours listened to in the reported period from active sessions, after the application of Triton Digital’s general invalid traffic filtration techniques.
  • Average Time Spent Listening (ATSL): The average number of hours for each active session in the reported period, after the application of Triton Digital’s general invalid traffic filtration techniques. Calculated as Total Listening Hours (TLH) (Net) divided by Active Sessions (AS) (Net).
  • CUME: The cumulative number of unique listening agents/identifiers with at least one active session in the reported period, after the application of Triton Digital’s general invalid traffic filtration techniques. Triton Digital uses a combination of unique IP address/user agent, and publisher-supplied unique user ID (VID) to determine CUME. Note, the CUME metrics cannot be summed to create an aggregate. That is, you cannot determine the CUME of a group by summing the CUME of the component stations. This metric is accredited only when the Listener Tracking methodology is employed, and if the publisher provides a unique user ID (VID).

Global Ranker Reported Metrics Definitions

The Global Ranker presents the following metrics for each of the top measured publishers, ranked by Average Active Sessions (AAS). The Global Ranker metrics are calculated from sessions converted to the listeners’ location time zone.

  • Average Active Sessions (AAS): The average number of concurrent sessions that were active during the reported period, after the application of Triton Digital’s general invalid traffic filtration techniques. Calculated as Total listening hours (TLH) (Net) divided by the number of hours in the reported period.
  • Session Starts (SS) (Net): The number of sessions that were started in the reported period, after the application of Triton Digital’s general invalid traffic filtration techniques.
  • Average Time Spent Listening (ATSL): The average number of hours for each active session in the reported period, after the application of Triton Digital’s general invalid traffic filtration techniques. Calculated as Total Listening Hours (TLH) (Net) divided by Active Sessions (AS) (Net).

In accordance with the Media Rating Council’s Invalid Traffic Guidelines, the Global Ranker discloses gross digital audio activity versus net measured digital audio activity. This is represented in Total Listening Hours (TLH) and Active Sessions (AS). The following metrics are disclosed in the monthly Global Ranker for the respective reported daypart as an aggregate of TLH and AS across the top measured publishers:

  • Gross Total Listening Hours (TLH gross): The total number of hours listened to in the reported period from active sessions. This metric includes the duration for sessions that may subsequently be removed by Triton Digital’s general invalid traffic filtration techniques.
  • Net Total Listening Hours (TLH net): The total number of hours listened to in the reported period from active sessions, after the application of Triton Digital’s general invalid traffic filtration techniques.
  • Gross Active Sessions (AS gross): The total number of sessions with any duration in the reported period, regardless of whether the session started in the period. This metric includes sessions that may subsequently be removed by Triton Digital’s general invalid traffic filtration techniques.
  • Net Active Sessions (AS net): The total number of sessions with any duration in the reported period, regardless of whether the session started in the period, after the application of Triton Digital’s general invalid traffic filtration techniques.
  • % Filtered Total Listening Hours: The total number of hours listened to in the reported period from invalid sessions that were excluded as a result of Triton Digital’s general invalid traffic filtration techniques expressed as a percentage of the total listening hours.
  • % Filtered Active Sessions: The total number of invalid sessions in the reported period that were excluded as a result of Triton Digital’s general invalid traffic filtration techniques expressed as a percentage of the total active sessions.

Webcast Metrics Local Reported Metrics Definitions

The following metrics are presented for Webcast Metrics Local through a report generated application, accessed via a web-based user interface. The Webcast Metrics Local reported metrics are calculated from sessions converted to the listeners’ location time zone.

  • Active Sessions (AS Gross): The total number of sessions with any duration in the reported period, regardless of whether the session started in the period. This metric includes sessions that may subsequently be removed by Triton Digital’s general invalid traffic filtration techniques.
  • Active Sessions (AS) (net): The total number of sessions with any duration in the reported period, regardless of whether the session started in the period, after the application of Triton Digital’s general invalid traffic filtration techniques.  
  • Total Listening Hours (TLH Gross): The total number of hours listened to in the reported period from active sessions. This metric includes sessions that may subsequently be removed by Triton Digital’s general invalid traffic filtration techniques.
  • Total Listening Hours (TLH) (net): The total number of hours listened to in the reported period from active sessions, after the application of Triton Digital’s general invalid traffic filtration techniques.
  • ACS-QH (Average Connected Streams Quarter Hour): The average of connected active audio streams after the application of Triton Digital’s general invalid traffic filtration techniques, with attributed audience for a specific demographic category to the stream, stated on the basis of average minute within the reported daypart (based on duration weighting at the second level). This metric is applicable to streams with dynamic content and dynamic advertising. This is generally a metric used for planning advertising campaigns and excludes “ad free” or otherwise non-ad-supported content.
  • ACS-QH RTG (ACS Rating Quarter Hour): The ACS-QH audience expressed as a percentage within a specified market demographic. This metric is expressed as a percentage and is calculated with the following formula: (ACS-QH / Population) * 100.
  • CUME: The cumulative number of unique (unduplicated) listeners active for at least five minutes within the reported period, after the application of Triton Digital’s general invalid traffic filtration techniques. CUME is calculated from the publisher-supplied unique user ID or user registration ID (VID).
  • CUME Rating (CUME RTG): Unique Listeners within the specified MSA, demographic and day-part expressed as a percentage of the MSA demographic population, after the application of Triton Digital’s general invalid traffic filtration techniques.

[CUME / MSA Population] * 100 = CUME Rating%

Calculation Granularity

All time-based calculations are based in whole seconds and expressed in hours/minutes or hours/portion of hour.

Report Parameters

Webcast Metrics Report Format

Webcast Metrics reported metrics are available by hour, calendar day, week (Monday-Sunday) and month by all days/times.  The client may select an alternative reported daypart (Mon-Sun 6a-Midnight, Mon-Fri 6a-10a, Mon-Fri 10a-3p, Mon-Fri 3p-7p, Mon-Fri 6a-7p, Sat-Sun 10a-7p or Mon-Fri 7p-Midnight) or range of sequential calendar days within the reporting UI. The client may further select to view the aggregated metrics across platforms (All, Desktop, Mobile Web, Mobile App, Smart Speaker and Other). The client can also display the report onscreen or export the report as .csv or Excel formats. Only data related to the publisher’s own streams are accessible at the publisher, group or station level.

Global Ranker Report Format

Global Ranker metrics are produced in static reports for the calendar month across the following dayparts: Mon-Fri 6a-8p, and Mon-Sun 6a-Midnight. These reports are produced as a PDF and downloadable from Triton Digital’s website (public access) and emailed to subscribed users.

Webcast Metrics Local Report Format

Webcast Metrics Local metrics are produced as static reports (downloadable, pre-generated PDF version) or dynamic, customizable reports (accessible through an interactive report generator) from data related to the publisher’s own streams.

Static Reports

Clients access the static reports in the report repository of the Webcast Metrics Local user interface (The Console). The reports are generated on a monthly schedule for a reporting period based on a 13-month year, corresponding to existing broadcast reporting periods. The static reports are provided for predetermined local markets (MSA level), Network Radio (national level) and Key Markets (i.e., top 10 markets by population), and aggregated by demographics (age groups – 18-34, 18-49 and 25-54, total, and/or gender – Male and Female) and daypart.  

The Network Radio report provides national level ACS-QH and CUME based on gender and in total (all), while the Key Markets and market reports provide ACS-QH Rating and CUME Rating based on MSA population. The dayparts reported are Monday-Sunday 6a-Midnight for the Network Radio report, and Monday-Friday 6a-7p and Monday-Sunday 6a-Midnight for the Key Markets and market reports.

Dynamic Reports

Clients interact with Webcast Metrics Local user interface to generate customizable reports based on market group (Network, Top 10 Markets, Top 50 Markets, Top 100 markets, Top 10 DMAs, Top 50 DMAs or Top 100 DMAs), local market or DMA, age group (13+, 13-17, 18-24, 18-34, 18-49, 21-34-, 21-49, 21-54, 25-34, 25-49, 25-54, 35-44, 35-64, 50+, and 65+) and daypart (Monday-Sunday 6a-Midnight, Monday-Friday 6a-10a, Monday-Friday 10a-3p, Monday-Friday 3p-7p, Monday-Friday 6a-7p, Monday-Friday 7p-Midnight, Saturday-Sunday 10a-7p and All days/times). The data is available based on the additional section of either calendar month or a three-month average (based on rolling calendar months). The data is presented by gender (male or female) and in total (or all, which also includes users with NULL or blank gender).

The customizable reports are outputted as a HTML report within the Webcast Metric Local user interface or a downloadable PDF report.

Preliminary and Finalized Reports

Webcast Metric data is initially processed on a four- and nine-day lag for daily, weekly and monthly reporting. Webcast Metrics reports are considered preliminary for 30 days after the end of the reported month, after which they are considered final data unless otherwise noted. Webcast Metrics Local and Global Ranker metrics are considered final upon release unless otherwise noted.

Time Zone Normalization and Geolocation Procedures

Webcast Metrics data is reported based on Station Time Zone normalization procedures. Webcast Metrics Local and Global Ranker metrics are reported based on Listener Time Zone normalization procedures.

Station Time Zone Normalization

Digital audio measurement data is collected in UTC time and then converted to the daypart times available within the Webcast Metrics user interface. Daypart reporting within the interface is based on the location (i.e., time zone) of the stations, regardless of where you are and what time zone you are in. If the report generated is at the publisher or publishing group level, and includes stations across more than one time zone, the data is aggregated for the daypart of each station’s respective time zone.  For example, if a report is selected for the daypart “Mon-Fri 3p-7p”, the report will include aggregated data from the “Monday-Friday, 3PM-7PM” daypart at the locations of the stations. This is referred to as “Station Time Zone Normalized”.

Listener Time Zone Normalization

Sessions aggregated and reported for Global Ranker are converted from UTC to the listener’s location time zone for reporting. This is referred to as “Listener Time Zone Normalized”. In order to assign the listener time zone, Triton Digital utilizes information provided by (1) the listener (user provided postal code, or if unavailable, user provided country code) or (2) a geolocation vendor derived from the ordination of the IP addresses (postal code based on IP address, or if unavailable, the location id assigned by the geolocation vendor). User provided data is prioritized over geolocation vendor supplied data.

If these data points are not provided by the geolocation vendor, and Triton Digital is unable to determine the user’s location based on the above data points, the time zone is normalized to the Central Time for USA digital audio activity and UTC for all other activity.

Utilizing geolocation data based on IP address has certain inherent limitations due to potential differences between the user’s physical location and the location the digitally connect to the internet. For example, users behind a proxy connection may be physically located in a different geography than the proxy connection to the internet, which is generally the location associated with the IP address. Additional limitations exist in situations where the geolocation vendor is unable to determine the location information associated with the streaming session. These situations are not unique to Triton Digital. 

Webcast Metrics Local Audience Reporting

Collecting data directly from client applications, Webcast Metrics Local uses registrant’s five-digit zip code, year of birth and gender to determine listeners’ MSA location and demographics for audience report breakouts.  

Webcast Metrics Local Market Definitions

For a detailed list of Triton Digital Metro Streaming Areas definition by zip code, please refer to the following file:

https://tritondigitalv3.blob.core.windows.net/media/Default/Other/ZipByTritonMSA.pdf

Hyping/Failure

Where applicable, Triton Digital shall footnote in the published Global Ranker situations where there are known technical difficulties or hyping actions (i.e., power failure lasting multiple days, a natural disaster, stations offering cash incentives for listening for a certain period of time, etc.).

Data Confidentiality

Triton Digital does not share publisher nor station level Webcast Metrics/Webcast Metrics Local metrics between publishers.

Aggregated publisher metrics may be shared publicly through the release of the Global Ranker.  However, Reported companies must opt-in for the public release of their digital audio metrics. A release agreement is maintained in these instances.

Quality Control

Potential clients undergo initial business partner qualification procedures prior to access to Triton Digital’s services and therefore reported metrics.

Triton Digital has relationships with a number of business partners, namely geolocation vendors, CDNs and industry organizations (supply invalid traffic filtration lists), that are considered material to our measurement services.

Triton Digital conducts publisher audits on all new Webcast Metrics clients in order to ensure CDNs are not manipulating data, and that we are reporting valid metrics.

Triton Digital also conducts periodic publisher audits on existing Webcast Metrics clients to ensure measurement implementations and data collection methodologies continue to operate within the minimum technical requirements needed for measurement and reporting.

Furthermore, daily, weekly and monthly automated and manual data reviews are completed to ensure the accuracy and completeness of the reported data.

Reissued Data and Notifications

Triton Digital will reissue data whenever an error or omission is found that affects any reported metric, for any station, by equal to or more than 5%, or would lead to a change in the ranking of affected station(s);

Triton Digital will communicate the above error or modification to clients via the Webcast Metrics and Webcast Metrics Local interface or via the Triton Digital website if it affects one of our public rankers.

As it pertains to any future changes in methodology that may affect the overall measurement and reporting of reported metrics (i.e., AAS, TLH, CUME, ACS-QH, AS, SS, and ATSL), client will be notified via the Contact database (email).

Data Retention

As it relates to the in-scope services of this DOM, Triton Digital retains the detailed records of the sessions, and the aggregated reports, for a minimum of 13 months.