Overview
Element451 offers a robust Deduplication module to efficiently manage and merge potential duplicate records. The module can be easily accessed to review and merge duplicates, utilize search and filter options, and handle conflicts with customizable settings. Whether merging from a contact’s profile, using the dedicated module, or performing bulk merges, Element451 provides tools to ensure your data remains clean and accurate.
Accessing the Deduplication Module
Navigate to Contacts > Deduplication.
The Deduplication Module Interface
Once you've accessed the Deduplication module, you'll find yourself in the Merge Duplicate People Records interface. This is where you are presented with a list of potential duplicate records that need to be reviewed.
Searching + Filtering the List
Searching + Filtering the List
Search: Above the list of possible duplicates, a search bar allows you to search for specific contact records.
Filter: To the far right of the search bar, a filter control allows you to filter the list to show only unresolved duplicates, all duplicates, or ignored suggestions. The filter is set to unresolved by default.
List Columns + Action Buttons
List Columns + Action Buttons
You will notice there are two name columns in your list. The left column shows the suggested Master Record, while the right column shows the Possible Duplicate. The Possible Duplicate record shares similar attributes to the Master Record, which triggered E451 to flag it as a candidate for merging.
To the far right of each row on the list, the following is displayed: displays the following:
Match: Percentage of duplicate criteria that were met (confidence score).
Status: Status of the possible duplicate record (unresolved or ignored).
View: View a preview of the possible duplicate record.
Merge: Opens the merge interface, shown later in this article.
Ignore: Ignores the duplicate match and leaves both records unmerged.
How Does Deduplication Work?
Deduplication Logic
Element451 automatically checks for duplicates whenever a record is created or updated, using key identifiers like name, email, and date of birth. For a detailed explanation of how this works, refer to the full article below.
Process of Merging Records
When records are merged, Element451 keeps the Element ID of the master record. Once the merge is complete, the duplicate record will be deleted/overwritten. Below is a description of how fields are prioritized and merged:
Single Value Fields
Single Value Fields
Only one data point can be kept for basic fields such as person data and contact information. If there are conflicting fields, the information in the master record will be selected. If the Master field is empty, then the duplicate data will be selected.
Multi-Value Fields
Multi-Value Fields
Notes, labels, and applications from both student records are merged to the master record by default unless you specify not to merge them.
Similarly, for fields such as evaluations, identities, event registrations, and surveys, the default is to merge into the master record. If there is conflicting data, Element selects the master record's data. You can also specify to ignore or keep one when there is conflicting data.
For fields such as education, addresses, milestones, and sources, they are merged by default unless you specify another action, such as append, ignore, or keep both.
For all other fields, the system merges everything to the master record by default.
Merging Records
Element451 offers flexible tools for managing duplicate records. You can merge duplicates directly from a contact’s profile, use the dedicated Deduplication Module, or perform bulk merges. Customize your approach to ensure clean and accurate data efficiently. For a detailed explanation of how this works, refer to the full article below.
Video Guide