Diagnosing Session-Level Data for a Streaming Service in Seconds

By Laura Shores - July 1, 2020

Take a moment and imagine yourself as a data analyst at a large online streaming service. It’s a highly competitive industry with intense pressure to compete for viewers’ time and attention,  and one that thrives on insights from streaming analytics.

In your day-to-day role, you’re feeling the pain as your streaming service captures an increasing amount of audience data, but you’re on a never-ending “data request hamster wheel.” Given the amount of data captured for every session, it’s impossible to quickly and comprehensively answer these repeated questions from stakeholders.

From working with our customers we know this isn’t a hypothetical — it’s a very real problem that analysts from many industries face, especially in the data-heavy streaming industries. But what if you could automate the manual, rote work of data exploration, and surface the most interesting, useful, and hard-to-find facts from your complex data? Let’s take a look at how you can use Sisu to find answers in your dynamic session-level data faster and inform decisions on everything from programming to ad lift. 

Diagnose your most complex metrics in session-level data

The average session-level dataset includes hundreds of columns – everything from household demographics and content viewed to session minutes and dayparts. That adds up to billions of possible reasons for change and it’s difficult to know where to start. 

Normally, you’d start with a hypothesis of the factors you think are impacting your metric. At Sisu, we believe it’s best to begin with what you know, which is your key business metric, and let our platform uncover the factors that matter so you don’t miss any. So let’s start with an analysis of session duration. 

Sisu simplifies the process of diagnosing this complex metric. To begin you only need to declare two things: where the session-level data lives and the column that defines the KPI. In this case, that’s an existing table (public.siview_sessions) and session_duration as our KPI, and we’d like to understand why it’s not increasing. 

(Product images use mock data.) 

Typically, you’d have to manually pick through the data to select the factors you think might affect this metric. This is time-consuming and introduces a certain level of bias into the analysis. Instead, Sisu will automatically identify the features in the data that are most important to the KPI, and gives you the choice to deselect factors that prove to be less valuable. 

For this query, we want to understand how the metric performs over time. We’ll select  session_date and all that’s left to do is to “Get the facts.”

Check millions of hypotheses in less than six seconds

Behind the scenes, Sisu is testing hundreds of thousands of individual sessions and millions of possibilities in the data to explain what impacts session duration. This is faster and more comprehensive than any tool (or team of analysts) and eliminates the arduous task of manually slicing and dicing data. As a result, you get more time for valuable analysis and collaboration with the business.

Focus attention on the highest-impact populations 

Now we can see that average session duration shows a moderate 2% decline month-to-month (from about 53 minutes down to 52.3 ). A dashboard will only show a relatively flat curve, which doesn’t give you a lot to go on. With Sisu, we can see trouble lurking below the surface. Let’s take a look at some of the facts below: