Released: February 18, 2026
Text area fields can now be used in segmentation filters. Previously, text area fields could not be used in checklist conditions or other segment-based logic, limiting their usefulness in workflows and targeting.
With this update, users can now apply “exists” and “does not exist” filters to text area fields. This enables segmentation based on whether a field contains any value, unlocking new use cases for conditional logic, reporting, and checklist configuration.
Due to the potentially large size of content stored in text area fields, more advanced and processing intensive filters such as “contains,” “starts with,” and “ends with” are not supported to maintain system performance and reliability.
New filter support for text area fields in segmentation
“Exists” condition to identify records where a text area field contains any value
“Does not exist” condition to identify records where a text area field is empty
Checklist condition compatibility allowing text area fields to be used in checklist-based logic
This update removes a key limitation when working with text area fields. Users can now incorporate these fields into segments enabling more flexible workflows and improved targeting.
