Creating a volume constraint
In situations where a customer is eligible for multiple actions, you may specify whether volume constraints should be applied to the actions as a group, or whether each action should be evaluated separately. Evaluating actions as a group allows Pega Customer Decision Hub to display all eligible actions, for example to a customer service representative, who should be able to see all the actions they can make to the customer.
Pega Customer Decision Hub
The two options available are:
- Constrain each action individually - Select this option to check
each action or action bundle for the customer separately against applicable channel and
action constraints. In this way, the highest priority action or actions for a customer may
pass constraint checks, while lower priority actions may be rejected, for example due to
volume constraints.
Note: If the marketing Strategy pushes out multiple actions for a customer, these actions should be prioritized in the Strategy since the highest priority action (based on the pxPriority field) will be made to the customer. - Constrain as a group for the customer (output all actions) -
Select this option to use the highest priority action to apply constraints on the channels
and actions, without removing the other actions for a customer. If the highest priority
action is allowed to pass the constraint, all lower priority actions for this customer are
also allowed without applying separate constraint checks. In this way, all eligible
actions for a customer can be displayed.
Note: You can automatically apply the setting Constrain as a group for the customer (output all actions) to all volume constraints in all the campaigns in your application. To do this, edit the Dynamic System Setting MKTConstraintAsGroup and set its value to true. If the value of the setting is set to true, the two customer volume constraint options are no longer displayed when you edit a volume constraint.
Previous topic Avoiding overexposure of actions with volume constraints Next topic Using volume constraints with action bundles