Who can use this feature?
- All roles with access level "high"
- Available on all plans
Duplicate contact records can occur in Catalyst when you supplement Salesforce contacts with contacts from a data warehouse or CSV upload. In the event of a conflict, Catalyst allows you to choose how to process the duplicate records.
De-duplication scenarios
Catalyst allows contact records to be originated from Catalyst or Salesforce:
- Catalyst originated: CSV upload or data warehouse
- Salesforce originated: Has a distinct Salesforce contact record
The following table describes how Catalyst handles each scenario:
| Created first | User action | Created second | Catalyst action |
|---|---|---|---|
| Salesforce record | Edited contact record fields | Catalyst record | Do not create Catalyst contact record |
| Catalyst record | No actions taken | Salesforce record | Merge Catalyst record into Salesforce and keep Salesforce values |
| Catalyst record | Edited contact record fields | Salesforce record | Respect duplication preference in the Salesforce integration |
Set your duplication preference
For the last scenario described above (Catalyst contact record created and edited first), choose how you want Catalyst to process the duplicate.
- Navigate to Settings > Integrations.
- Click on the Salesforce integration.
- At the bottom of the settings, select the duplicate contact record preference that fits your needs.
- Merge records and sync to Salesforce using the Catalyst value
This is the recommended option.
- Merge records and sync to Salesforce keeping the Salesforce value
- Allow duplicates. Create a new Salesforce contact record and keep the contact in Catalyst
- Merge records and sync to Salesforce using the Catalyst value
- Click Save.
When merging, if field A’s value on a record is null and field A’s value on the duplicate record is present, Catalyst keeps the present value. If your Salesforce contact record has fields with validation rules that don’t match the values filled in within Catalyst for that same field, Catalyst respects your Salesforce’s validation rules on the next Salesforce sync.