Docs / Introduction / 

Segmentation rules

Segmentation rules

In Able CDP, the 'Rules' section of the dashboard is a powerful feature that enables you to manage how events are processed. By setting up rules, you can transform or filter events based on specific criteria. This documentation will guide you through the process of creating and managing rules within your Able CDP dashboard.

Creating a Rule

To begin configuring a rule, navigate to the 'Rules' section in the dashboard. Here, you can define the following components for each rule:

1. Rule Priority

  • Function: Determines the order in which rules are applied when an event matches multiple conditions.
  • Configuration: Assign a numerical value to set the priority; lower numbers indicate higher priority.

2. Conditions

  • Function: Define the criteria that an event must meet for the rule to be applied.
  • Configuration Options:
  • All conditions must match: Uses the AND logical operator to ensure all conditions are met.
  • At least one condition must match: Uses the OR logical operator where meeting any of the conditions is sufficient.

Each condition includes:

  • Field Name: Use standard Able CDP event field names (e.g., deal_value, event_type), including nested fields separated by dots (e.g., lead.form_name).
  • Operator: Choose from 'equal', 'not equal', or 'regexp':
  • Equal/Not Equal: Compares the field value with the comparison string. Note that numerical fields treat empty strings, 0, and 0.0 as equivalent.
  • Regexp: Utilizes regular expressions enclosed in forward slashes (e.g., /^test/). Options like 'i' for case-independent, 'm' for multiline, and 'x' for extended syntax can follow the closing slash.

3. Actions

  • Function: Determines what happens when an event matches the rule conditions.
  • Types of Actions:
  • Ignore: Discontinues all processing for events matching the rule.
  • Fill Values: Specifies fields to be added or overwritten. Use dot notation for nested fields (e.g., { "lead.formName": "Y" }).

Common uses include changing the event_type based on a condition or adding UTM or custom parameters to the event data.

Example Use Case: Ignoring $0 Purchases

To create a rule that ignores events with a $0 purchase value, you would:

  1. Set the rule priority to ensure it is evaluated in the correct order.
  2. Configure conditions:
  3. Set the first condition to deal_value equal 0.0.
  4. Set the second condition to event_type equal Purchase.
  5. Set the action to ignore.

This setup ensures that only purchase events with a deal value of $0 are ignored.


Setting up rules in Able CDP allows for fine-grained control over event processing, enabling more accurate data analysis and reporting. By carefully defining rule priorities, conditions, and actions, you can ensure that your event data is handled efficiently and effectively.

For more complex needs, Able CDP has an API that allows to forward all inbound events to an HTTP endpoint that can modify or reject each event arbitrarily, as well as replace or add additional events. Contact us if you require access to this functionality.