Skip to main content
All CollectionsUsers and DataUser Management Terms on Almabase Explained
Understanding How Duplicate Profiles are Detected
Understanding How Duplicate Profiles are Detected
Krithipa R avatar
Written by Krithipa R
Updated over a week ago

In this article, let's understand how the system detects two profiles and flags them as duplicates. The system goes through the following steps in the specified sequence and assigns scores. If the score is greater than zero, it marks the two profiles as duplicate:

1. Name Match: It compares the full name, first name, and last name, and if it's ≥ 75% match, it scores it as (+1), and proceeds to check the next criteria.

2. Class Year: If both profiles have the same class year, it scores it as (+1). If both have class years but different values, it proceeds to check the next criteria.

3. Email: If both profiles have an email address and they match, it scores it as (+1). If both have email addresses but different values, it proceeds to check the next criteria.

4. Gender: If both profiles have the same gender, it scores it as (+1). If both have gender but different values, it scores it as (-1) and proceeds to check the next criteria.

5. DOB: If both profiles have the same date of birth, it scores it as (+1). If both have a date of birth but different values, it scores it as (-1) and proceeds to check the next criteria.

6. External Database ID: If both profiles have the same External Database ID, it scores it as (+2). If both have External Database IDs but different values, it scores it as (-2) and ends the process.

Take a look at the entire flow below:

Did this answer your question?