This is an old revision of the document!
The settings applied in this section will allow you to define the ‘Match Groups’. These groups can then be populated with the relevant 'Entity Attributes' which will be used for matching. After clicking on ‘Match Groups’ under ’Settings’, you will be able to navigate to the screen below.
NOTE: It is only possible to use one 'Entity Attribute' at one time.
Entity Type: For this incidence select 'Single Entity' from the drop-down.
Select Entity: Select from the ‘Select Entity’ drop-down to view the respective ‘Entity Attributes’ and ‘Attribute Group Configuration’ settings. You should be able to select from one of the following Entities:
Display Attributes By - For a selected entity, you can toggle the list of attributes by:
Hover over the ‘Account Entity Attributes’ heading and a drop-down will appear. This allows you to sort the attributes in ASC or DESC order. This can also be toggled by clicking on the headings. Hover the mouse over the Attributes Icon and you will be able to view the attribute name type. If the attributes are listed by ‘Display Name’, you can view the ‘Schema Name’ by hovering the mouse over the attribute name and vice-versa.
You can search for a specific attribute by using a Keyword Search feature. Please note - If the attributes are listed by ‘Display Name’, you can only search by the keywords from ‘Display Name’ and not by the keywords for ‘Schema Name’ and vice-versa. You will be able to drag and drop the attributes under any Attribute Group. However, 'Attribute Groups' can only be used once.
It is important to define our match group weighting when selecting our match groups. Select the 'Priority' drop down and select from a range of weighting options.
A weighting a can be applied to individual match groups dependant on the importance of your matching attributes.
On the right hand side of the Match group settings page you will see a toggle for 'Include for Matching'. If this toggle is activated, these attributes will be fed to our match engine. If unselected , these attributes will not be used for matching, but WILL be included for scoring purposes. EG. If email was used for matching but First Name and Last Name were not then you might get a scenario as follows:
Email fields match because they are both “email@example.com”, however because we used First Name and Last Name for scoring, Bob Smith will not match with Jessica Howes. Scoring is therefore an important element when returning legitimate duplicate records.
This functionality allows you to cross compare entities for duplicate records. There are a few small changes to be made in the setup but the fundamental functions are the same as a single entity configuration.
Entity Type: For this incidence select 'Across Entity' from the drop-drop.
Source Entity: Select 'Lead' Entity as this will be the entity from which you will be using to check for duplicates in the target entity.
Target Entity: Select either 'Account' or 'Contact' for the entity which you want to use for checking against your source
Attribute Groups: Displays the list of groups added with their attributes shown below. You can change the order of groups and attributes via a ‘drag and drop’ function. When moving groups, associated attributes will also be moved. The mouse hover tool tip will display the ‘Schema Name’ and vice-versa.
Priority: You can set the ‘Priority’ for each group with a double click on the drop-down selection. The 'Priority' is used to select the weighting for the match group. 'Priority' drop-down has five values:
You can set the ‘Match Key’ for each group with the help of drop-down selection. The 'Match Key' is used to select an algorithm for phonetic match token generation. The 'Match Key' drop-down will have six choices:
Soundex retains the first letter of the input string to formulate its match token. Soundex removes vowels (a, e, i, o, u) and h and w from the input string. The remaining letters are assigned numbers using a lookup table to produce a token of 4 characters.
This means ‘Cathy’ and ‘Kathy’ will not match as their match tokens begin with a ‘C’ from Cathy and a ‘K’ from Kathy. As such, Soundex does not match well where the start of a word sounds the same but is not the same. Also, due to the numeric substitution it is possible to be shown non-matches (false positive) matches.
DQSoundex overloads Soundex with the advanced capabilities of DQFonetix™. This improves the start of word logic and modifies the first letter(s) of an input string. DQSoundex will de-pluralise and pre-process the start of words to manage variances like ‘C’ to ‘K’ as in 'Cathy' and 'Kathy', as well as ‘Ph’ as in Phonetix to ‘F’ in Fonetix.
Metaphone improves the Soundex algorithm by using information about variations and inconsistencies in English spelling and pronunciation, to produce a more accurate encoding.
This allows you to find more precise matches than the simple Soundex algorithm. Metaphone considers a larger set of character transformations than Soundex and therefore analyses a string phonetically with far more accuracy.
DQMetaphone like DQSoundex is an enhanced Metaphone technology with the advanced capabilities of DQFonetix™. This improves the start of word logic and modifies the first letter(s) of an input string. DQSoundex will de-pluralise and pre-process the start of words to manage variances and improve matching.
In the case shown below (Christopher), Metaphone would have generated three of five names matches. However, after running DQ’s advanced algorithms and advanced logic, DQMetaphone allows ‘Kh’ from 'Khristopher' to match with the ‘Ch’ from 'Christopher'. Thus generating the same match key token.
DQFonetix™ contains our advanced phonetic algorithms developed over the last 25 years by DQ Global. The algorithm is property DQ Global and hence we do not share the specification of the process. However, DQPhonetix™ has four key features:
DQPhonetix™ provides your CRM system with the most varied matching window to highlight duplicate matches that may not be picked up – or falsely matches - in Soundex and Metaphone.
Selecting no match key will not generate a phonetic token, hence no match token will be generated. However, this allows you to match identical strings.
Include for Matching: With the help of a checkbox feature, you can configure the ‘Include for Matching’ to select the attributes to be used for matching purposes. By default, the group is included for matching. You do have the option to uncheck the group and mark it as excluded. The groups which are not included for matching are still used for percentage scoring.
These functions will allow you to navigate the DQ for Dynamics application. They are as follows: