Overview
Filters are essential for creating segments in Element451. By using different filter combinations, you can include or exclude attributes and behaviors of a person to generate a specific segment of person profiles.
In this article, we will discuss advanced segment filters by combining "All Properties" with HAS and DOES NOT HAVE operators.
All Properties
Within Element, there are several data groups that feature an All Properties filter option. These filters enable you to select specific conditions based on multiple properties associated with that data. For instance, if you use the Address (All Properties) filter, you can filter for a particular state and specific county in one filter.
The All Properties filters allow you to include or exclude multiple properties into one segment filter by using the HAS and DOES NOT HAVE operators.
Additionally, you can combine multiple filters using ANY and ALL operators to create highly targeted and robust segments within Element. Learn more about Any and All Operators by reading this article.
Data Groups that contain the All Properties filter are:
|
|
|
To find an All Properties filter, you can use the Find Filter search feature or scroll the list to locate a filter with All Properties in parenthesis.
HAS vs. DOES NOT HAVE
Within any All Properties filter, you can group filters within a property to generate a segment using the HAS or DOES NOT HAVE operator.
HAS: Use when you want to include only those users who match specific property attributes in your segment. This operator ensures that your segment consists of users who possess the characteristics or details you've chosen.
DOES NOT HAVE: Use when you aim to exclude users with certain property attributes from your segment. This operator filters out users who have the specific characteristics or details you wish to avoid.
For example, the screenshot below illustrates using the All Properties filter and the HAS operator. This filter will create a segment that includes users with an application that meets all the following criteria:
The Term is Fall 2022
The Application Status is Submitted
The Student Type is Freshman
If we use the DOES NOT HAVE operator instead, the filter will return users that have an application but that application fails to meet all three filter criteria.
The Term IS NOT Fall 2022
The Application Status IS NOT Submitted
The Student Type IS NOT Freshman
Additionally, the list will also include records with no applications at all.
💡 Pro Tip: Consider reading the segment conditions as a sentence to understand better how your segment will function. For the examples above:
<Find people that> Has an application <with> this term, status, and student type associated with it.
<Find people that> Does Not Have an application <with> this term, status, and student type associated with it.
Additional Use Case Example
Suppose you would like to send an email campaign to users with submitted applications and have not yet registered for a specific visit day event.
You can combine filters and operators to narrow down your user list accordingly.
Use the Application (All Properties) filter
Use the HAS operator to include users who have submitted an application for the current term using these properties:
Status = Submitted
Term = Fall 2022
Then, add an additional filter, Event (All Properties)
Use the HAS NOT operator to include users who have not registered for Campus Visit Day
Event Name = Campus Visit Day
Once you apply the additional filter, you will notice that it groups the two filters together with the ALL operator. This requires the criteria outlined in both filters to be matched in order for a user to be included.
The resulting segment will be those with submitted applications for the Fall 2022 term who have not registered for the Campus Visit Day event.
Common Mistakes
Users commonly think that using HAS combined with IS NOT or NOT IN is the same as DOES NOT HAVE combined with IS or IN. Let's look at another simple example of this:
Scenario: You want all users who have not registered for an upcoming open house.
Using the Event (All Properties) filter:
🟢 CORRECT
[Event (All Properties] [DOES NOT HAVE] [EVENT NAME] [IS] [OPEN HOUSE]
Explanation: This will include users with no event registrations AND those with an event registration for an event with a name other than Open House.
🔴 INCORRECT
[Event (All Properties] [HAS] [EVENT NAME] [IS NOT] [OPEN HOUSE]
Explanation: This will only include users who have registered for an event that is not named Open House.