Registering and signing in to LeanData's Help Center allows you to both Submit tickets and Track your tickets in one convenient place.
Please Sign In to Contact Support.

Menu

Articles in this section

See more

Routing - Duplicate Match Node Guide Follow

Avatar
Customer Education
  • Updated

Contents:

 

Overview

The Duplicate (DupL) Match Node is used to identify Leads in your Salesforce instance that are duplicates of the routed Lead. Before merging duplicate Leads in your router graph you must make a match using the Duplicate Match Node in your graph. Once the duplicate Lead has been identified you can merge the 2 Lead records together using the Merge Dupe Lead Action Node. The Duplicate Match Node also includes filters and Tiebreakers to help you identify the best duplicate Lead record if there are multiple potential duplicate Leads.

 

Example: Tim is the LeanData admin for Lighthouse Development. In his Router flow, he needs to match the routed Leads to any open duplicate Leads that might exist. He configures the Dupe Node, with Filters and Tiebreakers to match to duplicate Leads. Using the Filters, he ensures that no closed Leads are identified as duplicate Leads. 

Each Match node includes Tiebreakers to enable making a match to the best record if there is more than 1 possible match. Tiebreaker rules are included in the node configuration to pick the best match when LeanData finds multiple duplicate Leads. These Tiebreakers function just like the Tiebreakers in Tagging. The Tiebreakers on the node are local only to the node. Any changes made to the node’s Tiebreakers do not affect the Tagging Tiebreakers or even the Tiebreakers on other match nodes.

 

Customization

You have a number of options to configure the node.

  • Node Name
  • Description
  • Filter Duplicate Leads
  • Prioritize Duplicate Leads
  • Set Variable to Duplicate Lead
  • Advanced Settings

 

Node Name

By default, the Node Name is set to Match Node. You can change this label to anything you need. We strongly recommend giving this node a meaningful name such as the goal of the Match Node or simply Match Dupe Leads. This will help others understand the purpose of the node. 

Description
This field is not required but we recommend adding a description to document any customizations made to the node. If someone else needs to take over the management of the flow, the description will help them to understand the goal of the customizations.

 

Filter Duplicate Leads

Use the Filters to include or exclude matches based on the conditions you set on the node. You can use Filters to include or exclude duplicate Leads from matching to the routed Lead record. In our example, we are excluding Leads that are closed (Status = Closed - Converted,Closed Not Converted). This ensures that we will not match the routed Lead record to a Closed Lead. 

 

Value/Field

The Value/Field selector lets you choose between filtering for a value in a field on the matched duplicate Lead record and comparing a field on the matched duplicate Lead record with a field on the routed Lead record.

 

When using Value, you are looking for a specific value in a field on the matched Lead record. For example, if you wanted to filter out Closed Leads, you could select the Status Field, set the Operator to Equals, and select the Closed Statuses from the Value pull-down menu.

When using Field, you are comparing the value of a field on the matched Lead record with a field on the routed Lead record. For example, if your goal is to compare the industry field on the matched Lead record to the Industry field on the routed Lead record, you could select Industry from both the Matched Lead Field and the Lead field. Setting the Operator to Equals ensures that the Logic rule will look for the same industry on the duplicate and Lead records. The label above the Value field will change to Lead Field. In the screenshot above, we are filtering out any lead that does not match the routed Lead’s industry so we use the operator Not Equal To. 

For each condition you add, you will see:

  • Field: The Field selector will give you a list of all the fields on the matched duplicate Lead record that you are filtering.
  • Operator: The Operator gives you a condition to apply to the field for the decision. (Example: Contains, does not contain, starts with, is null, etc). The values in the Operator selection change depending on the field selected.
  • Value/Field: The Value is the value you are evaluating against in your selected field. This is typically a pull-down menu of possible values. If you select Field for Value/Field, you will see Lead Field as the label and the field will be a pull-down of fields on the routed Lead record.

You can add as many conditions as needed to create the desired Filters.

 

Working with Multiple Conditions

When you edit or add rules, you can have multiple conditions.  When you have a rule with multiple conditions you are given the option to specify the relationship between the conditions. By default, you will see an AND relationship. You can change this to OR as needed. You can also use parentheses to group conditions together. Example: ((1 AND 2) OR 3).

 

In the example above we use an OR  relationship because we are looking to filter out Lead records because they are Closed OR their industry does not match the routed Lead’s industry.

 

Exclude Matched Leads with Inactive Owners

This option, when checked, will prevent Leads with inactive owners from being matched to the routed Lead.

 

Prioritize Duplicate Leads

In the Prioritize Duplicate Leads section you will see a list of rules called Tiebreakers. These rules are applied after filters if there are multiple duplicate Leads that can match to the routed Lead record. Tiebreaker rules are processed from the top down and are used to narrow the pool of possible duplicate Lead matches down to the best match. The node will check each rule, one at a time, from top to bottom, until only one remaining potential duplicate Lead remains. This duplicate Lead will be matched to the routed Lead. The Dupe node includes a set of default Tiebreaker rules. You have the following options to modify the Tiebreakers:

  • Edit the existing rules
  • Add/remove rules
  • Change the order of the rules

 

Editing a Rule

To edit a rule, simply click in the rule to open it for editing. You will see the same options as in the Filters.

 

Adding a Rule

If you choose to add a custom Tie-Breaker Prioritization Rule, click New Rule. There are three rule types; LOGIC, SOQL, MIN MAX.

  • LOGIC - When configuring a new logic rule, you can use a Field or Field Value from the duplicate level. This works the same as adding Filters
  • SOQL - You can use a SOQL (Salesforce Object Query Language) string here. More Info
  • MIN MAX - The field you are choosing is the duplicate level field. Set the Operator to either Min or Max. Min meaning the lowest possible value and max being the highest. For Date and Time fields, Min equals the oldest date and Max equals the newest date. When applied to time MIN is the oldest time and MAX is the most recent or further into the future.

For example, Mel the LeanData Admin wants to build a tiebreaker rule that will look for the duplicate with the Min (oldest) created Date. She sets the Created Date to MIN to ensure the tiebreaker looks for the oldest duplicate that matches.

 

Set Variable to Duplicate Lead

LeanData Routing allows you to store values in a container called a Variable, which can then be referenced later in your routing graph for use in routing decisions and actions. This will allow you to assign recurring values, such as lists of User Ids, email domains, state names or zip codes to a Variable, which can then be used multiple times throughout your routing graph.

By default, LeanData will save the output of the Match Node to a variable for you to retrieve later. You can rename the Variable container as needed.

 

Advanced Settings

Node Edges

There are 3 exit edges from a Match Node. Under the Advanced settings you can select a target node for each of the edges for what you would like LeanData to do in each of these scenarios.

 

  • Match: LeanData has identified a best match based on the algorithm, after applying your Tiebreakers and Filters.
  • No Match: LeanData has not identified a match, after considering your Filters.
  • Multiple Matches Identified: If LeanData has more than one match remaining after your Filters, and you would like to take a different action than identify one best match, you can direct this edge to your desired action. This option is disabled by default. Upon enabling, you will also have to remove any Min/Max tiebreakers.

 

Working with Edges

You can Connect nodes in one of several ways:

  1. Open a node and select the Target through the dropdown next to the condition or outcome you wish to assign. Use the search functionality to narrow the scope of the results. If you want Lead processing to stop at your selected node, simply select End of Flow. 

 

Alternatively you can click the Stop Sign icon to set a particular edge to End of Flow, or click the crosshairs icon to assign that edge visually on the main flowchart graph view by clicking the node to which you would like that edge to proceed.

 

 

  1. If you are already in the main flowchart graph view, you can click on the yellow triangle and drag the edge you wish to direct to the next node to which you would like that edge to proceed.

 

Summary

The Duplicate (DupL) Match Node is used to match a routed Lead record with the best duplicate Lead record in your Salesforce instance. The Dupe node uses filters and Tiebreakers to identify the best duplicate Lead record to match to the routed Lead. This node is typically combined with the Merge Duplicate Node to merge the routed Lead with the matched duplicate Lead.

 

For more information on working with router graphs please see our Lead Routing Guide.




For questions or additional assistance please contact LeanData Support.

 

 

 

Related articles

Powered by Zendesk