Our organization is shifting data structures to utilize Contact Points. Does anyone have advice on how we can continue to effectively use DemandTools dedup to identify new Person Accounts with matching Contact Point records (whether that be emails/address)?
We currently use the following scenarios with our current data structure:
Pass 1: FN LN Email fields
Pass 2: FN LN Address fields
Pass 3: FN LN (created last week)
Pass 4: Email fields (created last week)
Any ideas on how to replicate this with Contact Points enabled?
Hey @gursin - As discussed, our reccomendation would be to run multiple Dedupe passes on the Contact Points, utilizing the fields your referenced for testing and look up fields to the corresponding Account to ultimately export the reports of found matches. Once we have our match files, we'll use Import to update the corresponding Accounts from our match files with the Dedupe Key field to ultimately process the Account merges first utilizing the Dedupe Key field matching method and ultimately, then deduplicate Contact Points on the newly merged Accounts. Please reach out to DemandToolsCOE@validity.com if we can assist further in any way!
