LISTSERV Maestro 8.1-4 Help

List Subscribers

The left pane displays the LISTSERV Maestro explorer tree, with the "Subscriber Datasets" subtree. This subtree contains all subscriber datasets and lists. In this tree, each dataset has its own little subtree, with the main dataset node as the root, and two or three child nodes. The Lists node is such a child node.

This Lists node is in turn the root node of a small subtree that contains all list folders and lists of the dataset.

While the List Subscribers node of a list is selected in this subtree, the pane on the right shows a table with all confirmed subscribers on the list and allows browsing through the subscriber list. Unconfirmed subscribers are not shown.

By default, the list of recipients is sorted alphabetically by their email address. Recipients with an email address that is alphabetically "lower" are listed first. To change the ordering, see Ordering the Subscriber List Result Display below.

Each recipient's entire current profile is displayed. Each column in the table stands for one profile field and each row in the table stands for one recipient. The table header contains the profile field names and each cell is filled out with the value for the corresponding profile field, as defined for the recipient in the given row. For "Boolean" type fields, either the value "T" (for "true") or the value "F" (for "false") is displayed. For "Multiple Select" type fields, all selected values are displayed in a comma-separated list. For Advanced Subscriber Lists with topics, one additional field is displayed that shows all selected topics in a comma-separated list.

Selecting Recipients for "Edit", "Modify", "Delete" or "Download"

To begin working with the recipients, start by selecting one or more rows in the list (in the usual fashion). Depending on your selection (and the filter, if defined), the "Edit" menu contains items for editing, modifying, deleting or downloading either the recipients you have selected with your mouse or those that are matched by the filter (or all recipients, if no filter is defined). As a quick alternative to the "Edit" menu, the context menu contains the items that are applicable to your selection only.

Editing Recipients: (Only applicable if one row is selected from the list.) Opens a separate page that allows you to change all profile field values for one recipient.

Deleting Recipients: Upon confirmation, this deletes recipients from the underlying list.

Modifying Recipients: Modifies a field value for many recipients in one step.

Downloading Recipients: Downloads recipients in a zipped CSV-format text file.

Ordering the Subscriber List Result Display

To change the ordering of the subscriber list result display, click any of the column headers. This changes the current ordering of the result by either switching between ascending (the default, meaning that lower values are shown first) and descending ordering (which means that higher values are shown first). In the case of a number field, the terms "lower" and "higher" have the obvious numerical meaning. For a text field, an ascending ordering means that texts which come first the lexicographic ordering supplied by the database are shown first, and "descending ordering" means the opposite. For a single-select field, the ordering sequence is defined by the sequence of the values in the corresponding lookup table. For the subscribe-time field, the ordering is defined by the actual temporal sequence, i.e. "lower" means "earlier" and "higher" means "later".

The current ordering of the list result display is quoted on the bottom of the pane.

Filtering the Subscriber List

To define a filtering condition for a field of the subscriber list, click the fields just below the column headers. A popup dialog is shown with the current filtering conditions for the profile field. Initially, the list of conditions is empty, which means that no filtering is active. You can add more than one filtering condition for a profile field: Click [Add Condition] to add an additional filtering condition. Click the "remove" icon on the left to remove a condition from the list.

If more than one condition is defined on the field, please decide how to combine the conditions. Using the choice all means that only those recipients are shown who indeed match each and every of the conditions in the list. (If you defined the conditions to be mutually exclusive, then this of course means that no recipients are shown if you choose "match all conditions".) Contrary to this, using the choice any means that a recipient is shown if one of the conditions matches.

Click the [OK] button to apply the filter. LISTSERV Maestro refreshes the list of recipients. Each recipient in the list matches ALL active field-filtering conditions. You see a short description of the activated condition in the highlighted area directly below each of the column headers of the fields you defined conditions on. Hover over the highlighted area to show a longer text that describes each of the conditions in the list that is defined for the associated field.

The filtering options available for a condition in the list of conditions on a field depend on the field type. The following sections describe the available filtering options: Filtering on Subscriber Activity, Filtering on Standard Text Fields, Filtering on Email Addresses, Filtering on Number Fields, Filtering on Boolean Fields, Filtering on the "Tracking Permission" field, Filtering on Single-Value Selection Fields, Filtering on Multiple-Value Selection Fields, Filtering on Date Fields, Filtering on Birthday Fields and Filtering on the Subscription Date.

Filtering on Subscriber Activity

To define a filter condition on subscriber activity, first define how you want to filter on the subscriber activity.

The following options are available:

• Subscriber was recipient of: All recipients are shown who were also recipient of the selected job, if a job is selected. If you select "any job sent to the dataset or its list", then the result contains all recipients who have received any job that you sent to the dataset or its list. Subscribers who never have received a job sent to this dataset are not included.
• Subscriber was not recipient of: Same as above, only with the opposite meaning.
• Subscriber's email bounced for: Only those recipients are shown who were recipient of the selected job(s) and for who LISTSERV Maestro has received a bounce message. If you select "any job sent to the dataset or its list", then the result contains all recipients for which LISTSERV Maestro has received a bounce message associated with any job that you sent to the dataset or its list. In other words: This list shows all subscribers who may in the future be subject to bounce cleanup. Note: The subscribers listed here are shown with the current email addresses. LISTSERV Maestro records the original address that was used during delivery in a separate repository and checks incoming bounce messages against this repository, to determine if the email sent to the subscriber bounced. Additionally, subscribers who have already been removed (by bounce cleanup or otherwise) are also not shown.
• Subscriber's email did not (yet) bounce for: Same as above, only with the opposite meaning. In this special case, however, the statement "did not (yet) bounce" of course also means that LISTSERV Maestro may in fact receive a future bounce message for this subscriber (and the same job!). In other words: A subscriber currently listed as "did not (yet) bounce" may disappear from the list if you refresh the list after a short while.
• Subscriber opened the mail of: Only those recipients are shown who were recipient of the selected job and have opened the mail (i.e. LISTSERV Maestro has recorded any event for this mail job and this recipient). If you select "any job sent to the dataset or its list", then the result contains all recipients who have received any job that you sent to the dataset or its list and have opened the mail. Subscribers who never have received a job sent to this dataset or for whom LISTSERV Maestro did not record any event are not included.
• Subscriber ignored the mail of: Only those recipients are shown who were recipient of the selected job and have ignored the mail (i.e. LISTSERV Maestro did not record any event for this mail job and this recipient). If you select "all jobs sent to the subscriber via the dataset or its lists", then the result contains all recipients who have received any number of jobs that you have sent to the dataset or its list and have ignored the mail. Subscribers who have not received any jobs or have received at least one job sent to this dataset and for whom LISTSERV Maestro has recorded at least one event, are not included.
• Subscriber clicked links in the mail of: If you select "any job sent to the list", then the result contains all recipients who have clicked at least one link in any of the received mails. If you instead select a specific job from the list, then please select from the following options:
  • clicked any link: Only those recipients are shown who were recipient of the selected job and have clicked any link (i.e. LISTSERV Maestro has recorded a click event for any link in this mail job and this recipient).
  • clicked the following link: (Select the desired link from the drop-down menu.) Only those recipients are shown who were recipient of the selected job and have clicked the specified link. (i.e. LISTSERV Maestro has recorded a click event for this particular link in this mail job and this recipient).
  • clicked any of the following links: (Select the desired links from the multi-select drop-down menu. Hold down the CTRL key to select more than one link). Only those recipients are shown who were recipient of the selected job and have clicked any of the specified links. (i.e. LISTSERV Maestro has recorded a click event for any of the specified links in this mail job and this recipient).
  • clicked all of the following links: (Select the desired links from the multi-select drop-down menu. Hold down the CTRL key to select more than one link). Only those recipients are shown who were recipient of the selected job and have clicked all specified links. (i.e. LISTSERV Maestro has recorded a click event for all specified links in this mail job and this recipient).
• Subscriber ignored links in the mail of: If you select "all jobs sent to the subscriber via the dataset or its lists", then the result contains all recipients who have received any number of jobs that you have sent to the dataset or its list and have not clicked on at least one tracked link the mail. Subscribers who have not received any jobs or have received at least one job sent to this dataset and for whom LISTSERV Maestro has recorded at least one tracking link click event, are not included. If you instead select a specific job from the list, then please select from the following options:
  • ignored all links: Only those recipients are shown who were recipient of the selected job and have not clicked any links (i.e. LISTSERV Maestro has not recorded a click event for this mail job and this recipient).
  • ignored the following link: (Select the desired link from the drop-down menu.) Only those recipients are shown who were recipient of the selected job and have not clicked the specified link. (i.e. LISTSERV Maestro has not recorded a click event for this particular link in this mail job and this recipient).
  • ignored any of the following links: (Select the desired links from the multi-select drop-down menu. Hold down the CTRL key to select more than one link). Only those recipients are shown who were recipient of the selected job and have not clicked on all of the specified links. (i.e. for at least one of the specified links, LISTSERV Maestro has not recorded a click event for this mail job and this recipient).
  • ignored all of the following links: (Select the desired links from the multi-select drop-down menu. Hold down the CTRL key to select more than one link). Only those recipients are shown who were recipient of the selected job and have not clicked on any of the specified links. (i.e. for all specified links, LISTSERV Maestro has not recorded a click event for this mail job and this recipient).
• Subscriber forwarded the mail of: If you select "any job sent to the dataset or its lists", then the result contains all recipients who have received any number of jobs that you have sent to the dataset or its list and have forwarded the message. If you instead select a specific job from the list, then the result contains all recipients who have received this particular job and have forwarded the message.
• Subscriber shared the mail of: If you select "any job sent to the dataset or its lists", then the result contains all recipients who have received any number of jobs that you have sent to the dataset or its list and have shared the message via a social media application. If you instead select a specific job from the list, then please select from the following options:
  • shared via any application: Only those recipients are shown who were recipient of the selected job and have shared the message (i.e. LISTSERV Maestro has recorded a sharing event for any social media application, this mail job and this recipient).
  • shared via the following application: (Select the desired sharing application from the drop-down menu.) Only those recipients are shown who were recipient of the selected job and have shared the message via the specified application. (i.e. LISTSERV Maestro has recorded a sharing event for this particular social media application, in combination with this mail job and this recipient).
  • shared via any of the following applications: (Select the desired applications from the multi-select drop-down menu. Hold down the CTRL key to select more than one application). Only those recipients are shown who were recipient of the selected job and have shared the message via any of the specified applications. (i.e. LISTSERV Maestro has recorded a sharing event for any of the specified social media applications, in combination with this mail job and this recipient).
  • shared via all of the following applications: (Select the desired applications from the multi-select drop-down menu. Hold down the CTRL key to select more than one application). Only those recipients are shown who were recipient of the selected job and have shared the message via all specified applications. (i.e. LISTSERV Maestro has recorded a sharing event for all specified social media applications, in combination with this mail job and this recipient).
• Subscriber triggered an action of: If you select "any job sent to the dataset or its lists", then the result contains all recipients who have received any number of jobs that you have sent to the dataset or its list and have triggered an action-tracking event for any of the received jobs. If you instead select a specific job from the list, then please select from the following options:
  • triggered any action: Only those recipients are shown who were recipient of the selected job and have triggered any action (i.e. LISTSERV Maestro has recorded an action-tracking event for any action, this mail job and this recipient).
  • triggered the following action: (Select the desired action from the drop-down menu.) Only those recipients are shown who were recipient of the selected job and have triggered the specified action. (i.e. LISTSERV Maestro has recorded an action-tracking event for this particular action, in combination with this mail job and this recipient).
  • triggered any of the following actions: (Select the desired actions from the multi-select drop-down menu. Hold down the CTRL key to select more than one action). Only those recipients are shown who were recipient of the selected job and have triggered any of the specified actions. (i.e. LISTSERV Maestro has recorded an action-tracking event for any of the specified actions, in combination with this mail job and this recipient).
  • triggered all of the following actions: (Select the desired actions from the multi-select drop-down menu. Hold down the CTRL key to select more than one action). Only those recipients are shown who were recipient of the selected job and have triggered all specified actions. (i.e. LISTSERV Maestro has recorded an action-tracking event for all specified actions, in combination with this mail job and this recipient).

Choosing an optional time constraint:

• If you selected any of the recipient-only subscriber activities for filtering and have chosen the "any job..." option, then you can optionally define a delivery time constraint on the collection of jobs that LISTSERV Maestro considers when applying the filter. Choose "that was delivered in the recent past" and supply a number of days to let LISTSERV Maestro ignore all jobs that fall outside of the given time interval.
• If you selected any of the other variants of subscriber activity for filtering, then you can optionally define a time constraint on the events that LISTSERV Maestro considers when applying the filter.
  • For the "ignore" type variants of subscriber activity, choose "no activity occurred in the recent past" and supply a number of days to let LISTSERV Maestro only look at the given time interval when checking if a recipient matches because the associated collection of tracking events was not found. (Or, in other words: A candidate subscriber may indeed have triggered the desired events, but is included in the result nonetheless because none of the desired events have been recorded in the given time period.)
  • For all other variants of subscriber activity (i.e. those which require that the recipient actually triggered a certain type of events), choose "the activity occurred in the recent past" and supply a number of days to let LISTSERV Maestro only look at the given time interval when checking if a recipient matches because the associated collection of tracking events was found. (Or, in other words: A candidate subscriber is included in the result only if the desired events have been recorded in the given time period.)

Filtering on Standard Text Fields

• is not supplied: (Only available for optional fields.) Only recipients without a value for the selected profile field are shown.
• is supplied: (Only available for optional fields.) Only recipients with an actual value for the selected profile field are shown.
• is: Select this option to show an additional input field and supply the desired comparison value. Only recipients with the specified value for the selected profile field are shown.
• is not: Select this option to show an additional input field and supply the desired comparison value. Only those recipients are shown who have a profile value other than the specified value.
• is strictly before: Select this option to show an additional input field and supply the desired comparison value. Only those recipients are shown who have a profile value that is strictly before the specified value. Note: This comparison is performed directly on the database, so the database's ordering semantics apply.
• is before or equal to: Same as above, only with a non-strict comparison.
• is strictly after: Select this option to show an additional input field and supply the desired comparison value. Only those recipients are shown who have a profile value that is strictly after the specified value. Note: This comparison is performed directly on the database, so the database's ordering semantics apply.
• is after or equal to: Same as above, only with a non-strict comparison.
• starts with: Select this option to show an additional input field and supply the desired comparison value. Only those recipients are shown who have a profile value for the selected field that begins with the text you supply as comparison value.
• ends with: Select this option to show an additional input field and supply the desired comparison value. Only those recipients are shown who have a profile value for the selected field that ends with the text you supply as comparison value.
• contains: Select this option to show an additional input field and supply the desired comparison value. Only those recipients are shown who have a profile value for the selected field that contains the text you supply as comparison value at the beginning, the end, or anywhere in between.

Filtering on Email Addresses

For filtering on the email address field, the same rules as described for Standard Text Fields apply, with the additional restriction that the field is mandatory.

Filtering on Number Fields

• is not supplied: (Only available for optional fields.) Only recipients without a value for the selected profile field are shown.
• is supplied: (Only available for optional fields.) Only recipients with an actual value for the selected profile field are shown.
• is: Select this option to show an additional input field and supply the desired comparison number. Only recipients with the specified value for the selected profile field are shown.
• is not: Select this option to show an additional input field and supply the desired comparison value. Only those recipients are shown who have a profile value other than the specified number.
• is strictly less than: Select this option to show an additional input field and supply the desired comparison number. Only those recipients are shown who have a profile value that is strictly less than the specified number.
• is less than or equal to: Same as above, only with a non-strict comparison.
• is strictly greater than: Select this option to show an additional input field and supply the desired comparison number. Only those recipients are shown who have a profile value that is strictly greater than the specified number.
• is greater than or equal to: Same as above, only with a non-strict comparison.
• is between: This is a convenience option to supply a value range condition. When chosen, two input fields are shown. Please supply the lower and upper limit that you intend to use for the range condition. Only those recipients are shown who have a profile value that lies within the specified bounds (inclusively).

Filtering on Boolean Fields

• is "True": Only recipients with the value "True" for the selected profile field are shown.
• is "False": Only recipients with the value "False" for the selected profile field are shown.

Filtering on the "Tracking Permission" field

For filtering on the special "Tracking Permission" field, the same rules as described for Boolean Fields apply.

Filtering on Single-Value Selection Fields

• is not supplied: (Only available for optional fields.) Only recipients without a chosen entry for the selected profile field are shown.
• is supplied: (Only available for optional fields.) Only recipients with a chosen value for the selected profile field are shown.
• is: Select this option to show an additional drop-down menu and select the desired comparison entry. Only recipients with the specified entry chosen for the selected profile field are shown.
• is not: Select this option to show an additional drop-down menu and select the desired comparison entry. Only those recipients are shown who have not chosen the specified entry.
• contains any of: Select this option to show an additional multiple-select menu and select the desired comparison entries. (To select additional entries, hold down the CTRL key.) Only those recipients are shown who have chosen any one of the specified entries. (Note: This is a shortcut and also a more resource-efficient alternative method to using the "is:" variant multiple times and using the "any" choice for combination.)
• does not contain any of: Similar as above, only negated for convenience.

Filtering on Multiple-Value Selection Fields

• is not supplied: (Only available for optional fields.) Only recipients without any chosen entry for the selected profile field are shown.
• is supplied: (Only available for optional fields.) Only recipients with any chosen entry for the selected profile field are shown.
• contains the value: Select this option to show an additional drop-down menu and select the desired comparison entry. Only recipients with the specified entry among the entries chosen for the selected profile field are shown.
• does not contain the value: Select this option to show an additional drop-down menu and select the desired comparison entry. Only recipients with the specified entry not among the entries chosen for the selected profile field are shown.
• contains at least the values in the set (>=): Select this option to show an additional multiple-select menu and select the desired comparison entries. (To select additional entries, hold down the CTRL key.) Only those recipients are shown who have chosen all of the specified entries, but maybe also additional entries. In other words: The set of entries selected for the profile field is a superset of the given set of comparison entries.
• does not contain other values than those in the set (<=): Select this option to show an additional multiple-select menu and select the desired comparison entries. (To select additional entries, hold down the CTRL key.) Only those recipients are shown who have chosen one or more of the specified entries, but no other entries. In other words: The set of entries selected for the profile field is a subset of the given set of comparison entries.
• contains exactly the values in the set (=): Select this option to show an additional multiple-select menu and select the desired comparison entries. (To select additional entries, hold down the CTRL key.) Only those recipients are shown who have chosen all of the specified entries, and no other entries. In other words: The set of entries selected for the profile field is the same set as the given set of comparison entries.
• contains at least one of the values in the set (&): Select this option to show an additional multiple-select menu and select the desired comparison entries. (To select additional entries, hold down the CTRL key.) Only those recipients are shown who have chosen at least one of the specified entries, but maybe also additional entries. In other words: The set of entries selected for the profile field has a non-empty intersection set with the given set of comparison entries. (Note: This is a shortcut and also a more resource-efficient alternative method to using the "contains the value:" variant multiple times and using the "any" choice for combination.)

Filtering on Date Fields

• is not supplied: (Only available for optional fields.) Only recipients without a value for the selected profile field are shown.
• is supplied: (Only available for optional fields.) Only recipients with an actual value for the selected profile field are shown.
• is at the given day: Two variants are offered:
  • supplied explicitly: Supply the desired comparison day by selecting from the calendar widget which opens automatically when you click into the input field.
  • supplied relative to today: Supply the number of days and select if you want LISTSERV Maestro to determine the actual day by looking into the past (choose "before today") or the future (choose "after today"). Note: Contrary to "supplied explicitly" above, this is a dynamic comparison value which is determined just-in-time when LISTSERV Maestro evaluates the condition, so the actual day changes when time progresses.
  With each of the variants above, LISTSERV Maestro is given a value that is used for comparison with the actual recipient's profile value. Only those recipients are shown who have this value in the field that the condition is defined for.
• is at or after the day: Similar to above, only that also recipients are shown whose field value is after the comparison day. Note: LISTSERV Maestro compares the field value and the comparison day with proper temporal semantics and not with simple textual comparison, so that "after" correctly means "later in time".
• is at or before the day: Similar to above, only with "before" instead of "after".
• is in the range of days: Four variants are offered:
  • supplied explicitly: See "is at or before the day" and "is at or after the day" above: This choice is a short-hand method to using these two options and combining them with "and", yielding a range comparison with explicitly given boundary days.
  • supplied relative to today: See "is at or before the day" and "is at or after the day" above: This choice is a short-hand method to using these two options and combining them with "and", yielding a range comparison with boundary days supplied as a "rolling window" following the progress of "today" during time.
  • supplied relative to this week: This special filtering option allows you to limit the desired field value with a week-relative rolling window. Supply the "From" and "To" boundaries by selecting from the drop-down menus. Note: For this type of condition, LISTSERV Maestro looks at a setting from your user interface preferences, namely your choice for "Week Starts On". This is used to calculate the number of weeks between a day supplied as profile field value and "today", which in turn decides if a recipient is shown or not.
  • supplied relative to this month: This filtering option allows you to limit the desired field value with a month-relative rolling window. Supply the "From" and "To" boundaries by selecting from the drop-down menus. Note: For this type of condition, LISTSERV Maestro uses calendar logic to determine the months into which the day given as profile field value and "today" fall. This is used to decide if a recipient is shown or not.
• marks an anniversary at the given day: See the discussion about anniversaries below. Available options are:
  • supplied explicitly: Select the desired comparison month/day from the drop-down menus.
  • supplied relative to today: Same as the "supplied relative to today" variant of the "is at the given day" option above.
• marks an anniversary in the range of days:
  • supplied explicitly: For "From" and "To": Select the desired comparison month/day from the drop-down menus. Note: It is perfectly valid to for example select a day in November for "From" and a day in January for "To", LISTSERV Maestro then checks the upper boundary by using one year in the future instead of the current year.
  • supplied relative to today: Same as the "supplied relative to today" variant of the "is in the range of days" option above.
  • supplied relative to this week: Same as the "supplied relative to this week" variant of the "is in the range of days" option above.
  • supplied relative to this month: Same as the "supplied relative to this month" variant of the "is in the range of days" option above.

Filtering on Birthday Fields

For filtering on birthday fields, the the filtering options as described for Date Fields are avalable. Additionally, the following options are available:

• defines the age: Supply the age in years. Only those recipients are shown whose field value defines a day that is the supplied number of years in the past.
• defines an age greater or equal to: Same as above, but also includes recipients whose field value defines a day that is the supplied number of years or more in the past.
• defines an age less than or equal to: Same as above, but also includes recipients whose field value defines a day that is the supplied number of years or less in the past.
• defines an age in the range: Supply the "From" and "To" age in years. Only those recipients are shown whose field value defines a day that is an amount of years in the past that falls in the supplied range (inclusively).

Filtering on the Subscription Date

Filtering on the subscription date is very similar to filtering on other Date Fields. However, since subscription dates are by their nature always in the past, the "relative to" variants only support supplying limits in the past.

• is at the given day: See Date Fields.
• is at or after the day: See Date Fields.
• is at or before the day: See Date Fields.
• is in the range of days: See Date Fields.

Filtering on Anniversaries vs. Filtering on Full Dates

LISTSERV Maestro allows you to view the date in the profile field value as a "historic day". For such days, questions like "When do we celebrate the next anniversary for this day?" or "When did we celebrate the last anniversary for this day" make sense. Typical for such anniversaries is that they occur once each year, repeatedly. Applied to profile fields with variable date values, this allows you to match recipients ignoring the "year" component of the date value. Contrary to this, when using any of the other options when filtering on date fields, the full date including the year component is taken into account.

Examples

You are running a used and vintage cars online store and are using LISTSERV Maestro to manage the subscriber data. Your subscriber list contains the following fields:

• The standard email address field.
• CAR_MODEL: A single-select field with a corresponding lookup table.
• BUILD_DATE: A birthday field, stores the day when the car was manufactured.
• PURCHASE_DATE: A date field, stores the day when the car was purchased.
• The standard subscription date field.

The following sections describe how LISTSERV Maestro allows you to accomplish the following tasks, starting with first showing the full, unfiltered list of recipients:

"Show me last week's new subscriptions"

You add a filter on the "Subscription Date" field. You add a condition and choose "is in the range of days", then you choose "supplied relative to this week". Then you supply "previous week" for "From: Start of..." and "previous week" for "To: End of...". After applying, you see the desired result.

"Show me all recipients whose car maintenance is due next month"

You are planning to send out a reminder-type newsletter to those recipients whose cars should be brought in for maintenance, reminding them roughly one month ahead. For this, you work with anniversary-type filtering on the BUILD_DATE field. Add a filter on this field, add a condition and choose "marks a birthday in the range of days" and then "supplied relative to this month". For "From:" and "To:", you choose "next month". The resulting list of recipients contains owners of cars of any age but only those whose month/day part falls into the month after "today".

"Show me all recipients who purchased a "Model X" with a build date between January 1st. and April 31st. 2000"

You have been notified by the manufacturer of "Model X" that all cars built in this range require a special, free-of-charge maintenance, to be performed in your garage. So you need a list of the matching recipients. Add a filter on the CAR_MODEL field, add a condition with "is" and select "Model X" from the drop-down menu. Apply the condition. This gives you a list of "Model X" owners. Now you add an additional condition on the BUILD_DATE field, choosing "is in the range of days" and "supplied explicitly". For "From" you supply January 1st., 2000 and for "To" you supply April 31st, 2000. Apply the condition.

"Show me all recipients who purchased a vintage car last month"

You plan to send a repeated monthly newsletter to vintage-car fans, but would like to restrict the list to recent buyers, outlining special tips and tricks that would not be interesting for recipients who already own the car for a longer time. A car is called "vintage" if it is older than 20 years, so you begin with adding a condition on the BUILD_DATE field: Add a condition using "defines an age greater than or equal to" and supply 20 for "From: ... years". Apply the condition to see the list of all vintage-car owners. Now you need to restrict this to the purchases of last month: Add a condition on the PURCHASE_DATE field, select "is in the range of days". Choose "relative to this month" and select "previous month" for "From: Start of ..." and "To: End of ...". Apply the condition.

Creating a Mail Job from Your Subscriber List

Regardless of whether you have defined a filter on the list or not, the "Edit" menu contains items that allow you to create a mail job (or A/B split job) from the list that you are currently viewing. The resulting mail job is created with a ready-made (i.e. "green") recipients definition. In the recipients definition, your filter settings (if defined) are already applied. Important: As is normal for the recipients type "Send to a List or Dataset in the Subscriber Warehouse", the list of recipients for the resulting mail job is determined just-in-time before delivery, which means that the recipients you have viewed before creating the mail job can (and in many cases will) be different from the recipients actually included in the mail job.

If you instead want the mail job to actually include the recipients that you are seeing now in the list, you have to first download the data (see above on how to do this) and manually create a mail job with recipients of the type "Uploaded Recipients". However, we strongly recommend against this because subscribers may have unsubscribed or may have changed their subscription profile in such a way that they no longer want to be (and should not be) included in future mail jobs.

Editing the Subscriber Subset of a Mail Job or A/B Split Job

If you are working on a mail job with recipients of the type "Send to a Subscriber List or Dataset" (regardless of whether the job was created from scratch or via the method above starting with a filtered subscriber list), then the "Source Details" page of the recipients wizard has a link Subset Details. Clicking this link opens a special variant of the subscriber list that is used to edit the filter settings of the recipients definition. Contrary to the standard variant, the screen shows additional buttons at the bottom right: [Use as Recipients: All Active Subscribers / Filtered Subscriber Subset] (depending on if you have a filter active or not) and [Cancel]. Define and/or change your filter settings just as described above and click the [Use as Recipients] button to apply your changes to the mail job recipients definition, the change is reflected in the recipients wizard.

Editing the Subscriber Subset of a Target Group

If you are working on a target group of the type "Based On Subscriber Dataset" or "Based On Subscriber List", then the "Source Details" page of the target group wizard has a link similar to the one described above, clicking this link also opens a special variant of the subscriber list that is used to define the filtering condition of your target group.

Filtering Conditions and Target Group Parameters

Adding an entry to the filtering conditions of a target group (via the subscriber list page) usually also means that a potential parameter is available for the target group. There are only few exceptions to this, for example the filtering options "is supplied" and "is not supplied" are treated as "constant" and do not constitute a potential parameter. To help you understand which of the condition elements are potential parameters, the filtering condition popup dialog highlights the corresponding parts of the condition already when you define them.

After applying the filtering condition via the button on the bottom-right of the screen, the target group definition is updated according to your changes and the "Parameters", the "Input Layout" and the "Input Preview" pages of the target group wizard allow you to change the various settings of a potential parameter (such as for example to declare that the corresponding condition element is fixed, which effectively removes the parameter from the target group, or to define a description or to re-arrange the parameter presentation sequence).