Skip to main content


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

Configuring ethical bias checks

Updated on September 15, 2022

You can test your strategies for unwanted bias by creating an ethical bias policy. For example, you can test whether your strategies generate biased results by sending more actions to male rather than female customers, as well as check how big the bias is. Perform the following procedure to configure the fields that you want to use to measure bias and to define the thresholds for detecting bias.

Pega Customer Decision Hub
Before you begin: Assign the pzBiasPolicyConfiguration privilege to your access group. For more information, see Optional: Granting permission to configure ethical bias policies.
  1. In the Pega Customer Decision Hub portal, click ConfigurationEthical Bias Policy
  2. On the Bias fields tab, click Add bias field.
    Tip: Any properties that are related to your main customer class, such as gender, age, and ethnicity-related properties, are good candidates for bias testing, even if your strategies or AI models do not directly reference these properties. This is because indirect bias can still occur.
  3. If the property that you select has a number value, in the Add bias field window, specify whether you want Pega Platform to interpret the value as a category (for example, gender or ethnicity), or as an ordinal number (for example, for age).
    Note: If there are many categorical values, the system only checks the 20 most frequent values for bias. In most cases, numerical values should not be classified as a category. However, if the property is not truly an ordinal number, you may want to treat it as a category, for example, you can use a postal code to test for location-related bias.
  4. On the Bias fields tab, review and configure the bias threshold settings for each issue in your business structure.
    The bias threshold measurement depends on the type of field that you select:
    • Rate ratio - Rate ratio is used to calculate bias for categorical fields by comparing the number of customers who were selected for an action to those not selected for an action, and then correlating the result to the selected bias field. For example, the rate ratio represented in the following table indicates that actions are sent more often to male rather than female customers:
      Female customersMale customers
      selected for the action5001000
      not selected for the action2000018000
      rate ratio0.462.16
      A rate ratio of 1 represents no shifts in the distribution. You can select a warning range with a threshold between 0 (send a warning if any bias is detected), and 0.7 (send a warning only if very high bias is detected). You can also choose to ignore this bias field for a particular issue in your business structure.
    • Gini coefficient - The Gini inequality coefficient is used to calculate bias for numerical fields. For example, it detects whether the distribution of age is different for customers who receive an action. A Gini coefficient of 0 represents no shifts in the distribution. You can select a warning threshold between 0 (send a warning if any bias is detected) and 0.50 - 2.00 (send a warning only if very high bias is detected). You can also choose to ignore this bias field for a particular issue in your business structure.
      Tip: For issues such as credit risk, set the value of the threshold lower than for marketing issues such as upsell, to better detect the variations.
  5. Click Save.
  6. To use the bias policy to test the behavior of your strategies:
    1. In the Pega Customer Decision Hub portal, click Simulation Testing.
    2. Create a new simulation test with the purpose Ethical bias.
  • Previous topic Using Geofences in strategies
  • Next topic Supplementing next-best-action with traditional outbound campaigns

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us