How does MoveData Manage Duplicate Records
MoveData uses unique identifiers and Salesforce duplicate rules to detect duplicates. Where a duplicate is detected, new information will be set against that record - if not, a new record will be created.
Object | Mechanism |
|---|---|
Contact | Platform Key and Salesforce Duplicate Rules |
Organisation Account | Platform Key and Salesforce Duplicate Rules |
Campaign | Platform Key |
Recurring Donation | Platform Key |
Opportunity | Platform Key |
The connected platform will typically provide a unique ID for a record in their system. This value is stored against the matching record in Salesforce. This way, when encountered again, MoveData can match against that record. Worked example:
- A fundraiser registers their page
- The page has an ID of
123 123is stored against the record in Salesforce- When
123is encountered again, MoveData will match against that record
The field used to store this value is called Platform Key. In practive, since you can connect different platforms using MoveData, and those different platforms can issue the same ID (particularly if their IDs are sequential in nature), the value is prefixed with an additional identifier like
raisely:123.Object | Field | Comment |
|---|---|---|
Contact | md_npsp_pack__Platform_Key__c.md_npsp_pack__Platform_Key__c | Contacts can exist on multiple platforms and thus carry multiple IDs. The Platform Key object contains a value for the ID md_npsp_pack__Platform_Key__c and a lookup to the contact md_npsp_pack__Contact__c |
Organisation Account | md_npsp_pack__Platform_Key__c.md_npsp_pack__Platform_Key__c | Organisation Accounts can exist on multiple platforms and thus carry multiple IDs. The Platform Key object contains a value for the ID md_npsp_pack__Platform_Key__c and a lookup to the organisation account md_npsp_pack__Account__c |
Campaign | Campaign.md_npsp_pack__Platform_Key__c | |
Recurring Donation | npe03__Recurring_Donation__c.md_npsp_pack__Platform_Key__c | |
Opportunity | Opportunity.md_npsp_pack__Platform_Key__c | |
If a match on platform key is not determined MoveData will run your Salesforce duplicate rules. For most organisations, and especially for those just staring out, we recommend using:
- Contacts: Fuzzy match on First Name, Exact match on Last Name, Exact match on Email or Personal Email
- Accounts: Exact match on Name (this is deliberately basic - because ordinarily, you are only capturing company name on the donation form, and not any additional information about that company to match on)
Importantly, operations on create and edit must be set to
Report and not Alert. If you need to implement new duplicate rules to achieve this, we recommend using Conditions to exclude the user who authorised MoveData from other rules, and include against the new rule (typically: Current User: Alias equals / not equal to User.Alias).Last modified 2mo ago