Priority Thresholds are a means of setting a minimum value for the calculated priority below which actions or treatments will not be considered for arbitration.
Such thresholds can be set in a hierarchical fashion with more granular values taking precedence, the hierarchy is shown below.
So, for example, if a threshold of 0.6 is set for the Outbound direction, and 0.7 is set for Outbound and the Email channel, 0.7 would be used for Email, and 0.6 for any other outbound channel that had not been explicitly set.
Propensity Threshold concepts
The thresholds are maintained in the Priority Thresholds DDR containing the properties described below. Only the relevant properties are shown.
|A user-friendly name for a threshold.
|Priority Thresholds are defined separately for Outbound or Inbound directions. If this is blank, then the same thresholds are applied to both Outbound and Inbound.
|The channel to which the Priority Threshold is to be applied. If this is blank, then the threshold is applied to all channels, however, if any channel is specified, then only channel specific thresholds will be applied, and all thresholds with a blank channel will be ignored.
|The issue to which the threshold is to be applied. If this is blank, then the threshold is applied across all issues.
|This is only referenced if pyIssue is not blank and is the
group to which the threshold is to be applied. If this is blank, then the threshold
is applied across all groups within the issue.
If not blank, this will supersede any threshold set at the issue level.
|The value which sets a lower limit for the Priority value of an action or treatment as calculated in the Arbitration strategy using the formula P x C x V x L. Only actions and treatments with a Priority greater than this threshold will be considered for arbitration within the next-best-action strategy framework.