Filtering Data
Overview
NetSpring maintains consistent data filtering across all explorations and model behavioral semantics. The filtering layer comprises various options to facilitate conditional data, group, aggregate, block, property, value, and time-based filtering.
Filtering Options
Depending on the analytics and data processing needs, the options are distributed across all functions. Let us examine the various filters that may be encountered while working on NetSpring.
Entity Filters
Throughout the application, entity filters facilitate conditional filtering in data definition and analysis. These filters can be accessed and enabled through the "Filter" button present in all exploration templates.
The + Add single condition and + Add group buttons enable you to establish one or more conditions. These conditions can be structured hierarchically, with nested and/or conditions forming groups that can be expanded to an unlimited number of levels.
You have the option of choosing filtering condtions and their values from 4 different tabs in the drop-down - catalog, blocks, values and parameters.
The Comparison operators used in each condition are as follows:
When working with string data, comparison semantics are case-insensitive.
| Condition | Description |
|---|---|
| is | The left-hand side of the condition equals the right-hand side of the condition. |
| is not | The left-hand side of the condition does not equal the right-hand side of the condition. |
| contains | The left-hand side of the condition is a string that contains the right-hand side of the condition as a substring. |
| in | The left-hand side of the condition is present within the set of values selected on the right-hand side of the condition. |
| <, >, >=, <= | Mathematical operators |
| not contains | The left-hand side of the condition is a string that does not contain the right-hand side of the condition as a substring. |
| not in | The left-hand side of the condition is not present within the set of values selected on the right-hand side of the condition. |
Properties used for comparison may include catalog properties such as columns, derived columns, blocks, values, or parameters.
Property Filter
Property filters are generally used in cohorts to specify conditions inside blocks.
You can use this filter to specify a condition that includes two values connected by a comparison operator. The comparison operators utilized in each condition are detailed below:
When working with string data, comparison semantics are case-insensitive.
| Condition | Description |
|---|---|
| is | The left-hand side of the condition equals the right-hand side of the condition. |
| is not | The left-hand side of the condition does not equal the right-hand side of the condition. |
| contains | The left-hand side of the condition is a string that contains the right-hand side of the condition as a substring. |
| in | The left-hand side of the condition is present within the set of values selected on the right-hand side of the condition. |
| <, >, >=, <=, | Mathematical operators |
| not contains | The left-hand side of the condition is a string that does not contain the right-hand side of the condition as a substring. |
| not in | The left-hand side of the condition is not present within the set of values selected on the right-hand side of the condition. |
Properties used for comparison may include catalog properties such as columns, derived columns, blocks, values, or parameters.
Time Filter
Time filters are generally used for filtering events based on the time of occurrence of each event
This filter can be used in the following modes:
| Mode | Description |
|---|---|
| Relative | relative to current time, e.g. last 3 months, or all time |
| Absolute | time window based on absolute dates and optionally time of day. |
| Relative to Event | filters events based on relative duration between an event and a baseline event or timestamp specified here, e.g. "within 2 weeks after event "onboarding" first occurrence". |
NetScript Filter
NetScript Filter is an alternative option for defining filtering conditions using NetScript instead of a regular Expression Tree-based interface.
For detailed documentation on syntax and functions, refer to the NetScript language reference.