22 9 / 2012
Spreaker app: issues with iOS6
Some users reported us issues with iOS6, the latest version of the Apple operating sistems for iPhone, iPad and iPod touch. We’re working hard on it in order to release an updated version as soon as possible.
In the meanwhile, continue reporting us issues by writing an email to: email@example.com
Do you want to become a beta tester and receive all bleeding edge versions of our iOS applicaton without waiting the official release in the App Store? Drop us an email to the same address above!
Sorry for the inconvenience,
The Spreaker team
13 8 / 2012
How Spreaker Tracks Listening Statistics
UPDATED on December 24th, 2012
I recently joined some discussions with our users, where they asked how statistics work in details. I understood there’s a bit of chaos about what people thinks how we calculate statistics and it revealed the need of a detailed and technical explanation.
Listening statistics is the primary metric for a podcaster. Like a blogger measures its success counting the number of times an article gets read, a podcaster wants to know how many people listens to his audio contents.
Tracking accurate statistics is not an easy task, but we try to our best to be as most accurate as we can. In this article, I’m going to explain in details how statistics are tracked at Spreaker, showing strengths and weaknesses, and exploding some myths and wrong information you can find on the net.
How we track statistics
Listening statistics are tracked on the streaming servers. They’re not tracked client-side in the player and this approch gives us two main benefits:
- we are able to track listenings from third party players that are not under our control and
- it’s much more difficult to track fake plays.
This means that we track every single play whose audio is served by our streaming infrastructure and we’re unable to track statistics for contents created with Spreaker and uploaded to other platforms. For instance, if you enable the sharing of your episodes on Soundcloud, we upload your mp3 file to Soundcloud and Soundcloud users listen the mp3 downloaded from their servers, so that we’re unable to track that plays.
To summarize, Spreaker do tracks statistics for listenings from:
- Spreaker website (desktop and mobile)
- Spreaker embedded players (including Facebook, Tumblr, your own blog or site)
- Spreaker mobile apps (iOS and Android)
- Third party services and apps that rely on Spreaker streaming servers (including iTunes and TuneIn)
Spreaker do not tracks statistics from:
Downloads are counted separately from listenings just because a user can download one your podcasts once and listen to it several times.
Because we cannot track every single listening of a downloaded podcast, if a user downloads a podcast instead of listening to it, we increment the “Total downloads” counter instead of the “Total plays” counter.
Difference between Total plays and Unique listeners
Total plays is the number of times your listeners have pressed “play” button on your episodes and listened at least few seconds of audio.
Unique listeners is the number of different (unique) users have listened to your episodes. This number is always less or at most equal to total plays.
How unique listeners are calculated
Tracking unique listeners is a bit tricky because we have to identify who is the listener, in order to correlate together two different plays from the same person. This is a common problem that most of all internet related statistics services have (ie. Google Analytics for website).
To track unique listeners we associate a listener id to each play. This listener identifier is calculated as follow:
- if the user is logged in to Spreaker, we use its unique user id (high accuracy)
- if the user is not logged in to Spreaker or the user is using a third party player (ie. iTunes), we calculate an hash with several information, including the IP address and browser user agent (low accuracy)
After that we calculate the number of unique listeners in a specific time range (ie. daily or monthly unique users) calculating the number of unique ids among all plays.
Are statistics updated real-time?
The short answer is not all statistics.
Calculating statistics is an heavy task and requires a lot of computation. For this reason, we track real-time statistics that simply require an increment (ie. total plays and total downloads), while we periodically calculate the aggregates of other statistics that require a more heavy elaboration (ie. unique users). These aggregates are usually calculated every few hours.
Generally speaking, the statistics shown in public pages are real-time, while private statistics shown in the dashboard are updated every few hours (at most every day).
How are popular contents ranked?
Ranking on Spreaker is designed to pop up contents that had many listeners in the last day and week. The algorithm details are secret and subject to changes, but we can say which are the metrics that we use to calculate it.
Metrics related to ranking (tracked in the last day and week - more is better):
- Number of unique listeners and total plays
- TTSL (total time spent listening)
- Average play length
- Number of followers
- Contents with an image, description, tags, …
Metrics not related to ranking:
- Total number of episodes - it doesn’t matter how many episodes you broadcasted, so that if you’re a new user but you get an huge audience, you can jump to the first position anyway
Permalink 2 notes
01 8 / 2012
YouTube connect: spike of requests!
Yesterday we launched the auto-share on YouTube and in less than 24 hours we got a spike on the requests of connection.
The following graph shows the number of accounts connected to YouTube, compared to Soundcloud and Tumblr. Till now, after Facebook and Twitter, YouTube is the most promising platform where sharing your podcasts!
If you didn’t connected your YouTube account to Spreaker, do it now! It’s just 1 click.
P.S. We internally use statsd+graphite to graph a lot of metrics, from the infrastructure to business. Do you want to know more? Ask an RFC to our operations wizard @alexanderfortin ;)
01 8 / 2012
Spreaker iOS app: +50% in 2 months
Spreaker iOS app is fast growing! Statistics on listeners from the iOS app show an increment of +50% in the last 2 months.
Haven’t you downloaded it, yet? Download it now. It’s free!
20 7 / 2012
Happy Birthday @cedmax (IE7 deprecated)
Today is the birthday of @cedmax our brilliant frontend developer. Last year our gift was removing IE6 from the list of Spreaker supported browsers. Supporting old versions of IE costs us an huge effort and prevent us to introduce cool features (supported by most modern browsers but not on old IE versions).
This year we remove the support of IE7 (currently it’s 1% of our traffic). This means that if you’re using IE7 you should upgrade it immediately or install Google Chrome, in order to continue using Spreaker. IE7 support will be completely dropped on 15th of August 2012.
Happy birthday Ced!
19 7 / 2012
iOS app update waiting for approval
We’ve submitted a new release to the Apple store and we’re now waiting for Apple review and approval. We’ll post again on this topic as soon as the app will be available for download.
19 7 / 2012
The best browser for Spreaker
Spreaker website currently support several browsers, including Firefox, Chrome, Safari, Opera, IE8+ and most mobile browsers (mobile navigation at http://m.spreaker.com).
However, sometimes people asks which is the best browser for Spreaker. Answering this question we should take in account several things, including:
- Features supported (ex. HTML5, CSS3, …)
After 3 years of work on our service, we can say that the best browser for Spreaker is Google Chrome, while the worst is IE (all versions). If you’re using Firefox, Safari or Opera it’s ok for Spreaker, but if you’re using IE we suggest you to try Google Chrome. You will see a much better website than you imagined ;)
Permalink 1 note
17 7 / 2012
Delayed release of iOS app update
Three weeks ago we released Spreaker iOS app 3.0. Some of you have experienced some issues while broadcasting with the brand new deejay console and we worked hard in the last weeks in order to fix everything.
A new update is ready since 10 days, but unfortunately we’re stuck with the slow Apple review process and we’re waiting the app will be published. We’re very sorry for this delay and we hope to get the app to the store as soon as possible.