Cleanlist’s Merge-Purge Duplicate Identification service uses advanced “fuzzy” name and address matching algorithms to identify duplicates across two or more databases, even when the content, formatting and syntax of the data is different.
Each database can be assigned a priority level to use in determining which record in a duplicate set survives. For example, if a Merge-Purge is performed between a customer and prospect file; typically the customer record survives and the prospect record is flagged for deletion. Priority rules may be as simple or complex as necessary. It’s also possible to consolidate the data from two or more records and create one best-of-all record, although this is not included with Cleanlist’s base Merge-Purge service (contact Cleanlist to discuss your unique requirements).
When performing a Merge-Purge service, Cleanlist first ensures that each source file is duplicate-free by applying its Duplicate Elimination service. (This is also referred to an “intra-file” duplicate elimination vs. the Merge-Purge which is an “inter-file” de-duplication process.)
You choose whether the objective is to identify multiple instances of the same individual (called “Individual Level” match), or different individuals at the same household address (called “Household Level” match).
When you order this service, you receive a consolidated result file containing all records from each source file, in a standardized format and with duplicates flagged for easy identification and/or removal.
An included summary report provides statistical data describing your results.
![]() |
![]() |
![]() |
![]() |
2% - 20% Range.
Field Name | Description | |
---|---|---|
DUPFLAG |
Duplicate Flag:
|
|
DUPID | Duplicate ID: This column contains the duplicate set ID. All records in a duplicate set have the same ID number. |
|