Overview
Constraints are the specific values of properties used to search for people and create Segments. Constraints vary depending on the type of field you select (and whether it is a text field, text area, dropdown, date, or other field type).
Below, we cover each type of field and the operators that apply.
String
The field contains letters and numbers describing the value. Examples include name, email address, and country.
The following operators apply to string fields:
Contains | The user's field has the value in at least part of the field |
Does Not Contain | The user's field does not contain the value in any part of the field |
Exists | The user has a value in this field.
Useful for finding users who have fields that are only generated in certain ways, such as email clicks or landing pages. |
Does Not Exist* | The field does not exist for the user
|
Starts With | The user's field starts with the value
|
Does Not Start With | The user's field does not start with the value
|
Ends With | The user's field ends with the value |
Does Not End With | The user's field does not end with the value |
Is Not | The user's field is not exactly equal to the value |
Regexp | Create a regular expression to compare against the user's field |
The Does Not Exist operator can't be used in Activity, Document, or Decision filters to identify missing data. Instead, 
The Starts With operator supports multiple values. For instance, you can filter last names starting with A, B, and C by entering “[A-C]”. To filter non-sequentially, separate values with commas (e.g., [A,D,G]). Note on Text Area Fields
Text area fields store long-form text (such as essay responses or personal statements) and follow the same string format. However, because their content can be quite large, only the Exists and Does Not Exist operators are supported.
✨ Pro Tip: This is especially useful when filtering or segmenting on text area fields used in Decision checklist conditions.
List
List fields are made up of limited choices that the user could select from, such as terms and applications (or any dropdown fields you have in Field Management).
When filtering for these fields, you are given a list of options to choose as values. Multiple conditions may be added to list field filters.
The following conditions apply to list fields.
Is | The value matches the user's field |
Is Not | The value does not match the user's field |
In | The user's field matches any of a number of choices in the value. You are able to select more than one choice using "In." |
Not In | The user's field does not match any of the values chosen |
Date
Date fields contain data on when a user completed an action, such as submitting an application or survey, or their birth date. The When Operator is the most important aspect of Date fields. This operator can be relative or exact.
Relative
Relative dates are measured from a certain point relative to the present. They are built using this format: "From X to Y days/weeks/months/years ago."
To use this filter, you would fill in the following fields:
From | Number of days/weeks/months/years |
To | Number of days/weeks/months/years |
Ago | Select days/weeks/months/year |
Exact Dates
Exact dates are measured with a start and end date, each with a day, month, and year.
Geo
Geo fields allow you to filter by the distance from a given point.
The following operators are used for geo fields:
Address | The address from which to measure. Beginning to type here will bring up an auto-complete using Google Maps to assist you in finding the exact address. |
Value | The number of miles/kilometers you would like to set as a maximum distance from the chosen address |
Unit | Choose to measure in miles or kilometers |
Now that you're familiar with constraints put them to use by learning how to create a segment.