Deduplication is one of the most important processes that Bedrock performs on behalf of our customer's data. Each object type has a different set of unique fields that are used to determine what records are matched up in our database to ensure that updates to mapped fields take place where expected.
Below is a table with an overview of the default dedupe keys for each object. Note that the Object names are standardized naming conventions and that many systems will have their own unique names for the object (i.e. Contacts could be called Leads, Persons, etc. and Companies could be called Accounts or Organizations. Doesn't matter what these systems call them, in Bedrock they go by the standardized names below).
|Object||Identifying Fields||Identifying Relationships||Matching Logic|
|Contact||N/A||Direct match on lowercased email address|
|Company||Company_Name||N/A||Fuzzy match on company name; Long term this will be come a more complex soft match|
|Opportunity||Name, Close_Date||Contact and/or Company||Fuzzy match on name, direct match on expected close date, and graph match on related contact/company|
|Owner||N/A||Direct match on lowercased email address.|
|Activity||Title, Occured_At||Contact and/or Company||Direct match on title and "occured at", and graph match on related contact/company|
If any of your systems happen to have multiple records with the same exact value for the above keys, they will be flagged as DUPE RECORDS and will be ineligible to sync until they resolved so that only one record remains. Learn more about DUPE RECORD conflicts here.