Home > DupeBlocker Step by Step Instructions > Scenarios > Creating/Editing Scenarios > Scenario Rules
Scenario Rules Overview
Scenario rules determine what fields will be used to identify matches, and how the fields will be matched.
All fields that are included in the scenario rules must be populated and must match (based on the mapping type used) for a record to be identified as a duplicate by that scenario.
DupeBlocker limits the total number of scenario rules across all scenarios that apply to a specific object type to a total of 40.
- Account scenario rule count is the total number of rules for all deployed Account and Lead to Account scenarios.
- Contact scenario rule count is the total number of rules for all deployed Contact and Lead to Contact scenarios.
- Lead scenario rule count is the total number of rules for all deployed Lead, Lead to Contact and Lead to Account scenarios.
For example counts would be calculated as follow if all the default scenarios were deployed:
Account scenario rule count = 19
Contact scenario rule count = 20
Lead scenario rule count = 29
Adding a New Rule
To add a new rule click "New".
Contact, Account or Lead Scenario Rules 
Step 1: Scenario Type - Will be auto-populated with the Scenario Type as selected on Scenario Details and cannot be updated.
Step 2: "Contact/Account/Lead" Match Field - Select from the list of fields in the object available for matching.
Beginning with DupeBlocker 2 ALL fields are available for matching, including custom fields!
Step 3: Mapping Type - Select the mapping type you wish to apply to this field.
- Mapping types will determine how a field is evaluated as a match.
- Various options are available for matching similar field values (i.e. similar Account/Company names, street addresses, phone numbers, first names etc.).
- The mapping types available for selection will vary based on the type of field being matched.
- A complete list of available mapping types and detailed description can be found in DupeBlocker Step by Step Instructions -> Scenarios -> Mapping Types Described in Detail.
Step 4: First XX Letters - If the mapping type is set to "First XX Letters" this field is required to specify how many letters to match on. For all other mapping types leave blank.
Step 5: Scenario - Will be auto-populated with the Scenario Name and cannot be changed.
Step 6: Additional Mapping Options - Checking one or more of these options will further loosen the match criteria:
- English Fuzzy: Phonetics engine capable of analyzing words for how they sound when pronounced. Through a technique of removing vowels and analyzing the remaining consonants the fuzzy engine works well for matching fields with spelling mistakes. Numeric characters are ignored with this option. DO NOT USE for matching phone numbers or other fields that contain numeric characters that you do not wish to ignore (i.e. street addresses).
- Transpose: Matches all words in a field regardless of their order. For example, "Smith and Jones" will match to "Jones and Smith".
- AlphaClean: Strips out non-alphanumeric characters. Just look at A-Z and 0-9, ignore everything else. Commonly used to ignore punctuation in a field.
Step 7: Match Blank - By default, blank fields are not matched against each other. If this option is checked then two blanks fields will be matched.
Repeat Steps 1-7 for all fields you wish to match on.
Lead to Contact and Lead to Account Rules
With Lead to Contact or Lead to Account Scenarios, a Lead Match Field and either a Contact or Account Match Field will need to be specified. The Contact or Account Match Field will be displayed as a "Related Field" in the Scenario Rule.
See also
| 
Print