A Standard Segmentation Rule allows you to easily create a rule to search for contacts based on one or more conditions, matching all or any of the defined conditions. Standard Segmentation Rules work with fields of type Number, Float, Date, and Text. Conditions using Number, Float, and Text fields require three settings: Field, Operator, and Value. Date Fields have an additional sub-type to help segment based on parts of a date (Day, Month, Year) or anniversaries.
To add a Standard Segmentation Rule
- Go to LISTS > SEGMENTATION > CREATE STANDARD RULE.
For versions after 9.8.0, go to LISTS > SEGMENTATION > VIEW SEGMENTATION RULES, then click the arrow next to Add Rule, and select Add Standard Rule - Old.
- Click the arrow next to Add Rule, and select Add Standard Rule.
- Enter a Name.
- Enter an optional Description.
- Select a Condition Type (AND, OR, NOT) and then define one or more conditions
- Select a Field
- For a Date field, select the Sub-Type
- Select a comparison Operator
- Enter a Value
- Click Add Condition to add another condition and repeat as needed.
- Select a list to Test Against for validation, then click TEST to run the test
- Click SAVE to save the new rule. Click CANCEL to return to the Segmentation Rules page without creating the new rule.
Parts of a Condition
A segmentation rule condition is composed of at least one field and operator and can also include one or more values.
Standard rules support three types of conditions:
|AND||Find only contacts that match all defined conditions|
|OR||Find any contacts that match any defined condition|
|NOT||Find only contacts that do NOT match the defined conditions|
The Field listbox displays the five most used fields by default. To view all Contact and Custom Data field options, click the Field listbox and then click MORE. If you want to change the fields displayed when you click the Field listbox, you can Pin the fields to the list. In the PIN column, select the fields you wish to display in the listbox, then click SELECT.
In the Field selector, the fields are sorted by Name. You may also sort by type by clicking the column header. Only Custom Fields of type Number, Float, Date, and Text are available for segmentation.
To select a field, find it in the list by scrolling or using the Filter box. Typing into the filter box will weed out Fields that do not match the text string entered. This is very helpful when you have many custom fields. Click to select the Field and then click SELECT to select the field for the condition.
The following Fields are available for segmentation:
|Contact Data Fields||Type||Sample or Description|
|Text||Contact's email address|
|First Name||Text||Contact's first name|
|Last Name||Text||Contact's last name|
|Company||Text||Contact's company name|
|Address||Text||First line of contact's street address|
|Address 2||Text||Second line of contact's street address|
|Zip||Text||Contact's zip or postal code|
|Phone||Text||Contact's phone number|
|Fax||Text||Contact's fax number|
|Created Date||Date||Date contact record was created|
|Updated Date||Date||Date contact record was updated|
|Subscribed Date||Date||Date contact was added to a List|
|Subscription FormatType||Number||Format contact is set to receive (see below)|
|custom_[field_name]||Number, Float, Date, or Text||Custom fields are prepended by 'custom_' to distinguish them from default Contact Data fields|
|Tracking Data Fields||Type||Sample or Description|
|Date Campaign Last Sent||Date||Date contact was last sent a campaign message|
|ID of Campaign Last Sent||Number||Identification of the last campaign sent to contact|
|Tracking Campaign ID||Number||Identification of the campaign associated with tracked event|
|Tracking Event Date||Date||Date contact performed a tracked event|
|Tracking Event Type||Number||Type of event contact performed.|
|Tracking List ID||Number||Identification of the list associated with tracked event|
|Tracking Data Browser Fields*||Type||Sample or Description|
|Browser/Device (clicks) - Browser||Text||Name of browser associated with the click-through event|
|Browser/Device (clicks) - Campaign ID||Number||Identification of the campaign associated with clcik-through event|
|Browser/Device (clicks) - Client Type||Text||Name of software client displaying click-through event|
|Browser/Device (clicks) - Event Date||Date||Date contact performed click-through event|
|Browser/Device (clicks) - List ID||Number||Identification of the list associated with click-through event|
|Browser/Device (clicks) - OS Name||Text||Name of Operating System displaying click-through event|
|Browser/Device (opens) - Browser||Text||Name of browser associated with the open event|
|Browser/Device (opens) - Campaign ID||Number||Identification of the campaign associated with open event|
|Browser/Device (opens) - Client Type||Text||Name of software client displaying open event|
|Browser/Device (opens) - Event Date||Date||Date contact performed open event|
|Browser/Device (opens) - List ID||Number||Identification of the list associated with open event|
|Browser/Device (opens) - OS Name||Text||Name of Operating System displaying open event|
|Conversion Tracking Data Fields**||Type||Sample or Description|
|Conversion Campaign ID||Number||Identification of the campaign associated with Conversion Tracking Event|
|Conversion Email Address||Text||Email address of contact who performed Conversion Tracking Event|
|Conversion Event Description||Text||Description of Conversion Tracking Event|
|Conversion Event Details 1||Text||Details of Conversion Tracking Event|
|Conversion Event Details 2||Text||Details of Conversion Tracking Event|
|Conversion Event Details Number||Float||Number or Price for Conversion Tracking Event|
|Conversion Event Name||Text||Name of Conversion Tracking Event|
|Conversion Other ID||Text||Alternate Details of Conversion Tracking Event|
|Conversion Referenced URL||Text||URL from which Conversion Tracking Event was launched|
|Conversion Referenced URL Parameter||Text||Parameters of URL from which Conversion Tracking Event was launched|
|Conversion Event Date||Date||Date of Conversion Tracking Event|
*Browser Tracking in 8.4 and up
**Conversion Tracking in 8.7 and up
A comparison operator is the test to perform against the selected field and the value you provide. Not all operators work with every field type. The 'LIKE' and 'NOT LIKE' operators compare a Text field to a text string. These operators require a string value that includes a percent symbol ( % ) to act as a wild card for searching.
The following table defines each operator and the supported field types:
|IN||Float, Number, Date, Text||Is the field included in the list of values? This is like creating several OR conditions with one condition.|
|NOT IN||Float, Number, Date, Text||Is the field not included in the list of values? This is like creating several AND NOT conditions with one condition.|
|=||Float, Number, Date, Text||Is the field equal to the value?|
|!=||Float, Number, Date, Text||Is the field not equal to the value?|
|>||Float, Number, Date||Is the field greater than the value?|
|<||Float, Number, Date||Is the field less than the value?|
|>=||Float, Number, Date||Is the field greater than or equal to the value?|
|<=||Float, Number, Date||Is the field less than or equal to the value?|
|LIKE||Text||Is the field like the text string? Contains: %string% Begins With: string% Ends With: %string|
|NOT LIKE||Text||Is the field not like the text string? Does Not Contain: %string% Does Not Begin With: string% Does Not End With: %string|
|IS NULL||Float, Number, Text, Date||Is the field NULL, or does it not exist?|
|IS NOT NULL||Float, Number, Text, Date||Is the field not NULL, or does it exist?|
A Value is required for all conditions except those using the 'IS NULL' or 'IS NOT NULL' operators. If a value is missing or incorrectly formatted, the field will appear with a red outline. Mouse over or click in the field to display a tool tip with information on how to correct the issue. If you attempt to save with invalid settings, an error will occur and allow you to make corrections before saving.
Each field type expects a value to match that type. Dates also require sub-types and a matching value pair.
|Text||string of characters|
|Date||Value of||date in format mm/dd/yyyy|
|Date||Day of||integer from 1 to 31|
|Date||Month of||integer from 1 to 12 or List (see below)|
|Date||Year of||four digit integer|
|Date||Days between, End Date||date in format mm/dd/yyyy|
|Date||Days between, Value||-/+ integer|
|Date||Days between anniversary of, End Date||date in format mm/dd/yyyy|
|Date||Days between anniversary of, Value||-/+ integer|
|Date||Months between, End Date||date in format mm/dd/yyyy|
|Date||Months between, Value||-/+ integer|
|Date||Months between anniversary of, End Date||date in format mm/dd/yyyy|
|Date||Months between anniversary of, Value||-/+ integer|
|Date||Years between, End Date||date in format mm/dd/yyyy|
|Date||Years between, Value||-/+ integer|
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, which changes to allow a list of values. Enter a value, then press ENTER on the keyboard to add it to the list and continue entering values. Click SAVE LIST to save the list of values. They will appear in the Value field as a comma separated list.
To add a blank value to the list, just press ENTER. To delete a value from the list, click the X next to the item.
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. However, for 'IN' and 'NOT IN', you must enter the Value String or the Value Number exactly as defined below.
Date: Month of options include:
|January||1||Also accepted: Jan, jan|
|February||2||Also accepted: Feb, feb|
|March||3||Also accepted: Mar, mar|
|April||4||Also accepted: Apr, apr|
|May||5||Also accepted: May, may|
|June||6||Also accepted: Jun, jun|
|July||7||Also accepted: Jul, jul|
|August||8||Also accepted: Aug, aug|
|September||9||Also accepted: Sep, sep|
|October||10||Also accepted: Oct, oct|
|November||11||Also accepted: Nov, nov|
|December||12||Also accepted: Dec, dec|
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:
|Plain Auto||0||Default subscription format, Sends Plain Text message|
|Plain Text||1||Plain text with no formatting|
|Multipart MIME||99||Merged Plain Text and HTML|
Tracking Event Type
Tracking Event Type options include:
|Sent Message||9||Message was sent to contact. Track Sends must be enabled in the realm. Only available on Broadcaster systems.|
|Read (Open) Message||10||Contact read or opened message|
|Clicked on URL||11||Contact clicked a URL in message|
|Subscribed||20||Contact opted in to subscribe to a list|
|Unsubscribed||21||Contact opted out of a list|
|Globally Unsubscribed||22||Contact opted out of all lists in the realm|
|Universally Unsubscribed||23||Contact opted out of all lists in the system. Only available on SMB systems.|
|Soft Bounce||30||Message bounced back as Soft Bounce|
|Hard Bounce||31||Message bounced back as Hard Bounce and opted out|
|Complaints||34||Contact reported the message as abuse or junk|
|Block Bounce||36||Message bounce back as a Block Bounce|
|Display Message||40||Contact clicked to display message in a browser|
|Display Message: Video||42||Contact clicked to display Video message. Video integration must be enabled on the realm|
|Display Message: Mobile||43||Contact clicked to display message in a mobile browser|
|FTAF||50||Contact clicked to forward the message to a friend|
|FTAF (Anon)||51||Anonymous user clicked to forward message to a friend|
|Sent Message (one-off)||70||Message was sent to contact via API single message. API must be enabled on the realm|
|Sent cc Message (one-off)||72||Message was sent to contact via API single message carbon copy (CC). API and CC must be enabled on the realm|
|Cart Abandonment||121||Contact abandoned a cart tracked with analytics. Analytics integration must be enabled on the realm|
|Product Purchases||122||Contact purchased a product tracked with analytics. Analytics integration must be enabled on the realm|
|Product Views||123||Contact viewed a product tracked with analytics. Analytics integration must be enabled on the realm|
|Video Played 0%||131||Contact started playing a video. Video integration must be enabled on the realm|
|Video Played 25%||135||Contact played video 25% through. Video integration must be enabled on the realm|
|Video Played 50%||136||Contact played video 50% through. Video integration must be enabled on the realm|
|Video Played 75%||137||Contact played video 75% through. Video integration must be enabled on the realm|
|Video Played 100%||138||Contact finished playing a video. Video integration must be enabled on the realm|