In all Kubit reports, use the “Additional Settings” dropdown at the top to access advanced features, usually found in the Mode setting. In Query there are 2 Modes:

Query - The standard report type that is explained in this help article.
Impact Analysis - A valuable report method that let’s you see the impact of a particular metric before and after a user performs an event for the first time.

Impact Analysis

Within Impact Analysis the main use case is: “What is the impact to Metric A after a user engages with Event A?” More practically, here are a few examples from your favorite digital products:

What is the impact to Total Time Watched after a user is shown a Content Recommendation?
What is the impact of Total Sessions after a user signs up?
What is the impact of Customer lifetime value (LTV) after they purchase their first premium item?

Steps to build your Impact Analysis

Change the Mode in Query to Impact Analysis.
Choose the Metric you want to measure that is going to be impacted. Typically these are Sum, Count Event, or a Compound Measure, showing percent per User.
Apply any necessary filters or breakdowns.
Define the date range.
Select the Event that is the Impact or “trigger” event. This will be the thing that you believe will Impact your metric you built in Step 1.
1. Examples include Campaign Impression, Content Recommended, Signed In, etc.
Execute the analysis!

Let’s see an example of “What is the Impact of Total Watch Time after a user Enables Notifications?”

Interpreting Results of Impact Analysis

When you see the results what you see is the following:

A Day 0 indicator in the center of the chart showing that is was the first time in the period you selected that these users performed the “Enable Notifications” event.
A negative and positive Day counter on either side.
- This shows the days less than or after the Day 0 event date. It could be different for each user as you’re selecting a date range so we normalize them for you.
A line indicating the Metric (or Measure) you defined in Step 1.
- This will show IF the metric was impacted by the event you selected.

What we can see in our example is that in general “Enable Notifications” had a positive impact on Total Watch Time for our users during that time period.

Histogram

Oftentimes, understanding the number of users with a particular occurrence of an event or compound measure is helpful to understand distribution of engagement.
In Kubit you can build Histograms on any Sum/Avg/Min/Max Functions

Steps to build your Histogram Analysis

Change the Mode in Query to Histogram.
Select the Metric you want to measure that is going to be impacted. Typically these are Sum, Count Event, or a Compound Measure , showing % per User.
Select the Subject you want to analyze, this will be the “thing we are counting” that would perform the measure you create in Step 2.
Choose your ‘Count Subject’ by in the y-axis
Choose your ‘Group By’ in the x-axis (Binning)
1. You are able to use a pre-built Range if it’s applicable or create a custom one.
2. These Bins will be related to the expected values from your Measure in Step 2.
  1. Ex. If you are counting events performed and a user typically only can do that action 10 times in a day then the max number of your Range would likely be 10.
Apply any necessary filters
1. You cannot perform Breakdowns in Histogram Mode
Select the date range
Execute!

This example shows a histogram of Users based on the SUM of Minutes Watched on a Streaming Application. The Range of 100 means each Bin size is equally distributed up to 100 minutes.

Interpreting Histogram Results

Once the histogram computes you’ll see the results grouped by the Range bins you created in Step 4. This means that each color group is all Subjects that fell into that Range for the day/week/month/all time.

Using our example from above we can see that for 6/2/22 we are looking at Overall 444 users. Of those users 117 of them watched between 0-20 min of content. If we wanted to make a Cohort of users who fell in this Range we could left click on one of the bars and click Create Cohort from that data point.

Custom Alert Monitors in Query

When a Query is monitoring critical KPIs it’s important to be alerted when a measure or compound measure dips below or above a certain threshold. Previously Kubit detected these anomalies using our own model but now you are able to set thresholds yourself!

When creating a schedule for the Query report, follow the same flow of:

Naming the Schedule.
Setting the refresh timeframe.
Adding recipients to the emails of that Report and any Alerts.

The newly added functionality allows you to set thresholds of when an alert will fire on a given day.

Click “Custom Threshold Met”.
Input the parameters, meaning if any value on the chart is Above/Below a specific number.
You can also set Alerts based on percent change from the previous day by adding a Comparison Analysis to your Query.

Rolling Measures

Want to know what’s your weekly/monthly active users on a daily basis? Or what’s the moving average for any given day? Rolling Measures is a new feature designed to help you get those answers.

Rolling Options

There are three options. For each, you are able to select from the pre-filled numbers or type in your own and select it.

Rolling Average

For every day of the date range, do an average of the measure values for the last X days (including the current day).

Rolling Sum

For every day of the date range apply, the Measure Function and do a sum of the Measure values for the last X days (including the current day).

Rolling Window

For every day of the date range, apply the Measure Function over the date range window.

How to Build a Rolling Measure

Build your Measure in Query and when selecting your Measure By option (under your selected event) you will see a Rolling option in the top right of the dropdown.

Select your Rolling option
Select the pre-defined days or enter your own custom days and click the checkmark
Execute your Query

Constraints with rolling measures

Rolling Measures can span a maximum of 90 days.

Compound Rolling Measures

You’re also able to create multiple Rolling Measures and build formulas from their results. Here are a few examples:

Rolling DAU/WAU %
- Rolling 7 day Average of Unique Users divided by Rolling Window of 7 days of Unique Users
Rolling DAU/MAU %
- Rolling 7 day Average of Unique Users divided by Rolling Window of 30 days of Unique Users

Measure Filters

Measure Filters allow you to easily exclude outliers, especially when breaking down ratios. Let’s consider the following example:

It’s a simple ratio broken down by Country and interestingly there are some very high ratios:

Taking a closer look we can see the reason for the high ratios are the very low denominators. And this is the whole problem we are trying to solve here, very often when analyzing huge volumes of data there will be these outliers which creep up the order and prevent us from seeing the actual patterns clearly.

Let’s apply a Measure Filter to find all ratios where B > 100, so we can get a more representative order.

And sure enough, we get a very different top ratios from a different set of countries.

Note how all the B measure values are > 100:

What’s Next

Introduction

ANALYSIS

Collaboration

Lumos AI

DATA SOURCE

DATA MODELER

DATA MANAGEMENT

EXPORT AND SYNC

Administration

Advanced Query Features