Audience Filter Rules
Last updated
English
Last updated
Audience groups are made up of a combination of filter conditions, which are broadly divided into event and user profile conditions.
Event
Up to 2 possible
User Profile
No limit on the number (but filter conditions cannot be added with the same properties)
At this time, you can only add with the same filter conditions within a group. ( )
Events are broadly divided into counts and the way they aggregate the sub-attributes of the event . In the case of attribute aggregation , the sub-attributes of the event must be registered to be used .
Total Count
You can filter conditions on the total number of events that occurred within a period.
Attribute Aggregation
You can filter by aggregating sub-properties of the selected event.
*Filtering by attribute aggregation is not possible for all events, all active events, and system events.
It refers to the number of times an event occurs.
If you want to set a condition for customers who have made more than 5 purchase events in the past 30 days, you can set it as follows.
You can set more detailed conditions with sub-properties of the event.
If you want to set the customer as a customer who has purchased a total shipping fee of 5,000 won over the past 30 days, you can set it as follows.
Shipping fees are collected as integer data, and you can choose aggregation methods such as sum, average, minimum, and maximum. However, if the data type is different, the aggregation function provided will be different according to the table below.
String
• Number of attributes (Unique)
Integer (Number)
Mistake (Double)
• Sum • Average • Min • Max
List of strings
Not supported
True/False (Boolean)
Not supported
Date and Time (Datetime)
Not supported
Character (String enum)
Not supported
List of “Number | Double”
Not supported
After selecting an event, you can filter the event further by adding detailed conditions. There is no limit to the number of filters, but you cannot add duplicate properties that have already been added.
Basically, all events can be filtered by the DFINERY auto-collected properties, and additional filtering is also possible by sub-properties of the selected event.
If you want to add a filter called Customers who purchased in Gangnam-gu to the previous example ( Customers who made more than 5 purchase events in the past 30 days), you can set it up as follows.
Event Attributes Precautions
Not operator (does not include, excludes values, excludes starts with, excludes between values) is not supported.
Only one List type can be used at most.
Unlike event conditions, user profiles can be filtered directly by the always up-to-date user profile DB attribute values without selecting events.
If you want to set a condition for customers who are female and have a membership level of 'Diamond' , you can set it as follows.
There is no limit to the number of conditions you can add to a user profile, but you cannot add duplicate properties that have already been added.
You can set up to 100 days per group.
When the period is set to 'Relative', the selectable reference date can also be set to up to 100 days in advance.
User profiles are broadly divided into categories: user properties, recent device properties, and behavioral properties. ( )
When combining two groups, you can search for up to 200 days. ( )