Table of content

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.

Learn more about how to set the conditions in a filter.

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 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.

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 MailUp API.

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 30 days ago) select the Subscription Date field and set the remaining fields as shown in the picture below.



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).


When you select Decimals from the Type menu:

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:

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.

Hour-based profile and activity filters

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:


... 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).

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 an hour-based conditions. For example...

Profile filters:

Activity filters:

A popular scenario in e-commerce is to run an email drip campaign which targets shoppers that have abandoned a shopping cart. Click here to read more


Related Topics