Skip to main content
You are viewing the documentation for Interana version 2. For documentation on the most recent version of Interana, go to


Scuba Docs

Metrics, measures, and aggregators

Neal Kaplan

There are different ways to measure events in Interana. The measures you can use when building a query in the query builder (in the Visual Explorer) and when creating named expressions include basic counts (Count Events, Count Unique <column values>) and pre-built aggregators (sum, average, median). And once you create your own metrics you can use those, too. 

Default Interana measures


There are three types of metrics you can create, per-actorratio, and custom session metrics, and a fourth type of metric that is automatically created when you build sessions and funnels. 

Per-actor metrics

Per-actor metrics let you define and name a measurement for each actor, such as the number of times they performed an action. You can use these in the Query Builder under Measure to understand characteristics of different actors or under Filter to compare different subsets of actors based on ad-hoc criteria. You can create per-actor metrics in the Metrics tab.

Per-actor metrics calculate how many times an event occurs during a specified period of time. For example:

  • How many times per day callers hang up while waiting on hold
  • Number of users active out of a 7 day period
  • Number of unique products a user has viewed over the last year

Interana displays per-actor metrics as  metric  <metric name> in lists.

Using the Time override settings

By default, when you use a metric in a query the time range used to compute the metric is inherited from the time range used to create the query. So if you are querying over the last month, the metric will be computed over the last month of data. 

You can use the Time override controls to have Interana compute the metric over a different time range. 

  • Single measurement over time range: Use this to set a specific time range to use to compute the metric. This is the time range that will be used every time the metric is included in a query. 
  • Time series of measurements over all time: Use this to compute the metric over specified time windows over all time (from the beginning of your data stream). You can also use this to create relative time window metrics, which create metrics for the current time, the "next" time window, and the previous and "before previous" time windows. 

If you use the Time series of measurements over all time option, your query resolution will default to the units that you set for that option. So if you set the time series of measurements to 2 hours, the query resolution will be in hours. Similarly, if you set the time series of measurements to 1 month, the query resolution will be in months (a "month" in Interana is defined as a 30-day period). You can use the chart controls in the Visual Explorer to adjust the resolution. Alternatively, you can add "with_nonoverlapping_windows" to the name of the metric to override this behavior and instead use the default resolution of the query. 

Ratio metrics

ratio metric divides the result of one measurement by the result of another measurement. You can define ratio metrics for events occurring during a specified period time; when the numerator represents a subset of the denominator, the result is a percentage. You can create ratio metrics in the Metrics tab.

For example:

  • New users who signed up this week versus those who signed up last week
  • Emails opened versus emails sent per month, on a rolling basis
  • Users who consumed a particular resource after viewing a webpage, compared to all users who viewed the page

Interana displays ratio metrics as an aggregation similar to Count Events in the Measure tab.

Ratio metrics and filters

The filters that you apply to queries are applied to both the numerator and denominator of ratio metrics.

Custom session metrics

Custom session metrics are metrics you can create to apply to events which occur during a particular session. 

For example:

  • Number of purchases users made within their first login session.
  • Unique webpages users went to in sessions which last more than 1 hour.
  • How many error messages the user saw during their second attempted registration session.

Interana displays session metrics as  session  <metric name> in lists.

Auto-generated metrics

These metrics are created automatically when you build sessions and funnels. 

Automatic per-session metrics

Interana automatically creates two metrics for every session: a duration metric and an event_count metric. The duration metric is session_name.duration, and the event_count metric session_name.event_count

Interana displays auto session metrics as   session  <session_name>.duration and  session  <session_name>.event_count  in lists. 

Funnel metrics

Interana creates five metrics for each funnel.

  • <funnel name>.current_state: This represents the most recent step that was reached within a funnel. This is calculated on a per-funnel instance basis. For example, if I had a funnel named myFunnel, where Step1 was Register, Step2 was Purchase, and Step3 was Log Off, events with myFunnel.current_state=1 would be all events that happened between Register and Purchase, including register and excluding Purchase.
  • <funnel name>.terminal_state: This represents the furthest step reached within a particular pass through a funnel. This is calculated on a per-funnel instance basis. For example, if I had a funnel named myFunnel, where Step1 was Register, Step2 was Purchase, and Step3 was Log Off, and today I registered, purchased, and logged off, then all of my events from Register to Log Off would have myFunnel.terminal_state=3 since the furthest step I reached through this pass of the funnel was 3.
  • <shard key>.max.<funnel name>.terminal_state: For each actor, if the actor passed through a funnel multiple times during the time range that you selected this metric shows you the furthest step that they reached in all of their passes through the funnel.
  • <shard key>.<funnel name>.time_between.<step>.<step>: This is the time each actor took between steps, for any pair of steps in the funnel. If the actor made multiple passes through the funnel, this computes the average of those times.
  • <funnel name>_transition_time_to_current_state: This is the amount of time it took to reach the step representing the current_state in the funnel pass from the step representing the previous state in the funnel pass. This is calculated on a per-funnel instance basis.

Interana labels these metrics as  funnel  <metric name> in lists. 

See Build funnels and funnel metrics and for detailed descriptions and examples.