Options > Constituent Matching

Tried or trying many many fields, to reduce the no. new records being created, but so fare, matched records are less than 10%. We tried,

1) First Name, Last name and email - around 5-6%

2) First name, Last name, Address, City, Province & Postal code, around 5-6%


It is frustrating to see so many duplicates are been created but don't know how to stop. Every two years, we run the merge tool & reindex or reorder the database as an alternative.

Hi Marie Harris‍ - As others have mentioned previously, it is likely that no matter the default fields you select for Constituent Match, you will have to search for constituents yourself and manually change information to match your database standards (i.e. Addresses).


We have a number of fields selected for default Constituent Matching (which may or may not be a good thing), 'Exact Match' is not selected:

• First Name / Last Name
• Birth date
• Address / State / ZIP
• Any Phone or Email

We review every constituent that comes through the RE/LO portal, and do not allow RE/LO to process any new records or linked records automatically. We have found that some of records RELO shows as 'matched' to a record in our system are not correct. While this review does take a fair amount of time, I would rather spend the time upfront ensuring records are matched/linked correctly than deal with duplicate records later.

We have tried to match with First name, Last Name and email (WO exact) also First Name, Last Name and postal code. I believe Marie is correct in saying to check each record which comes thru, but our daily Volume is average is around 50, that means every morning i have to spend more than an hour that is impossible for a 1 man team !


I would like to understand the logic behind the matching program to better implement a process.