This article explains the different use cases for "Possible Mismatch" and "Possible Duplicate" tags
Background
Checking for duplicates in your Alpine database is crucial for ensuring accurate and reliable Constituent data. Removing duplicates saves time, prevents errors, and allows for effective Constituent engagement.
While Alpine won’t automatically run duplicate checks for you, we recommend running these reports at least once a quarter to help keep your database clean. Here is a quick video on how to first run a duplicate check.
Running a duplicate check in your Alpine database will create two types of Tags under the "[System] Needs Review" Tag Group. They include "Possible Duplicate" Tags and "Possible Mismatch" Tags.
"Possible Duplicate" Tags
"Possible Duplicate" Tags are applied when multiple Constituents share either the same name, email, or validated address.
Example: Possible Duplicate (by Name)
Example: Possible Duplicate (by Email)
Example: Possible Duplicate (by Address)
"Possible Mismatch" Tags
The "Possible Mismatch" Tags apply to individual Constituents that use either a different name or address other than the one on their Constituent profile when making a transaction.
Example: Possible Mismatch: Name
If a Constituent uses a different name than the one you have associated with their email address when making a transaction, Alpine will apply the "Possible Mismatch: Name" tag to their Constituent profile. A transaction can either be a donation, ticket purchase, or membership payment.
Example: Possible Mismatch: Address”
If a Constituent uses a different address than the one you have on file when making a transaction, Alpine will apply the "Possible Mismatch: Address" tag to their Constituent profile. A transaction can either be a donation, ticket purchase, or membership payment.
