Filters
Power your data insights
Last updated
Power your data insights
Last updated
Filters are a core component of Fanplayr 360 that you should get a good understanding of before you start using the system.
Filters are used by many parts of the Fanplayr 360 application including:
Each of these use filters in a slightly different way but in general the interface is common throughout the experience.
When choosing a filter you can choose from event attributes, Profile attributes, Audiences and Consent details.
When choosing an event attributes the filter will show only those events that match. When choosing a Profile attribute, or Consent detail, events related to Profiles that match the filter will be used.
All event names and attributes, as well as Profile attributes will be displayed in this list as defined in the Data Dictionary. If you are sending through an event attribute of songName it could display as "Song Name" if defined in the dictionary.
The options displayed for attributes in filters are affected by PII settings in the Data Dictionary and wether the current user has chosen to display PII data.
After you select an attribute, the next step is entering a value in the section depicted below in Figure 2.
When selecting a value to compare your selected attribute, you will see a component similar to that in Figure 2. There will be up to five editable parts of this:
Data Type: In the top-right of the component, you can tell the system how to interpret the value entered. All semantic attributes have their data types defaulted, and you should only need to change this when filtering on custom attributes.
Scope: The first dropdown in the component is the scope. This will only appear when selecting an attribute from certain semantic objects (currently Product and Location). These objects can appear at various levels of an incoming event. For example, a product can enter the system by itself in a "Product Viewed" event or as part of a Cart object in a "Cart Viewed" event. This dropdown allows you to select which product scope you are looking to match.
Aggregation: If the data type is "Number", you will see another dropdown that dictates whether you would like to aggregate the data before attempting to match the filter. There are three basic levels of aggregation:
No aggregate: Filtering attempts to match this value on an event-by-event basis.
Aggregate by session: You can select a form of aggregation (count, sum, average, min, max, median). The system will aggregate the selected attribute's values over each of the user's sessions.
Aggregate by user: You can select a form of aggregation (count, sum, average, min, max, median). The system will aggregate the selected attribute's values over all events tied to the user.
Comparison: This dropdown will always exist but can have different options depending on the data type. The selected option will tell the system how to compare the defined value with the system data (greater than, equals, includes, etc.).
Value: This is the value to compare the data with to see if the filter matches. If a comparison operator of "between" is selected, you will need to enter two values.
If an aggregation is selected in a numeric filter, the resulting events (in Insights or Exports for example) will be those that match across the entire aggregation level. For example, a filter matching the total sum of order revenue for a user will return all events for each user that matches the filter.
By default only events from the last 30 days will be processed. This can be changed to filter on events up to a year ago.
In certain situations, there are additional date range options based on the current feature. These options are listed below:
"Last automation step": This option is available in Automations of any type. If selected, the filters selected will only be evaluated on events that have occurred since the beginning on the previous Automation step. For example, this could be used in conjunction with timer nodes to evaluate filters based on events that arrived since the beginning of a timer.
"Triggering Event": This option is available in Automations of type "Event". If selected, the filters selected will only be evaluated on events that have occurred since the event that triggered the Automation initially.
If you would like to filter on a specific event simply choose "Event Name".
Most items shown in the filter dialogue will be event attributes.
Attributes set on a Profile will show as "User > Attribute" in the list.
Events may be tracked with Semantic Objects, including data such as Orders and Products.
For example to filter on Product details, find the "Product" attribute" and selet it.
You will then be shown a list of Product attributes you can filter on.
Consent can be filtered on. Simply choose the "Consent" attribute.
You will then see different parts of the consent that you can filter on.
When choosing "Consent > For" you will get al ist of the different types of Consent users have given.
