"Have" filters relate to demographic and other characteristics about people. Examples include their name and email address as well as preferred majors and terms. These are called "properties."
When you build a filter, you'll first select a group, which is a set of categorized properties to narrow down your search.
After selecting the group and property you'll be taken to the "constraints" tab. The constraint looks at specifics of the property. For example, if you choose the "Address State" property, the constraint might look to see if the address field in the person's account contains a particular state. The state itself, for example New York, is the "value."
Constraints vary depending on the type of filter you select (Learn more about constraints - link)
"Did" filters relate to actions people have taken. For example, answering a survey, clicking a link, or submitting an application. Did filters help you keep track of how people are interacting with your communications, applications, etc. And like "Have" filters, they help you send personalized communications and deliver relevant content.
Let's take a look at how these filters are built. Did filters are all built in a similar fashion as Have filters. The differences you will find are in the options you have for the constraints.
When you create a Did filter, you'll first select the group and then the action, which is called a "property." Then you'll be taken to the Constraints tab.
In the first section of the Constraints tab, you can select multiple properties related to the main property to narrow down your search. For example, if "Clicked Link in Email" is the action, you'll need to indicate the property of that email you want to look at, such as its title. Once you choose the property, you'll indicate a value to compare to, and a logical operator to use in the comparison. The list of properties will vary depending on the action you selected, but here are some common ones:
- Site: Choose the Site you'd like to associate with the event from a dropdown. This allows you to differentiate between similar actions that occurred in different parts of the app, such as a Clicked Link on a specific Admitted Students Microsite, or a User Login to the App451 site.
- URL: For example, Page URL and Target URL constraints will appear for Link Clicked on Page. Entering a full URL (e.g. 'https://admit.wne.edu/dashboard') or a partial URL (e.g. 'admit.wne', 'dashboard') will filter Link Click events by the page the user was on and the page the link directed them to. You can use the operators like 'contains', 'starts with', 'ends with' to make your search more specific.
- Email: Populates with a list of your named saved emails. Operators like 'is', 'is not', and 'in' allow you to narrow or expand your search.
- Email Name: Allows you to search for a word or group of words that match the name of the email. Word search operators include 'contains', 'exists', 'starts with', 'ends with', 'is not', 'does not contain', 'does not exist', 'does not start with', 'does not end with', and 'regexp' (a very specific search using the Regular Expression language).
- Application: Populates with a list of your applications.
- Country: Select a country from a drop down list to match where the user performed the action.
- City: Search for a word or group of words that matches the name of the City where the user performed the action.
- State: Select a US state from a drop down list to match where the user performed the action.
- State or Region Name: Search for a word or group of words that matches the name of the state or region (including regions outside of the US) where the action was performed.
- Mobile Device: True/False field matching whether the user completed the action using a mobile device (like a cell phone or a tablet).
- Browser Family: Search for a word or group of words that matches the Web Browser the user used to complete the action.
- OS Family: Search for a word or group of words that matches the Operating System the user used to complete the action.
After completing the property information, you'll need to fill the Number of Times section. This is where you define the limits for the number of times a user has completed the chosen action. You can set the operator to "At least" or "At most" and then enter the value.
Just below that is the timing section. Just as with date fields in "Are" filters, you can choose a date range that is relative or exact.