Interana analyzes event data. The events are described by a combination of actions and event properties.
You can easily understand what is being done in each event by referring to a specific attribute (the action). You can define actions from an existing attribute in the raw data or you can define relevant actions from across multiple columns in unstructured raw data through the use of event properties.
You can access your data (like actors and event attributes) with cleaned up names and values that are familiar to you when you compose queries. You can then align the resulting names of your data with your day-to-day in your business, rather than the technical names represented in the code. This makes it easier for everyone who isn't familiar with every piece of data in your system.
You can build event properties that clean up your data by transforming names and existing values post-ingest. The ability to do this after ingesting data alleviates the need to anticipate and address all problems at ingest. It also means that you don't have to re-ingest data to make changes.
Data transformation sometimes necessitates bucketing various values into a new value, or performing an arithmetic function on a value. When constructing event properties, you can see examples from the underlying raw data (this feature will be added in the future) and the expected values output.
After building new, cleaned up event properties, you can hide other event properties so the incomplete data isn't used in a query or object definition. This helps ensure that users always refer to the correct data.
Raw and manual event properties
We differentiate between two types of event properties:
- A raw event property is any information in your raw data that adds more definition to actions.
- A manual event property is one that you have created through a defined value and function.