Prospect Duplicate Check Paige Freeman May 06, 2024 13:02 Updated In the Additional Duplicate Check section of the Prospect List Mapping Summary, you can define which fields you want to use when checking for duplicate records. From the Marketing Central page or the left navigation, select Manage Prospect List Mapping. On the Manage Prospect List Mapping page, select the edit pencil or the hyperlinked List Source in the grid to open the Prospect List Mapping Summary. On the Summary tab, select the edit pencil to open the fields for edit. In the Additional Duplicate Check section, perform the following: Select the Prospect Field from the drop-down.This lists all of the fields from the Prospect table for use in additional duplicate checking. For example, if the Social Security Number field is always uploaded into the Prospect Social Security number, then the social security number is compared to the other prospects as part of the duplicate checking process. If customers have the same email, for example, the duplicate record will be deleted. Select the Corresponding Customer Field from the drop-down.When the system performs duplicate checking, this field is compared against the Corresponding Customer field in the Customer table for duplicate checking. If applicable, set the Check Duplicate Addresses toggle to NO.The system must at least perform address duplicate checking. This field is only enabled if the Prospect Field AND Corresponding Customer fields are selected. If set to YES, the process includes checking by address as well. If set to NO, you can use only the two Prospect and Corresponding Customer comparison fields. If both the Prospect and Corresponding Customer fields are null, then the Check Duplicate Addresses toggle is set to YES and disabled. Prospect Duplicate Check Logic From the Prospect List Mapping page discussed above, you can define which fields you want to check for the finding of duplicate record: Prospect Field Corresponding Customer Field Based on the above field value the upload process checks: Is there a record already exists based on the corresponding Prospect Field value in the mkt_prospect table? If yes, then this is a duplicate prospect. Is there a record already exists based on the Corresponding Customer Field value in the customer table? if yes, then this is a duplicate customer. If the record is not a duplicate prospect or customer, then the upload process checks to see if the Check Duplicate Address toggle is set to YES. If the Check Duplicate Address = 'Y' then If mstrListRecordType = "I" (individual) Or mstrListRecordType = "B" (both individual and company), then: To identify the duplicate customer, the system check in the CUS_Address_Alias_vw for the following fields: substring(First_Name,1 ,1) Last_Name Address_1 City State Postal_Code To identify the duplicate prospect, the system check in the MKT_Prospect for the following fields: substring(First_Name,1 ,1) Last_Name Address_1 City State Postal_Code If mstrListRecordType = "C" (company) Or mstrListRecordType = "B" (both individual and company), then: To identify the duplicate customer, the system check in the CUS_Address_Alias_vw for the following fields: Label_Name Address_1 City State Postal_Code To identify the duplicate prospect, the system check in the MKT_Prospect for the following fields: Label_Name Address_1 City State Postal_Code After the above the verification, the system again checks for the following fields in the current list (the uploaded text file) for duplicates: last_name First_Name Address_1 City State postal_code After the above the verification, the system again checks for the following fields for the current list (the uploaded text file) for duplicates: label_name City Address_1 State postal_code