Skip to main content


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

Configuring match conditions

Updated on May 10, 2021

As an administrator or a sales operations user, define the conditions that a lead must meet for the system to identify it as a potential duplicate. Defining the match conditions accurately prevents redundant leads, minimizes false positives, saves time, and aids in better forecasting.

All Pega Sales Automation users can review duplicates and merge leads where appropriate. For more information, see Viewing and resolving duplicate leads.

Pega Sales Automation Implementation Guide

You assign weights to specific properties of the Lead case type that you want to use to compare a lead with other leads in the system, and specify the total weight (sum of weighted conditions) that the system requires to flag a lead as a potential duplicate. You can optionally specify the case properties that must match for a lead to qualify as a potential duplicate.

Note: The total weight that you specify at the case level overrides the application-level weightage thresholds that you define when you enable the lead de-duplication feature. For more information, see Enabling the lead de-duplication feature.
  1. In Dev Studio, click RecordsDecisionCase Match.
  2. Depending on the lead type for which you want to configure match conditions, open the appropriate case match rule:
    • To configure match conditions for individual leads, open the FindDuplicatesForIndividualLead rule.
    • To configure match conditions for business leads, open the FindDuplicatesForBusinessLead rule.
  3. On the Case Matching Type page, define the case properties that you want to use to determine potential duplicates in a comparison against the existing leads:
    ChoicesActions
    Define must match conditionsDefine the conditions that must match between the current case and an existing case and for the system to consider the current case a duplicate:
    1. In the Must match conditions section, click Add must match condition.
    2. In the Label field, enter a unique name for the condition.
    3. In the Potential duplicates field, select a case property that you want to use to compare the cases.
    4. In the Relationship field, select the operator that you want to use to compare the cases.
    5. If the Current case field is enabled, define the current case property that corresponds to the property that you selected in substep c above.
    6. Optional: To add additional must match conditions, repeat substeps a through e above.
    Define weighted conditionsAssign weights to case properties and define the total weight that is required for the system to consider a case a duplicate:
    1. In the Weighted match conditions section, in the Find potential duplicate cases where the sum of weighted conditions is at least field, enter a sum of weights that represents a threshold when the lead is a potential duplicate.
    2. Click Add weighted condition.
    3. In the Weight field, enter the weight that you want to assign to a case property to compare the cases.
    4. In the Condition field, select the case property.
    5. Select the operator that you want to use to compare the cases.
    6. Define the current case property that corresponds to the property that you selected in substep d above.
    7. Optional: To add additional weighted match conditions, repeat substeps b through f above.
  4. Check in your changes.
For example: You can configure the settings as follows:
  • Add a must match condition that specifies that the .LeadEmailis equal to .LeadEmail. Here, the first .LeadEmail property relates to existing leads and the second .LeadEmail property relates to the current lead.
  • Add the following weighted match conditions:
    • Weight: 20, Condition: .FirstName = Primary.FirstName
    • Weight: 10, Condition: .LastName = Primary.LastName
    • Weight: 20, Condition: .Company = .Company
    • Weight: 20, Condition: .LeadMobile = .LeadMobile
    • Find potential duplicate cases where the sum of weighted conditions is at least: 50
In this case, if the email address and any three of the weighted properties in the current lead match an existing lead, the system identifies the lead as a duplicate.

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