Interana made major enhancements in 3.0 based on feedback from our customers. Included in these improvements is a new system of knowledge objects that replace and extend the 2.x named expressions as Interana's re-usable query building blocks. In 3.0, you can express any 2.x named expression logic in 3.0 knowledge objects with many new capabilities and simplifications.
Named Expression to Knowledge Object mapping
This table shows how specific named expressions in 2.x map to new knowledge objects in 3.0.
|Named Expression (2.x)||Knowledge Object (3.0)||Notes|
|Cohort||Segment||Segments in 3.0 perform the same functions as cohorts in 2.x, but are no longer limited to a specified time range.|
||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.|
|Ratio metric||(Not in 3.0)||In 3.0, you can perform similar functionality in Explorer, and there is not a separate Ratio metrics object.|
|Per-actor metric||Actor property||
Per-actor metrics use cases are served by actor properties in 3.0, as they are properties used to describe actors.
New Knowledge Objects
We have created new knowledge objects in 3.0 to make more logic re-usable between queries than in 2.x.
|Event Property||Properties allow queries to summarize, group by and filter on re-usable expression that can be direct references to physical data columns, references to values derived from lookups, or logical expressions evaluating multiple physical columns.|
|Action||A knowledge object that defines what is happening for each event.|
Other Renamed or Refactored Concepts
We have also renamed, and in some cases refactored, other components of Interana between 2.x and 3.0 beyond named expressions for additional clarity.
|2.x Concept||3.0 Concept||Notes|
|Dataset / Table||Dataspace||We’re using the name dataspace 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 analyses.|
|Time column||Timestamp||What matters is when the event occurred, its timestamp; not how you store the information.|
||Event Property||Data columns, derived columns, and lookup tables all create properties for events that can be used in the same way in queries.|
|Lookup table (joined to a shard key)||Actor property||A lookup table joined to a shard key is describing the actor, so it’s now one of the actor’s defining properties.|
|Measure||SHOW (in Explorer and Object builders)||Use the SHOW syntax in builders to define how you want to measure your events.|
|Aggregator||Function||An aggregator in 2.x is simply a function you can run on your data in 3.0.|
|Group by||Split by||In 3.0, 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.0 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.|