Contents:

• Overview
• Finding the Match Settings Page
• Domain Only Matching Setup
• Best Practices
• Routing Match Limits
• Matching Fields
• Custom and Default Matching Fields
• Special Fields in Lead-to-Account Matching
• Preserving Manual Updates

 

Overview

The LeanData Match Settings tab within the Matching section of the LeanData App allows you to customize how matched objects are selected, prioritized, or updated with three sections: Domain Matching, Preserve Manual Updates, and Routing Match Limits.

 

Finding the Match Settings Page

To locate the Match Settings page, go to the Matching tab on the left sidebar in the LeanData Dashboard and select Match Settings from the dropdown menu.  

 

Domain Only Matching Setup

The first section on the Match Settings page is Domain Only Matching for Tagging and Routing.

To clarify, even with this setting disabled, domain is always considered as one of the multiple matching criteria in the LeanData Matching Algorithm. But typically, if domain is the only matching criteria between lead and account, it is insufficient to form a match. Enabling this setting will allow Lead-Account matches where domain is the only matching criteria. 

When toggled ON you have the option to select Use as a Fallback (Include ONLY IF no other matches are found).  If you decide to include domain-only matches, this is our recommended setting because it considers other higher quality matches first while using domain-only matching as a fallback, if no higher quality matches are otherwise found. 

Always Include will always pull in domain-only matches as potential matches and subject these to tiebreakers alongside other higher quality matches. There is a greater likelihood of selecting low quality matches with this setting.

 

Best Practices

When considering your options for domain-only matches, keep in mind that the fuzzy matching algorithm evaluates company name, email domain, website domain, phone number and address.

Enabling this domain-only match setting will allow a Lead to match to an Account if they have the same domain associated with them, even if the company names are completely unrelated.

This is why it is recommended that you either select the Use as a Fallback option or keep domain only matching disabled, so that your match settings aren’t overly dependent on domains.

 

Routing Match Limits

The next section of match settings, Routing Match Limits, is used for controlling the maximum amount of potential matched records that can be returned for a particular object that you’re matching against, which affects system performance.  You may have a lot of potential matched records in your system that you want to evaluate for your matches and expand that number to more than 1,000.

 

If the number of potential matched records LeanData identifies exceeds the amount in the settings (in the above case, 1,000), the default setup will only consider the 1,000 matched records that have been most recently modified.  

The criteria for which records will be considered can be customized in the right hand side dropdown menus.  You can choose between ‘created date’, ‘last modified date’, or ‘last activity’.  From there you can also select between the ‘most recent’ or ‘oldest’ records.

Note: this setting is rarely modified, and should only be used if you have many records with over 1,000 potential matches, and LeanData is missing the correct match because it hasn’t been recently modified.

 

Matching Fields

LeanData will typically look at Company Name, Email, Website, Phone, and Address field when matching records. In the rare case that your organization does not utilize these standard fields on your Leads, Contacts and Accounts, you can specify custom fields you would like to utilize in addition to these.

To do so, navigate to LeanData > Matching > Matching Settings > Matching Fields Tab. 

 

Custom and Default Matching Fields

You will be able to customize the matching fields that LeanData will use for Leads, Contacts, and Accounts. Navigate to the object for which you wish to customize your matching fields. Then use the dropdown to select the custom field you would like to use alongside LeanData's defaults. 

 

Special Fields in Lead-to-Account Matching

In addition to the matching fields configured above, you also have the option to add one additional field to consider when matching Leads and Accounts. LeanData will look for an exact match on the values between these special fields and will consider any Leads and Accounts that have matching value to be a potential match, regardless of any other criteria. Typically, this is used to incorporate a Unique Identifier or external ID field into LeanData matching.

To configure this, enable the Special Fields in Lead-to-Account Matching setting on the Leads tab. Then select the field you wish to use as an additional matching criteria.

 

Once you have selected your Lead field, navigate to the Account tab and find the same Special Fields in Lead-to-Account Matching section, enable the setting and select the Account field you wish to compare with the Lead field you selected above.

After saving this setting, ​​LeanData will always consider Leads and Accounts that have the same value in these fields to be a potential match. Matches made using this field are still subject to your filters and tiebreakers.

 

Preserving Manual Updates

Within the Tagging functionality, LeanData provides the option to preserve any manual updates to the Reporting Matched Account field. You can find this under Matching > Tagging Settings > General Tab > Preserve Manual Updates.

You will find two settings under the Preserve Manual Updates section. Continuous Tagging and One-Time Tagging. Continuous Tagging is running in sync with LeanData’s batch processing time while One-Time Matching is only utilized when you initiate a One-Time Tagging job.

Preserving Manual Updates for Continuous Tagging will preserve any values that are manually updated in your Reporting Matched Account and Mapped Account Fields. This can be useful if people are inputting manual values for these fields and wish to prevent LeanData from overwriting these values as we continuously update the matches.

One-Time Matching is utilized when you run a One-Time Tagging job under the Advanced Settings. Preserving manual updates for One-Time Matching will preserve any values that are manually updated in your Mapped Account Fields if you ever run a One-Time Tagging job. This can be useful if people are inputting manual values for these fields and wish to prevent LeanData from overwriting these values during any One-Time Tagging jobs.