Webcast Explore

Prev Next

Webcast Explore makes it easy to create filtered audience reports across a variety of dimensions. For example, you can view a station's audience split by day of the week and device family, or a station's audience split by device family and day of the week. The data for both is the same, but the way it's presented is different. You can include up to three splits in a report, in any order. You can also export your reports to an Excel file.

The Webcast Explore user interface is responsive and easy to use. The descriptions below will help you get started, but the best thing to do is navigate through the application, seeing how the various elements work together to create insightful reports that you create according to your needs and interests.

Overview of the Webcast Explore interface

  1. Query Builder.
  2. Selection Management area.
  3. Report.
ItemDescription

Main Menu

The main menu contains all of the related tools that you have access to, such as Webcast Metrics, Podcast Metrics, and TAP Explore (if they are part of your product suite with Triton Digital).

Query Builder

This is where you build and run your Webcast Explore queries.

Selection Management Area

When you click a filter or the date range the Selection Management area opens where you can select the exact item(s) you wish to include in the report. Use the drop-down menu to select Dimensions.

Report

This is where your report appears.

Creating Reports with the Query Builder

The basic steps for creating a report in Webcast Explore are:

  1. In the Query Builder, choose your filters (minimum: publisher, date range, and day part).
  2. Build out your splits by selecting one or more dimensions (up to six).
  3. Run the report to see it in the report area.
  4. (Optional) Export the report to an Excel (.xlsx) file.

Choosing Filters

Filters determine what data is included in your report. You must include at least one publisher/group/station a Date Range, and a Daypart selection. Other filters are optional.

  • Click the first filter button to open the Selection Management Area to select the publisher/group/station. You can select multiple items of the same type, such as multiple groups from the same publisher, or multiple stations within the same group. You cannot intermix, such a choosing stations from different publishers or stations from different groups.
  • Click the current date range selection to open the Selection Management Area to change the date range.
  • The default daypart selection is Daypart - All Times; to select a specific daypart, click the selected daypart and choose a daypart from the list that appears in the Selection Management Area.
  • The filters list is a subset of the Dimensions list. See Available Dimensions for filter/dimension definitions.
  • Click Add new to add one or more additional filters. If you add no additional filters, the charts displayed are for all dimensions for the selected publisher, group, or station and date range. Otherwise, the charts show only the filtered data.

Choosing a Date Range

Webcast Explore requires a date range. When you click the date range indicator the Date Range panel appears, where you can choose a range such as "Last 7 Days" or "Last Week," or specify a custom range. Click Apply or Apply and Run to apply the date range.

The date range and time dimension settings in TAP and Webcast Metrics are based on station timezone. Those settings in TAP Explore, TAP Affidavits, Podcast Explore, and Lineup Explore are based on UTC.

  1. Click the Date Range indicator...
  2. ...the Date Range panel appears.
  3. Select a date range preset or a custom range.
  4. Click "Apply" or "Apply and Run."

Date range definitions

Preset

Definition

Last Day

The last day for which there is data. Due to the way data is processed, this means today minus four days. (E.g., if today is September 27, "Last Day" is September 23.)

Last Full Day

The last day for which there is full data. Due to the way data is processed, this means today minus nine days.(E.g., if today is September 27, "Last Full Day" is September 18.)

Last 7 Days

The seven days preceding the last day for which there is data.

Last Week

The calendar week preceding the last day for which there is data.

Last 30 Days

The 30 days preceding the last day for which there is data.

Last Month

The calendar month preceding the last day for which there is data.

Last 90 Days

The 90 days preceding the last day for which there is data.

Standard and Custom Dayparts

The default daypart selection is Daypart - All Times. To select a specific standard daypart, click the current daypart and choose a daypart from the Standard list that appears in the Selection Management Area. (You can select only one daypart; if no dayparts are selected, all dayparts ("Dayparts - All Times") are included.)

To revert to Daypart - All Times, click the "x" on the selected daypart in the Selection Management Area.

To create a custom daypart, select the Custom tab in the Selection Management Area and define the start and end days, and the start and end times.

To revert to Daypart - All Times, click the "x" on the selected daypart in the Selection Management Area.

For more information, see the usage notes, below.

Custom Daypart Usage Notes
  • Remember that reports are timezone normalized according to the criteria outlined here.
  • Select a start day, end day, start time, and end time. The daypart you define is shown in the field at the bottom of the Custom dayparts panel.
  • You cannot mix different times on different days.
  • Important: the date range filter outranks the daypart filter. If, for example, you create a custom daypart that crosses the midnight date change hour (such as a four hour block from 10PM to 2AM), and you run a report that includes that filter, the data for each day is divided according to the date, not the daypart. More importantly, the daypart is only included if both its start time and end time are within the defined date range.
     In other words, on the first day of the date range, any daypart that started on the previous day is not included. Similarly, on the last day of the date range, any daypart that ends on the next day is not included. See the case study below for an example.
    • Case study: you create a custom daypart for Monday to Sunday (all days) from 10PM to 2AM. You then run a report for Tuesday, Wednesday, and Thursday. Your report will include:
      • Two hours for Tuesday (10:00PM to midnight; the previous midnight to 2:00AM half-daypart is not included because its start date is on Monday).
      • Four hours for Wednesday (midnight to 2:00AM, plus 10:00PM to midnight; this is actually two half-dayparts).
      • Two hours for Thursday (midnight to 2:00AM; the ending 10:00PM to midnight half-daypart is not included because its end date is on Friday).

  1. 10p-2a daypart (blue bars)
  2. Tuesday to Thursday reporting date range.
  3. This daypart is not included because the daypart's Start Time is outside of the reporting date range.
  4. Half of this daypart is included for "Tuesday."
  5. Two half dayparts are included for "Wednesday."
  6. Half of this daypart is included for "Thursday."
  7. This daypart is not included because the daypart's End Time is outside of the reporting date range.

Choosing Dimensions

Dimensions determine how the data is displayed. You must include at least one Dimension and a maximum of six. Click the Dimensions drop-down menu to add or remove dimensions. Dimensions are added in the order in which you select them. To re-order, un-select them in the drop-down, then re-select them in the order you prefer.

Available Dimensions

Click to view the list of available dimensions.
DimensionDescription

City

The city of the listener.

Country

The country of the listener.

DMA

The listener's DMA (Designated Market Area). Only applicable in the U.S.

Date Hour

Shows the metrics for each hour within the selected date range.

Day

Split metrics by date.

Device

The listener's actual device, such as an iPad or Android device. (See note, below.*)

Device URL Param

The device that is passed in the URL query in the dev or devicename parameter.

Device Family

The listener's device family, such as "Mobile Device" or "Smart Speaker." (See note, below.*)

Distributor

The distributor that is passed in the URL query in the dist parameter.

Group

The publishing group.

Hour of Day

Literally, the hour of the day. When used on its own it provides a breakdown for each hour within the filtered dates and dayparts.

Log Type

The type of logs that are used as the source of the metrics data.

Month

Split the metrics by the calendar month.

Mount Name

The streaming mount name as specified in the Triton Streaming Console. Not available for all publishers; this is intended to be used by publishers who are accustomed to seeing Mount Name as a dimension in the former Live Analytics tool from the Triton Streaming Console.

Platform

The platform of the listener's player, such as "desktop," "mobileapp," or "smartspeaker." (See note, below.*)

Player

The listener's specific player, such as "iTunes" or "Stitcher." (See note, below.*)

Player Family

The listener's player family, such as "Podcast Player" or "Web Player." (See note, below.*)

Player URL Param

The player that is passed in the URL query in the tgt or ps or pname parameter.

Publisher

The publisher.

Radio Format

The Radio Formats dimension only reports the formats that have been configured for your stations; if you have not configured any formats, nothing will be reported. If you have not already done so, please submit your stations' radio formats to Triton Digital now. Be sure to include the station names exactly as they appear in Streaming Metrics! For details on how to submit your stations' Radio Formats, see this knowledgebase article in the Triton Digital Support Center.

Region

The geographical region of the listener (such as the state or province). Not all countries have defined regions.

Source Param

The source that is passed in the URL query in the src or ss parameter, such as described in the "Required and Optional Fields in the Log Lines" requirements table.

Time Shifted

Whether or not the reported events took place during a time shift. Filter options are True and False. True is only available to publishers using the Triton Timeshift Radio feature.

Station

The station name.

Station ID

Similar to Station but based on the internal station ID instead of the station name. The internal Station ID is a stable identifier for the station that does not change over time, even if you change the name of station. This is useful for long-term analysis, because you can create reports that cover time periods that span name changes.

Week

Split the metrics by week (Monday to Sunday).

* Note:
Dimensions that originate from the listener's user agent might include some variability because user agents do not always return an exact match (i.e., a particular device or player might go by two or more different names). Note that Moblie - Web or App is used for user agents that are known to be mobile but it is unclear if they are web-based or app-based.
Also note: in the Player dimension, "iTunes" refers to the iTunes desktop app; podcast downloads via mobile iTunes is reported as "iOS unspecified App."

Sorting Reports

You can sort the columns in Webcast Explore reports by clicking on the column header. The arrows show if the sort order is ascending or descending, and the sorted column appears lightly shaded for easy visibility. Click again to sort in the other direction.

Be aware of the following usage notes when sorting reports:

  • Sorting works essentially the same way in all Explore tools. There might be slight differences (such as the default sort column) but in general the same principles apply to all.
  • On-screen reports are limited to 500 lines. If the report you generate contains fewer than the maximum, then resorting is immediate because the sort is based on the data in memory. However, if your report contains more than the display maximum (and therefore some rows are truncated), sorting refreshes the query to ensure your sort is based on all available data and not just what is displayed.
  • AAS is is a special case because of how it is calculated. As a result, if you sort an on-screen report that exceeds the  500 line limit, Explore refreshes the query but sorts the report by TLH. This also happens if you export a report that is sorted by AAS. (A notice briefly appears at the top of the screen.)
  • When you sort a report and the save the query, the saved query remembers the sort order.

Saving and Scheduling Queries

Query ID and Metrics API

You can save and retrieve queries in Webcast Explore, Podcast Explore, Lineup Explore, TAP Explore, and TAP Affidavit. Every saved query has a query ID that you can use to send the resulting data to your business intelligence (BI) applications via the Triton Metrics API.

Important!
The Triton Metrics API can only access queries that were saved by the same user who created the queries. Be sure to log in with your Triton Metrics API access username before saving queries, and when you want to retrieve query IDs and use the API. For more information, see Using the Query ID and Metrics API.