Create Standard Rule

Matching Empty or Non-Existent Fields

Standard Segmentation Rules can match both empty (blank) or non-existent (NULL) custom fields. This is done using the "Equals/Not Equals" operators for blank fields, and "Null/Not Null" operators for non-existent fields. For example, to find contacts that have no data stored in the field "weekly", define the command:

custom_weekly Is Null OR custom_weekly Equals _____ (blank value)

This checks if the field does not exist or, if it does exist, is empty.

To find all non-empty fields, define the command:

custom_weekly Is Not Null AND custom_weekly Not Equals _____ (blank value)

This checks if the field exists and, if it does exist, is not empty.

This is an important difference between the prior and new Standard segmentation, due primarily to improvements in data storage.  When you add or import contacts, custom data fields are not always filled or created if the data is blank or empty.  For instance, if a field is blank in your import file and you import with the SmartSubscribe option, a blank custom field is added.  However, if you do not use SmartSubscribe, the custom field is not created.  If a field is not filled on import or save, then it essentially does not exist.  When you search for contacts, you must take into account fields where data exists vs. fields that don't exist at all. 

For example, if you want to search for contacts who do not want to receive the monthly version of your email (custom_monthly != 1), in Standard segmentation, your rule would look like:

custom_monthly != 1 or custom_monthly Is Null

The operator 'Is Null' finds all contacts that have never had data stored for the field, and '!= 1' finds all contacts that have data stored, but it is not the number 1, meaning it could be blank, or 0, or a string like NO.

As of Version 16.00 (January 14, 2021), customers using new custom fields in segmentation rules where the Operator is Not Equal, Not Like or Not In, will experience a change in how we calculate the results of the rule. This will have no effect on old Custom fields. Currently, if a rule has a “Not” operator, it will specifically calculate everyone who meets the criteria but wouldn’t calculate anyone with a null value. As an example, if you have the following segment rule: 

List of Values

Most Operators allow only one Value per condition. With the 'IN' and 'NOT IN' operators, you can enter a list of possible values, including a blank value. These operators act as a group of OR conditions in a single definition.

For example, to find all contacts who live in Washington OR Oregon OR Idaho OR California, use the following:

state IN WA,OR,ID,CA

To define the list of Values, select a Field and then the 'IN' and 'NOT IN' operator. Click to select the Value field and enter each value separated by a comma (WA,OR,ID,CA).

Range***

Zip Code Range field allows you to query for contacts within a mile range of a specific zip code.  Drag the Zip Code Range field to the workspace, then select a Mile range from 5 to 100 miles (in 5 mile increments).  Enter a single 5-digit Zip Code in the Value field.  

To search within a range of multiple zip codes, use the OR condition type and group the Zip Code Range queries together.  

***Zip Code Range in 11.2 and up

Predefined Values

While most fields require you to enter a value, the Date: Month of, Subscription Format, and Tracking Event Type fields provide a list of options based on the values allowed for the default fields.

Subscription Format

Plain Auto is the default format when you import contacts to a list and do not define the contact selected format. It acts the same as Plain Text when sending a campaign, but is used to differentiate between contacts that have chosen to receive Plain Text versus contacts who have not selected a preferred format. When segmenting based on Format, if you want to find all contacts who will receive Plain Text messages, create a condition that checks for Subscription Format IN Plain Auto, Plain Text.

Subscription Format options include:

Tracking Event Type

Tracking Event Type options include:

**Note: Tracking_Event_Type Not Equals will return 0 results.  To search for contacts who have NOT performed an event, use Advanced Segmentation or Remarketing.