There are many attributes in Exponea, either for customers or events, which can be used to further specify and filter the data you are looking for. Filters in Exponea are almost everywhere, and each filter is used bit differently. One type of analyses can have multiple different filters, but also multiple filters of the same category. It is important to choose the correct filter to apply where there are multiple options.

There are multiple types of filters:

  • Date filters
  • Customer filters
  • Event filters

When working with customer and event attributes, values are filtered by comparison with static values or dynamic attributes using operators.


Date filters

Date filters use to restrict the time range of events. They work with UNIX timestamp value that is an attribute of each event. Time filters are usually present in dashboards, reports and other analyses, and whenever there is any metric working with events. Date filters can be specified e.g. for whole report, or for individual metrics in report separately. When there are multiple date filters, they work as AND and consider intersections of them. Date filters for reports DO NOT influence events in customer filter funnels.

date filters

There are two possible ways of selecting the range in date filters: absolute date range, relative date range

  • Absolute date range works with specific dates, which are taken into consideration. There is an option to remove restraint from one side only by checking from start or until now checkboxes.
  • Relative date range changes the date depending on current time. It also depends on the time period chosen, with start of the period being always dependent on the unit chosen. When selecting the option as days, start of the period will always be midnight of specified day. When choosing month, start of the period will always be 1st of specified month. This causes different results for e.g. last 7 days vs. last 1 week. Relative range can be selected from predetermined templates, or can be customized. You can determine the length of the period and also how long ago in time it was

custom relative range

Customer filters

Customer filters can be specified both when working with customer attributes and when working with event metrics. Customer filters are located e.g. in reports or as scenario nodes. There can be more customer filters specified and combined using mathematical AND and OR. Customers can be filtered in two ways.

  • Based on attributes. When this option is selected, the filter will look on given or derived customer attributes (such as aggregates or expressions) to determine if the customer matches filter or not
  • Based on funnels. When this option is selected, the filter looks on events of the customer to determine if the customer matches filter or not. The specified event order must be present to match the customer. More about funnels can be found in the separate guide. When working with funnel filter for customers, global date filter (e.g. in reports) does NOT apply for the events specified in the funnel.

customer filters

Event filters

Events are filtered based on their tracked or derived attributes. This is especially important, as one event type can be further specified by some attributes. Event filters work similarly as customer filters based on attributes. Multiple event filters for one event are always combined using mathematical AND.

event filters

event filters 2


Operators are used both in customer filters and event filters. There are multiple different ways to compare the attributes.


When choosing an operator, you can compare either to a static value or to another attribute by clicking on the Pi button.

operators dynamic attribute

There are different categories of operators, as well as 4 that special ones, that are

  • is set – is evaluated as true in case when the attribute is filled (even with ’empty’ value, e.g. string with length of 0
  • is not set – is evaluated as true only in case when the attribute is not filled at all (is null)
  • has value – is evaluated as true in case when the attribute is filled with some non empty value (e.g. string with length > 0)
  • has no value – is evaluated as true only in case when the attribute is filled, but with empty value (e.g. string with length of 0)

String operators

String operators compare the exact match of characters to the specified value. There are 6 different operators in this category

  • equals – value must be identical to this string
  • does not equal – value must be set, but different than the specified string
  • in – value must be matching one of the strings selected from a list
  • not in – value must be different than all specified values – value must be set, but different than the specified values
  • contains – value specified must be a part of the attribute
  • does not contain – value specified must not be a part of the attribute

Number operators

Number operators work with values as numbers and can be mathematically compared.

  • equals
  • in between
  • less than
  • more than

Boolean operators

Boolean operators work with the values as either true or false, and therefore there are only two options. Some attributes that are of Boolean nature doesn’t have to have any value, and in that case, neither of the operators will select them

  • is true
  • is false

Date operators

These operators compare attributes that are in date format to the current time.

  • more than – relative time period in past or future that is further away than the specified time restraint
  • less than – relative time period in past of future that is closer than the specified time time restrain
  • matches range – any date within the specified absolute date range
  • matches current day- if the day of the month of the date attribute matches the day of the month of current day.
  • matches current month – if the month of the date attribute matches the current month.
  • matches current year – if the year of the date attribute matches the current year.

supported time formats are:

  • UNIX timestamp
  • Y-M-D, Y-M-D H:M, Y-M-D H:M:S,
  • D-M-Y, D-M-Y H:M, D-M-Y H:M:S
  • M/D/Y, M/D/Y H:M, M/D/Y H:M:S
  • D.M.Y, D.M.Y H:M, D.M.Y H:M:S

List operators

list operators combine one of the previous operators with an ability to choose if all items from the list must fulfill the conditions of if it is enough that at least one item fulfills the condition

list operators


You are now done with the Getting Started guide!

Updated on October 30, 2017

Was this article helpful?

Related Articles