Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Customer 360 for Salesforce
  3. Configuring the Data Cleansing Settings
  4. Managing Batch Jobs
  5. Verifying Addresses, Email Addresses, and Phone Numbers
  6. Synchronizing Salesforce Records with Customer 360 for Salesforce
  7. Managing Duplicate Records
  8. Consolidating Records
  9. Converting External Records to Salesforce Records
  10. Managing Hierarchies
  11. Integrating Customer 360 for Salesforce with Multidomain MDM
  12. Managing Multi-Org
  13. Troubleshooting
  14. Appendix A: Custom Settings
  15. Appendix B: Glossary

Matching Settings

Matching Settings

The matching settings define weighting for each field that the matching and duplicate check processes use.
If you do not change the matching settings,
Customer 360 for Salesforce
uses the default settings. If you want to update the matching settings, you can define matching settings for each object class or record type.
Customer 360 for Salesforce
returns null scores when one record has a null value for a field.
You can configure the following matching settings:
Name
Name of the object class or the record type for which you want to define matching settings.
You can use one of the following name formats to define matching settings:
  • For an object class,
    <Object Class Name>
    For example, Account.
  • For one or more record types,
    <Object Class Name>:<Record Type Name1>,<Record Type Name2>,...<Record Type NameN>
    For example, Case:High Severity,Medium Severity indicates that the matching settings are applicable to the High Severity and Medium Severity record types.
  • If you want to include the records of an object class that do not belong to any record type,
    <Object Class>:,<Record Type Name1>,<Record Type Name2>,...<Record Type NameN>
    The comma (,) after colon (:) in the name format represents the records of the object class that do not belong to any record type. For example, Account:,R1 indicates that the matching settings are applicable to the R1 record type and the account records that do not belong to any record type.
Duplicate Threshold
Threshold for being detected as a duplicate record. When the duplicate check batch job and duplicate contact check batch job run, records must have a match score that meets or exceeds the duplicate threshold. If the total match score achieves the duplicate threshold, CC360 considers the records as duplicates. Default is 90.
Duplicate Review Threshold
Threshold score below which you do not want to consider the records as duplicates. Records with scores greater than the duplicate review threshold score and less than or equal to the duplicate threshold score are queued for manual review before merge. Set the duplicate review threshold score lesser than the duplicate threshold score. If the records have scores less than the duplicate review threshold,
Customer 360 for Salesforce
does not consider the records as duplicates and enables the duplicate checked flag for the records. If you do not want to manually review the records before merge, you can leave this field empty.
High Matching Threshold
The highest threshold for matching records. When the matching batch job runs, the external data record and the master bean record must have a match score that meets or exceeds the high matching threshold. If the total match score achieves the high matching threshold,
Customer 360 for Salesforce
considers the external data record and the master bean record a match. Default is 90.
Keep Duplicates when Re-Processing
Retains associated duplicate records even when the duplicate checked flag is reset. Default is disabled.
Low Matching Threshold
Not used.
Maximum Score
The maximum possible score. Do not populate this field. Default is no value.
Null Score Billing City
Null score for the Billing City field. Default is 100.
Null Score Billing Country
Null score for the Billing Country field. Default is 100.
Null Score Billing Postal Code
Null score for the Billing Postal Code field. Default is 100.
Null Score Billing State
Null score for the Billing State field. Default is 100.
Null Score Billing Street
Null score for the Billing Street field. Default is 100.
Null Score Birthdate
Null score for the Birthdate field. Default is 0.
Null Score Country ISO Code
Null score for the Country ISO Code field. Default is 100.
Null Score Custom Fields 1 through 6
Null score for custom fields 1 through 6.
Null Score Domain
Null score for the Domain field. Default is 0.
Null Score Email
Null score for the Email field. Default is 0.
Null Score First Name
Null score for the First Name field. Default is 100.
Null Score Last Name
Null score for the Last Name field. Default is 100.
Null Score Legal Form
Null score for the Legal Form field. Default is 100.
Null Score Mobile Phone
Null score for the Mobile Phone field. Default is 0.
Null Score Company Norm
Null score for the Company Norm field. Default is 100.
Null Score Phone
Null score for the Phone field. Default is 0.
Weighting Billing City
Weighting for the Billing City field. Default is 10.
Weighting Billing Country
Weighting for the Billing Country field. Default is 0.
Weighting Billing Postal Code
Weighting for the Billing Postal Code field. Default is 5.
Weighting Billing State
Weighting for the Billing State field. Default is 5.
Weighting Billing Street
Weighting for the Billing Street field. Default is 5.
Weighting Birthdate
Weighting for the Birthdate field. Default is 0.
Weighting Country ISO Code
Weighting of the Country ISO Code field. Weighting should be set to 200 to ensure that only accounts with the same country ISO code are detected as duplicates. Default is 200.
Weighting Custom Fields 1 through 6
Weighting for custom fields 1 through 6. The custom fields have the following behavior:
  • If custom fields 1 and 2 have numeric values,
    Customer 360 for Salesforce
    performs an exact match.
  • If custom fields1 and 2 have alphanumeric values,
    Customer 360 for Salesforce
    performs a fuzzy match.
  • Customer 360 for Salesforce
    performs a fuzzy match for custom fields 3 and 4 if the weight is <=100. If the weight is >100,
    Customer 360 for Salesforce
    performs an exact match.
  • Customer 360 for Salesforce
    performs an exact match for custom fields 5 and 6.
Weighting Domain
Weighting for the Domain field. Default is 10.
Weighting Email
Weighting for the Email field. Default is 0.
Weighting First Name
Weighting for the First Name field. Default is 0.
Weighting Last Name
Weighting for the Last Name field. Default is 0.
Weighting Legal Form
Weighting for the Legal Form field. Default is 0.
Weighting Mobile Phone
Weighting for the Mobile Phone field. Default is 0.
Weighting Company Norm
Weighting for the Company Norm field. Default is 75.
Weighting Phone
Weighting for the Phone field. Default is 10.
Enable Native Salesforce Matching
Enables
Customer 360 for Salesforce
to use the Salesforce Levenshtein matching algorithm.
Native Salesforce Match Threshold Level
Threshold for detecting a matching record when
Customer 360 for Salesforce
uses the Saleforce matching algorithm. The Saleforce algorithm might result in slightly different match scores than the
Customer 360 for Salesforce
matching algorithm.

0 COMMENTS

We’d like to hear from you!