Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Designing Criteria Segments by using a rule form (deprecated)

Updated on August 4, 2022

In this approach, you provide a series of criteria by identifying the appropriate column, the relationship type, and the value for which to search. These criteria are then combined in the Filter conditions field to allow the user to describe the logic for applying the various criteria.

Pega Customer Decision Hub
Note: This approach to designing Criteria Segments is deprecated. If possible, design all Segments using the standard approach. For more information, see Designing Criteria Segments.
  1. On the Design tab of a Criteria Segment, click the rule form icon .
  2. In the rule form, click Add filter.
  3. In the Column source field, enter or select the property which you want to use as a criterion.
  4. In the Relationship list, select the operation that evaluates the property and value.
  5. In the Value field, enter the required value of the property.
  6. Use the gear icon to add filter options, such as Ignore case and Use null if empty.
  7. In the Filter conditions to apply field, define the relationship between the criteria. By default, the criteria are applied with an AND logic. If needed, you can change the relationship between some criteria to OR.
  8. Optional: Select other Segments as criteria within this Segment. Selecting a Segment criterion automatically includes or excludes all customers in that Segment.
    1. In the Segments section, click Add Segment.
    2. Select the Segment from the SEGMENT NAME  list.
    3. In the IN / NOT IN  list, select whether the new Segment evaluates customers who are in or not in the existing Segment.
    4. In the Filter Segments field, define the relationship between the Segments.
  9. Click Save.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us