Skip to main content
Interania

3.x to 2.x Object and Concept reference

Interana 3.x contains major enhancements based on customer feedback, including a new system of re-usable query building blocks that replace and extend the 2.x named expressions. In 3.x, you can express any 2.x named expression logic in 3.x using the intuitive sentence model query builder. 

Named Expression to Knowledge Object mapping

This table shows how specific named expressions in 2.x map to new knowledge objects in 3.x.

Named Expression (2.x) Knowledge Object (3.x) Notes
Session Flow Flows replace and extend both sessions and funnels. You can use flows to analyze user actions over time, a sequence of actions, or a sequence of actions over time. For a walkthrough of how to build a 3.x flow that models a user session, see Creating a 2.x session using 3.x flows.
Funnel Flow Flows replace and extend both sessions and funnels. You can use flows to analyze user actions over time, a sequence of actions, or a sequence of actions over time. For a walkthrough of how to build a 3.x flow that models a funnel, see Creating a 2.x funnel with a 3.x flow.
Ratio metric Actor property, Flow property In 3.x, you can compute ratios directly in Explorer using the query model sentence builder. You can also save a named per-actor or per-flow ratio as an actor property or a flow property.
Per-actor metric Actor property Actor properties in 3.x are roughly equivalent to Per-actor metrics in 2.x (but do not yet support the "activity" aggregation option). For a walkthrough of how to build a 3.x actor property that covers similar functionality as a 2.x actor metric, see Creating a 2.x per-actor metric as a 3.x actor property.
Cohort Actor property In 3.x, you can create an Actor property and filter on it within the Explorer to answer the same questions you would have answered using a Cohort.
Column Raw event property In 3.x, each Column from your raw data is automatically mapped to an Event property. You can change the name of this Event property without breaking existing references (references in 3.x are tracked by internal ID, not by name). 
Lookup column (joined to non-shard key) Lookup event property In 3.x, if the Lookup table is joined to a non-shard-key column, each Lookup column is automatically mapped to an Event property. 
Lookup column (joined to shard key) Lookup actor property In 3.x, if the Lookup table is joined to a shard key column, each Lookup column is automatically mapped to an Actor property.
Derived column Custom event property In 3.x, you can create a custom Event property that combines other Event properties using math functions and if/else bucketing. This covers many (though not all) of the use cases supported by Derived columns in 2.x, with the benefit that it does not require writing code. 
Global filter Custom event property In 3.x, you can use the "pre-filter" option to apply an event based filter to an Explorer query, or use "board filters" to apply an event based filter to all Panels within a Board. You can filter on a saved custom event property to answer the same questions you could have answered using a saved global filter.
(Not in 2.x) Action In 3.x, you can optionally "tag" one Event property as being the Action. This allows the Interana UI to streamline certain interactions. 

Other Renamed or Refactored Concepts

We have also renamed, and in some cases refactored, other components of Interana between 2.x and 3.x beyond named expressions for additional clarity.

2.x Concept 3.x Concept Notes
Table Dataset We’re using the name dataset to make it clear that Interana can ingest data from multiple data sources. 
Shard key Actor An actor, or the entity such as a person or a thing whose behavior was captured in an event, was always defined by a shard key; we’re clarifying this by using a single term.
Dashboard Board We shortened the name to boards because Interana’s boards are not static dashboards. Instead, Interana’s boards are active, living results of queries that you can use to launch your own analysis.
Time column Timestamp What matters is when the event occurred, its timestamp; not how you store the information. 
Measure Measure—Show and Calculate A measure in 3.x uses Show and Calculate syntax define how to measure events in Explorer and object builders.
Aggregator Aggregation function An aggregator in 2.x is referred to as an aggregation function you can run on your data in 3.x. 
Group by Split by In 3.x, we are clarifying that when you use this operation, you are splitting the whole of your result into different groups for ease of analysis.
Chart (Dashboard) Panel We’ve changed the name of the individual components of boards from charts (in 2.x dashboards) to panels in 3.x to convey that they are living, interactive components.
Query builder Explorer The explorer is where you can explore your data in depth; building queries is only one starting point in that process.
Named expression builder Object builder We changed the name of the builder to match the change from named expressions to knowledge objects.

Changes You May Appreciate When Moving From 2.x To 3.x

This table shows a few highlights of existing 2.x features that have improved in 3.x.

Product Area Core Change Notes
Explorer  Increased flexibility in combining aggregations, filters, split by and time offsets.  In 3.x, each aggregation can have its own filter (the two are rolled up into a named measure) and there is also a global "pre-filter" that applies to all measures. When working with multiple measures, you can select a split by that applies to all measures. You can select multiple time offsets (not just one) and these time offsets can be applied in combination with all the features above.
Explorer Math operators can be used directly in the explorer, and combined more freely using a function builder In 3.x, you can compute ratios (and other math expressions) directly in Explorer using the query model sentence builder. 
Boards Board panels can be edited  In 3.x, you can choose to edit a board panel. This takes you back to explorer, where you can adjust the query for that panel and click Save when you're ready to update the existing board panel. 
Derived columns Bucketing (if / else) and math function use cases can now be built directly in the UI (without writing D code) In 3.x, while we do not have full support for all 2.x derived column use cases, many of the common cases (such as bucketing and math functions) can be authored in the UI. 
Query history Your query history now persists across browser sessions In 2.x, the breadcrumbs showing preview queries would go away when you closed your browser. In 3.x, your query history persists across sessions. 
Query URL sharing Sharing a query URL is as simple as copying the URL from your browser In 2.x, the URL displayed in the browser was a long, complex string, and in order to get a short URL you would click the "share button". In 3.x, the URL displayed in the browser is already a compact URL designed for sharing. 

 

  • Was this article helpful?