Best Practices for Mapping Matching Attributes
Match attributes, such as name, country, and postal code are used for real-time and batch matching of the account and contact records. You map the attributes in Customer Data Management application with the corresponding Enterprise Data Quality (EDQ) attributes to create an attribute mapping.
For example, for account matching, map the EDQ Attribute, name, to the Account Attribute, OrganizationName. When you map the attributes in the CDM application with the corresponding EDQ attributes, you create a matching configuration setting for identifying duplicate entries. These settings are stored as matching keys in CDM.
You can use two types of EDQ Match Identifiers to include or exclude records from matching.
-
Unique Identifier: Records that have the same Unique Identifiers always match, regardless of all other data.
-
Elimination Identifier: Records that have different Elimination Identifiers never match.
Examples of attributes that could be used for Unique Identifier or Elimination Identifier are Social Security Number for contact or D-U-N-S number for account. You can use up to 3 Unique Identifier and 3 Elimination Identifier attributes in your matching configuration.
Key considerations for managing key generations:
-
When you change the attribute mappings you must regenerate matching key values for the new or updated accounts and contacts.
-
A key generation failure is logged for records having a null or empty string value for a mapped attribute.
-
Consider using a Unique Identifier for cases where an exact match on a single attribute value will always signify duplication. In other words, a single-value exact match rule would be configured with a match score of 100.
Matching configuration parameters are system-level parameters that control aspects of the data quality matching services. An Enterprise Data Quality (EDQ) matching configuration includes both real-time and batch matching configuration parameters.
The following table describes the real-time and batch configuration parameters and provides the supported parameter values where applicable.
|
Parameter |
Description |
Parameter Value |
|---|---|---|
|
Cluster Key Level |
Returns records based on the cluster key level. |
|
|
Score Threshold |
Specifies the score above which the matched records are returned by the matching service. Records equal to or greater than the score are considered as matches and the records with scores less than the threshold are rejected. |
|
|
Match Results Display Threshold |
Controls the number of matched records that are returned by the real-time matching. Note: This match configuration parameter is enabled only for real-time matching. |
|