Adding a New Profile Filter
The process of adding a new Profile filter consists of defining one or more conditions that will be used when the filter is applied.
- In a Profile filter, set conditions based on Recipient data or Groups
- You can connect multiple conditions using the Boolean operators AND & OR (e.g. "Age" field must be a number that is more then than "35" AND equal to or less than "50")
- The "Test" drop-down changes depending on the selection made in the "Type" drop-down. Fox For example, the tests that can be done when the "Type" is "Text" are clearly different from the ones that are performed when the "Type" is "Date" or "Number".
...
In the example below, a business that is using MailUp in connection with an ecommerce store is setting up a filter that looks for customers whose latest order amount was a number between 100 and 500. Two conditions were created using the "Decimal" type Number (decimal)" entry and connected using the AND operator. This filter is based on the assumption that the a field containing the latest order amount exists in the Recipients Fields.
Tip | ||
---|---|---|
| ||
You can populate fields in the recipients database by using one of the available ready-to-go integrations (e.g. ecommerce integrations) or by developing your own integration between your application and MailUp using the mailupapi. |
Subscription date
Among the fields that you can use to create Profile filters is the subscription date. This field is filled automatically with the date of when the subscriber is added to the List, and can be used for a number of useful filters and triggered messages.
If you are doing a comparison on that date (e.g. a filter that looks at everyone that subscribed 60 days ago) select the MM/DD/YYYY field format from the Type drop-down, as shown in the picture below.
Tip | ||
---|---|---|
| ||
When filling a date field, you can input date format (month and date) as follows: 05/06/2014 or 5/6/2014 ... the system will accept both. The year format however must always be in a 4 digits number (e.g. 2014). |
Decimals
When you select Decimals from the Type menu:
- MailUp expects a number in that field
- The number should not contain a thousands separator
- The number can use either the comma or period as a decimal separator
Keep this in mind when you import recipients data via the Import Wizard or the API.
Handling arrays of values
If you save an array of values into a recipient field, you can match an element of the array by combining multiple conditions into your filters.
For example, let's say that in a recipient field called "Product_Purchased" you are saving IDs of recently purchased products (the data has been saved there via a data import, by leveraging an integration with another application, or by executing an API call).
Assume that you want to see if a product whose ID is "101" has been purchased. You would create a filter that contains the following conditions:
- Product_Purchased equals to "101" OR
- Product_Purchased starts with "101," OR
- Product_Purchased contains (like) ",101," OR
- Product_Purchased ends with ",101"
You can adjust the conditions above if you want to create a filter that looks to ensure that this product has not be purchased, or to cover other scenarios.
Related Topics
- Listing existing profile filters
- Editing a profile filter
- An introduction to filters
- About the Marketing+ feature package
Multiple values profile filters
By using the two profile conditions "is one of these" and "is not one of these" you can create a filter containing multiple values separated by a comma, up to 500 characters.
In the example here below, the filter will pick up all recipients living in New York, San Francisco, Boston or San Diego.
The "is not one of these" condition does not consider empty or null values, so it will exclude only recipients who have a value assigned to the selected field.
Anchor | ||||
---|---|---|---|---|
|
Date and time format
Filters now support hour-based conditions that allow you to run time-sensitive drip campaigns, such as abandonment cart emails, that need to be sent within hours.
In order to use this type of comparison, the data must be saved into a recipient field using the ISO date-time standard, which looks like this:
YYYY-MM-DDThh:mm:ssTZD
... where:
YYYY = four-digit year
MM = two-digit month (01=January, etc.)
DD = two-digit day of month (01 through 31)
hh = two digits of hour (00 through 23) (am/pm NOT allowed)
mm = two digits of minute (00 through 59)
ss = two digits of second (00 through 59)
TZD = time zone designator (Z or +hh:mm or -hh:mm)
For example: 2015-02-24T19:20:30+01:00).
Info | ||
---|---|---|
| ||
When using an hour-based comparison with a profile filter, make sure that it contains the date and time in the ISO format: YYYY-MM-DDThh:mm:ssTZD |
Common scenarios for hour-based conditions
There are many scenarios in which you may want to use hour-based conditions. For example:
- 4 hours after the latest order has been placed on an online store
- 2 hours after somebody signed up for a certain service
- 3 hours after someone abandoned a shopping cart
- Etc.