Choose the right filter operator

Make each condition say exactly what you intend

After you choose a Field, CAB limits the Operator list to choices supported by that Salesforce field type.

Operator reference

Field kind	Operators shown in CAB	Notes
Text, Email, Phone, URL, Text Area	Equals, Does Not Equal, Is Empty, Starts With, Ends With, Contains, Does Not Contain	Text comparisons use the entered string.
Number, integer, currency	Equals, Does Not Equal, Is Empty, Greater Than, Less Than, Less Than or Equal, Greater Than or Equal, Between	Between accepts a lower and upper bound.
Percent	The comparison operators above, except Between	Enter the value as CAB presents it for the Salesforce percent field.
Date and Date/Time	The number-style comparison operators, including Between	Switch between a calendar value and a relative date.
Time	Equality, emptiness, and greater/less comparisons	Between is not offered for Time fields.
Picklist	Text-style operators	Equals and Does Not Equal use picklist choices; text-style matching is also available.
Multi-Select Picklist	Equals, Does Not Equal, Is Empty, Includes, Excludes	Use Includes/Excludes for individual stored selections.
Lookup, ID	Equals, Does Not Equal, Is Empty	Search for one or more Salesforce records instead of typing raw IDs.
Checkbox	Equals, Does Not Equal	The value is true or false.
Location	Is Within, Is Not Within	Configure a radius and point. See Filter by distance from a location.

With Is Empty, set Value to true to match blank/null values or false to match populated values. “Empty” is a null check; it is not the same as searching a text field for a space.

For Multi-Select Picklist fields, Includes and Excludes remain distinct from Equals and Does Not Equal. CAB preserves that distinction when Cabby authors the condition, when the condition is stored in a Filter Library module, and when a configured copy is added to an audience.

For Picklist and Lookup fields, selecting several values uses OR with Equals and AND with Does Not Equal. Between includes both From and To; the To value must be larger than the From value. For a Date/Time field, comparisons use the calendar-date portion rather than the time of day.

Use relative dates

For a Date or Date/Time condition, select Use relative date. The field changes to Enter a relative date…. Supported patterns include:

• YESTERDAY, TODAY, or TOMORROW;
• LAST WEEK, THIS MONTH, or NEXT FISCAL QUARTER;
• LAST 30 DAYS or NEXT 2 WEEKS;
• 90 DAYS AGO.

Relative input is case-insensitive. Between uses two calendar-date inputs rather than relative expressions. Select Use calendar date to return to a fixed single value.

Fixed and relative dates answer different questions

A calendar date keeps the same boundary every time the audience runs. A relative date moves with the run date, which is usually appropriate for a recurring audience such as “created in the last 30 days.”

Combine several conditions

Under Filter Records where, choose All Conditions Are Met, Any Condition Is Met, or Custom Logic Is Met. Custom logic accepts condition numbers, AND, OR, NOT, and parentheses without regard to case. Reference every condition, group mixed AND/OR, and parenthesize negation—for example, (NOT 1) or (NOT (1 OR 2)).

Connected object branches have their own Related Object Filter Logic; see Combine related-object filters with custom logic.

Test exclusions with a small example

Negative operators and NOT can interact with empty values differently from a positive match. Add an explicit Is Empty condition when null handling matters, then use the audience test and a sample Record Match Breakdown before activation.

Large-data-volume diagnostics

CAB flags Contains, Does Not Contain, Ends With, Does Not Equal, Excludes, and “Is Empty = false” as potentially non-selective. This does not make them invalid; use Audience Query Diagnostics when a large audience is slow. Running an object with no conditions also produces No field filters because it can scan a large part of the object.