Here we aim to make sense of the terms used throughout Analytics and answer any and all questions that you may have. If you have a question that is not covered in this section, feel free to reach out to us and we'll get it updated. 


Terms Explained

Active Sessions

Active Sessions have a 60-second filter applied in an attempt to provide insight into valid and engaged listeners. This is especially important for customers who monetise their online audience as this is the metric advertisers are interested in and rate 'valid audience' at. 

Sessions Started 

Sessions Started have a 1-second filter applied to minimise the data-skewing effects of snooper bots or traffic manipulation. This means that a listener has to remain connected to the stream for at least 1 second before they will be counted as a valid session start.

Total Listening Hours

Total Listening Hours is the total time listeners remained connected and is based on sessions of at least 60 seconds in duration (Active Sessions).

Time Spent Listening

Time Spent Listening is the total time listeners remained connected for at least 1 second (Sessions Started).

Bounce Rate

The Bounce Rate refers to the percentage of listeners not converted from Session Started to Active Sessions. Said more plainly, the Bounce Rate represents listeners who listened for less than 60 seconds but more than 1 second. A high Bounce Rate can be due to a number of causes, some of them listed below:

  • Listener interest;
  • Website accessibility and reliability;
  • A listener's internet connectivity and stability;
  • Stream availability, etc. 

What percentage Bounce Rate is considered to be a 'good' Bounce Rate is subjective to the person viewing the data. There are certain scenarios where a high Bounce Rate might be expected and others where it is not. 

Simple actions you can take to reduce your Bounce Rate percentage include:

  • Reviewing the most popular platforms used by your listeners to access your stream to ensure the listener experience is smooth and without unexpected errors; and
  • Ensuring you are using the correct load-balanced listen-links provided by the Support Team to distribute your stream.

Session Peak

Session Peak refers to the maximum number of listeners connected at the same time. When reviewing this data over a longer time period, for example, a week, the Session Peak will refer to a single Session Peak observed over that week. No filters are applied to Session Peaks. 

Average Time Spent Listening

Average Time Spent Listening is based on the Total Listening Hours and the number of Active Sessions observed. 

Unique Users

Unique Users refers to listeners accessing the stream from a unique IP address. Generally speaking, people in the same office block or household use the same IP address as they are on the same network and will count as a single Unique User. Listeners who are travelling between networks will see their IP address change as they move through a city, for example, and each new IP address will register as an additional Unique User. Ip addresses are assigned by Internet Service Providers and SharpStream has no control over this assignation. 


How can I grant additional team members access to Analytics?

To get more of your team members using Analytics, just let the Customer Success Team know. We will need to know their name, surname and email address to set them up. 

How can I change my timezone?

To change the timezone associated with your profile, select the headshot at the top right of your screen and select 'Settings'. Under 'User Settings', click on the dropdown to open a list of available timezones. Find the timezone you need and select it to apply. Now click 'Save' and the changes will be applied immediately.

Why is the timezone on the dashboard graph different to my timezone?

The date range specified is based on the timezone selected under your Profile Settings. However, the system runs on the UTC timezone and as such the time period displayed on the graph axis will be in UTC. For example, stats for Dayparts between the hours of 6 am UTC +2 and 9 am UTC +2 will display in the graph on the Dashboard as 4 am UTC to 7 am UTC. Hovering over the graph will display the time in your timezone.

How can I view stats for each of my individual audio shows?

You can specify dayparts to show stats data for certain times of the day over the date range you specified. For example, if you want to track stats for the breakfast show that airs between 6 am and 9 am, you can create a daypart for just that. 

Why is there a difference between Unique Users summed weekly for January and Unique Users for January as a month?

The concept of unique listeners involves counting one particular listener, identified by the IP address + user agent, only once for any period of time.

With that in mind, if I were to listen to a station for 7 days in a row, a daily report would identify me as a unique listener for each of those 7 days. But when you would generate a report for that entire week (or month or any period of time), that weekly report would count all my sessions as one single unique listening session, not 7. Because those are not 7 distinct listeners over the course of a week, but rather a single one.

In other words, for any period of time, we are counting distinct listeners just once. If the same listener tuned in on multiple days, as long as their IP address and user agent remained the same, they would always be counted as the same listener and would generate one single unique listening session.

In Email Reports (Beta), why are TLH, TSL, Session Duration and Active Session Duration so different?

The TLH is not based on a formula but rather a count on the relevant date. The different metrics are explained below:

TLH: Session duration active more than 60 seconds intersected with the selected interval for reporting

TSL: Session duration crossing the selected interval for reporting

Session Duration: The total duration of a session that started in the selected interval for reporting

Active session duration: The total duration of a session active for more than 60 seconds that started in the selected interval for reporting

Below is an example to illustrate how these are working and what values are expected :
If we take these 3 listener session examples and from them determine the TLH, TLS, SS, and AS in a particular day, for the time period between 12:00 to 12:15:

Session NameStart TimeEnd TimeTotal Duration
11:58:0012:05:007 minutes
session_B12:03:0012:03:1010 seconds
12:05:0012:20:0015 minutes
For TLH :
From session_A we only count 5 minutes, because that’s the intersected time with our interval ( 12:00 to 12:15)
From session_B we don’t count anything because the duration is lower than 60 seconds.
From session_C we only count 10 minutes, because that’s the intersected time with our interval ( 12:00 to 12:15)

For TSL:
From session_A we count 5 minutes
From session_B we count 10 seconds
From session_C we count 10 m

For Session Duration:
From session_A we don’t count anything because it didn’t start in the selected interval 12:00 and 12:15
From session_B we count 10 seconds
From session_C we count 15 minutes

For Active session duration:
From session_A we don’t count anything ( outside of the selected interval)
From session_B we don’t count anything because it is under 60 seconds
From session_C we count 15 minutes


If your question hasn't been answered, feel free to get in touch! We'll answer your question and add it here to help future users.