This type of criteria allows you to create groups or perform searches based on contact data found in various locations in the application.
Criteria are presented under different tabs, representing the related feature.
*Note that you only see criteria related to modules that are enabled in the project.
| Section | Criteria | Description | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Profile | This section lets you add new criteria found in the project fields. You need to select a field for which you want a specific value and the operator, that is how the value must match. Then, you need to indicate whether the search value correspond to a fixed value or to the value contained in a project field. Searching for a fixed value is the most common since it allows to find contacts based on a specific value contained in a given field of the project. The option to find a value in a Field is used when you want to compare the values contained in two different fields in the project (such as an email address entered on a form and the confirmation email address provided in the same form). Therefore, if you want your group to include only contacts who have correctly entered their email address in both fields, you will use the following criteria: Email is equal to the field Email Confirmation. Once the value is specified, click on Add. Note that if the value is a date, the format must be YYYYMMDD. It is important to note that any date value can be decomposed, that is that you can create a group based on a specific day, month or year contained in a given date field. | |||||||||||||||
| Field | Used to select the profile field in which to search a specific value. The drop-down list displays all the fields available in the contact profile. | |||||||||||||||
| Operator | Used to specify the operator that joins the field and the value, that is how the value should match. See the list of valid operators. | |||||||||||||||
| Value | Option indicating that the selected field must correspond to the value defined in the Value field, based on the selected operator. | |||||||||||||||
| Field | Option indicating that the selected field must correspond to the value of another field in the same project. When this option is selected, a Field field displays to let you select the desired field. | |||||||||||||||
| Query time | Only valid for date fields. Option indicating that the date must correspond to the query date. The query date is the date on which the group will be used (usually when viewing or preparing a mailing). A group based on this criteria will target different contacts depending on when it is generated. Other options can be added if you also select Relative date (computed). In such a case, you can add or remove days, months, years, etc. from the current date. For example, to find a date in the past, you must remove days from the current date. | |||||||||||||||
| Status | This section lets you add criteria related to the various status, either the mailing status, email status or quarantine status, or based on the contact's subscriptions. | |||||||||||||||
| Sending status | Option indicating whether the contacts to include, or exclude, are active or inactive. | |||||||||||||||
| Email (syntaxis) | Option used to include, or exclude, contacts who's email address is valid or not. | |||||||||||||||
| SMS (syntaxis) | Option used to include, or exclude, contacts who's SMS number is valid or not. | |||||||||||||||
| In email quarantine | Option used to include, or exclude, contacts who are in email quarantine or not. You can also specify which type of quarantine interests you. | |||||||||||||||
| In SMS quarantine | Option used to include, or exclude, contacts who are in SMS quarantine or not. You can also specify which type of quarantine interests you. | |||||||||||||||
| Present in the email kill fill | Option used to include, or exclude, contacts present in the email kill fill. | |||||||||||||||
| Present in the SMS kill fill | Option used to include, or exclude, contacts present in the SMS kill fill. | |||||||||||||||
| Present in an unsubscribe list | Option used to include, or exclude, contacts present in an unsubscribe list. | |||||||||||||||
| Scenarios | This section lets you create groups based on information related to marketing automation scenarios, whether it is based on the scenario or on its status, final result, goal, start date or end date. Depending on the selected criteria, you will also need to specify the related item. | |||||||||||||||
| Messages | This section lets you add criteria based on the delivery status of messages. Depending on the selected status, other options can be available. | |||||||||||||||
| Delivery | Option specifying whether the contacts to include, or exclude, have sent, delivered or bounced messages.Sent - Message that was sent by Dialog Insight, regardless if the message was actually delivered or not to the contact. It is possible to select a specific message or mailing, or to indicate a given number of mailings. Delivered - Message delivered to a contact, where the reception has been confirmed by a remote email server ( valid email address). You can also filter messages by click or open status. Bounced - Sent message that bounced because of an error. | |||||||||||||||
| Source | When using the Select message or mailing option, you can select messages, mailings or message categories at the origin of the sent, delivered or bounced message. | |||||||||||||||
| Filtrer based on openings | Option valid only for delivered messages (Delivery = Delivered) that lets you select contacts based on the fact that the message was opened or not. | |||||||||||||||
| Filtrer by clicks | Option only valid for delivered messages (Delivery = Delivered) that lets you select contacts based on the fact that the message was clicked or not. | |||||||||||||||
| Keywords | Since the drop-down list doesn't show all the results, it is possible to enter Keywords as well as a date range (Min and Max) to further reduce the number of messages, mailings or message categories. | |||||||||||||||
| Occurence | Option that lets you specify the number of times the message, mailing or message category was sent, delivered or bounced. | |||||||||||||||
| Period | When specifying a date, it is possible to choose a specific date, specify that the date matches a value entered in another project field, or requires that the date matches the query date. How the two values should connect is determined by the selected operator. See a detailed description of the Period field. | |||||||||||||||
| SMS | This section lets you create a group with contacts who have received an SMS message or to whom one was sent. It is possible to do a search to find all contacts who have received or sent an SMS or limit the number of contacts based on a the result, source or period. | |||||||||||||||
| Mobile push | This section lets you create a group with contacts to whom one or more mobile push notifications have been sent or contacts who subscribed to a specific application's notifications. | |||||||||||||||
| Type |
| |||||||||||||||
| Web push | This section lets you create a group with contacts to whom one or more web push notifications have been sent or contacts who have subscribed to a a specific website's notifications. | |||||||||||||||
| Type |
| |||||||||||||||
| Links | This section lets you add criteria related to actions performed on links in the messages. Once you have selected the type of link to search, you have to select the actual link in the list of links. In addition, you can specify the origin of the click and how many clicks you are looking for. At last, you can define a specific date range to search. | |||||||||||||||
| Links | Indicates the type of link to search for.
| |||||||||||||||
| Clicked from | When a generic or operational link is selected, you can specify where the click originated, either from mailings, messages, message categories or from all sources. Once the type of click is indicated, you need to select the actual element or elements in the list in which to search the link. | |||||||||||||||
| Links | Drop-down list of all links in the selected mailing(s), message(s) or message category(ies). If you have selected clicks originating from all sources, this list will display all available links in all sources. | |||||||||||||||
| Keywords | Since the drop-down list cannot display all the possible results due to space limitation, you can use Keywords as well a specify a date range in (Min and Max) to reduce the number of results displayed. | |||||||||||||||
| # of clicks | Option that lets you indicate the number of times the link was clicked. | |||||||||||||||
| Period | When specifying a date, it is possible to choose a specific date, specify that the date matches a value entered in another project field, or requires that the date matches the query date. How the two values should connect is determined by the selected operator. See a detailed description of the Period field. | |||||||||||||||
| Administrative | This section is used to create contact groups based on administrative information contained in the contact profile. These information can correspond to actions specific to contacts , the creation source of the contact or the date of a selected event or source. Example You could create a group with contacts who have modified their profile over the last year. | |||||||||||||||
| Event | Option used to specify an action performed on contacts, such as contact creation, modification, activation/deactivation or quarantined or lifted from quarantine. Criteria can be cumulative (and) or exclusive (or). Example If you want contacts that have been created and modified, you will need to add the 2 criteria in 2 operations and link them with the 'and' operator. | |||||||||||||||
| Sources | When an event is selected, you can also specify its source, that is how the event occurred. ExampleOne could want to group all contacts who have been created manually. To do so, you would selection the event Creation and the source User interface. | |||||||||||||||
| Period | When specifying a date, it is possible to choose a specific date, specify that the date matches a value entered in another project field, or requires that the date matches the query date. How the two values should connect is determined by the selected operator. See a detailed description of the Period field. | |||||||||||||||
| A|B Split | Creating a group using segments lets you have A|B Split campaigns based on defined groups of contacts, with up to 10 segments. The advantage of this type of group is that a contact will always be part of the same segment over time. Contacts are assigned to segments, in turn, based on their ID number. For instance, let's take a project that has 7 contacts, and that you want to divide it in 3 segments - in this case, contacts will be dispatched as follows:
If contacts are added, they will necessarily be assigned a new and unique Contact ID and will be assigned to one of the segments, without modifying the contacts that were already assigned. And when a contact is deleted, the assigned segment does not change and is not assigned to another contact; the contact will just not be part of the campaign. | |||||||||||||||
| Segment my contact list in x segments | Specify the number of segments by which to divide your list of contacts. You can have a maximum of 10 segments. | |||||||||||||||
| Target X segment | Specify which specific segment is targeted by the group you are creating. | |||||||||||||||
| Device | As the system automatically collects information on the last device and last platform used to view a message, as well as the date of this last access, it is possible to create groups of contacts based on this information. You can therefore target contacts that have used an Android tablet over the last 60 days, or the ones who have viewed their messages on a mobile, whatever the device or date. It is important to note that only the last message access is taken into account. So if a person has opened a message with an Android tablet 5 days ago and opens another message (or the same) 2 days later with an iPhone, only this last access will be considered, that is Mobile+Apple. You can combine both Device type and Platform but it is important to remember the following:
| |||||||||||||||
| Device type | Option that provides the ability to target contacts who have used a tablet or a mobile (phone) to view messages. This type of segmentation lets you separate these 2 types of contacts and send them, ofr example, promotions based on the device they use. If no device selection is made, both devices will be targeted - meaning the same result as if both device types were checked). If you check more than one device type, the contact will have to satisfy either one. | |||||||||||||||
| Platform | Option provides the ability to target contacts based on the platform they use to open messages. This segmentation lets you group, for example, contacts who have used any Android device, or only an Android tablet. If no platform selection is made, all platforms will be targeted - meaning the same result as if both device types were checked). | |||||||||||||||
| For the last x days | Option that provides the ability to target a specific message view period. By adding this option in the criteria, you can, for instance, target contacts who have used an Apple tablet over the last 14 days. | |||||||||||||||
| Import | This section lets you target contacts who were part of an import. You must select a specific import and specify if you want all imported contacts to be part of the group or only those that were added or edited by the import. | |||||||||||||||
| Geolocation | This section lets you target contacts based on their location from a given postal code or from a specific location on a card, depending on the option that was defined for geolocation purposes. | |||||||||||||||
| Include contacts located at X km or less | Lets you indicate the distance in kilometers between the contact's location and the source location. | |||||||||||||||
| From | Lets you specify the source location, to calculate the indicated distance. There are 2 choices:
| |||||||||||||||
| Engagement | This section lets you target contacts based on their engagement and create groups based on the frequency or recency of the actions they have performed on your messages. Using this criteria, you can target contacts who have, or have not, received, opened or click in a message, during a given period or a given number of times, and this for one or more communication types. Following are some examples of use:
Note also that data are only compiled as of June 2016. | |||||||||||||||
| Type of measure | Specify on what type of measure you want to base your group, on the frequency or the recency of the actions performed. | |||||||||||||||
| Include contacts who | In the first field, indicate whether you want contacts who have, or have not, performed the action, and in the second field, the performed action, that is:
| |||||||||||||||
| Number of times, or period | Whether you have select to include contacts based on recency or frequency, the shown options will differ. Make one choice amongst the various options. | |||||||||||||||
| at least one message of the following type of communication | Specify in this field, the type of communication associated to the message. You can select only one, or multi-select by holding the CTRL key will selecting. Selected types are shown highlighted. | |||||||||||||||
| Personas | To target contacts based on personas you have created. Persona calculation is updated as per the set frequency, or on demand. You can choose to include contacts who are associated to one single persona or to multiple ones. | |||||||||||||||
| Abandoned cart | This section lets you target contacts who had a shopping cart with articles that they did not buy. Using this criteria, you can send these contacts a reminder to let them know of the articles they had showed interest in and ask them if they want to complete their purchase. It is important to specify the date and/or time of the cart was abandoned. When specifying a date, it is possible to choose a specific date, specify that the date matches a value entered in another project field, or requires that the date matches the query date. How the two values should connect is determined by the selected operator. See a detailed description of the Period field. | |||||||||||||||