This document describes...
- managing when and how the integration creates new Engage supporters or Salesforce contacts or matches with existing contacts.
- whether to override Duplicate Rules in Salesforce.
- processes for Salesforce admins to manage Salsa Engage New Supporter Queue entries, deletions, and contact merges.
- provides tips on how to locate synchronized records in Engage and Salesforce.
Setting these options to meet your specific business needs is key to keeping your synced data healthy and up-to-date.
How the Integration Handles New Supporters in Engage
Each time the integration syncs, the integration determines whether there are any potentially matching contacts before creating a possible duplicate. New Salsa Engage supporters are sent to Salesforce. However, instead of immediately creating a contact for each new supporter, the integration will first stage the record in a custom object in Salesforce called the Salsa Engage New Supporter Queue. Once there, the integration will use a special rule that’s installed in Salesforce’s built-in Duplicate Matching and Detection tools to compare the staged supporter with your existing contacts. The rule looks for an exact match on Last Name and Email as well as a "fuzzy" match on First Name. Click here to see what we mean by "fuzzy".
In Engage, you can opt for the integration to always create a new Contact or attempt to sync with an existing contact that matches with an existing Salesforce contact automatically, or the integration can always send those new supporters to the Salsa Engage New Supporter Queue to be resolved individually. This option is found under Handling New Supporters section in the Salesforce menu under the Settings tab.
Creating New Contacts Automatically
Click Queue All New Supporters in Salesforce and let me decide to queue all new supporters in the Salsa Engage New Supporter Queue for a Salesforce administrator to resolve. This includes new supporters that had no potential matches. While waiting for manual resolution, no activities, donations, or other records associated with that new supporter will be pushed to Salesforce. This ensures that the connected activity records are added to the correct contact in Salesforce once resolved.
Click Automatically Create a New Contact or Attempt to Sync With Existing Contacts That Match to automatically create new supporters that have no potential matches as new contacts. We provide a few additional options when you select this option that will determine what happens if there are potential matches.
Matching with Existing Contacts Automatically
Set Auto-match new Engage Supporters with existing Salesforce Contacts to No to automatically create a new contact from new supporters without any potential matches. If any potential match is found, it will be queued in the Salsa Engage New Supporter Queue for a Salesforce administrator to resolve.
Set Auto-match new Engage Supporters with existing Salesforce Contacts to Yes to allow the integration to look at the number of potentially matching contacts before deciding whether to auto-match.
- If only one potentially matching contact exists, it will automatically connect to that contact.
- If more than one potential match is found, a further setting decides whether the integration should automatically match with the oldest or the most recently modified contact. Or, you can choose Let me decide to leave it queued in the Salsa Engage New Supporter Queue for a Salesforce administrator to resolve.
NOTE: Whenever auto-matching is enabled and the contact that it should match with has the Do Not Synchronize with Engage contact field checked, the integration will NOT auto-match in that case. Instead, it will remain queued in the Salsa Engage New Supporter Queue for a Salesforce administrator to resolve.
Overriding other Duplicate Rules in Salesforce
Overriding other Duplicate Rules in Salesforce may be necessary to create new contacts through the integration. The integration uses the API to manage the creation of new contacts. If, for example, your Salesforce account has a rule set to alert whenever a new contact matches an existing contact’s Last Name, it may prevent the integration from creating a new contact through the API.
Setting this option to Yes allows the integration to override those rules and create contacts through the API without having to change your existing duplicate rules that alert in Salesforce. This includes overriding the Standard Contact Duplicate Rule, which comes activated by default in Salesforce accounts.
NOTE: Any duplicate rules explicitly set to "Block" the creation of duplicates in Salesforce cannot be overridden through the API and must be set to "Allow".
Resolving Entries in the Salsa Engage New Supporter Queue
Entries made in the Salsa Engage New Supporter Queue that have not been cleared automatically by the integration must be resolved by a Salesforce administrator. You can find the queue in Salesforce under the App Launcher while using the Lightning Interface or as a tab in the Classic Interface. Search for Salsa Engage New Supporter Queue.
If there are any pending entries, they will be listed. You can click into an entry to see any potentially matching contacts. You can decide whether to create a new contact for this record or match with an existing contact by clicking the "link" button.
Once a decision is made, the full supporter data, donations, and other activity records tied to the pending new supporter will be sent to Salesforce and applied on the next sync.
How the Integration Handles New Contacts in Salesforce
Each time the integration syncs, the integration looks for any new contacts that have been created since the last time it ran. For these new contacts, the integration will check to see if any are eligible to sync before creating a matching Supporter in Engage.
A new contact is eligible to sync if the Do Not Synchronize With Engage field is not checked.
Eligible contacts will then be compared with the existing Supporters in Engage to check for duplicates on email address.
- If the new contact’s primary email address is already in use in Engage and that Engage record is synced to a contact record, it does not create a duplicate Engage supporter. Only one record can exist in Salsa Engage with the same email address at a time. An error entry will be made in the Errors tab indicating which record was a duplicate.
- If the new contact’s primary email address does exist in Engage but the Engage supporter has NOT synced with any record in Salesforce, the integration will place a new entry in the Salsa Engage New Supporter Queue in Salesforce. If a pending queue entry already exists, then the new contact will be added to the list of potential matches for a Salesforce administrator to resolve manually.
For all remaining eligible new contacts, the integration creates new, matching supporter records and keep them in-sync moving forward.
How the Integration Handles Updates to Synced Supporters and Contacts
Updates made to synced supporters and contact records follow the Field Mapping rules set in the integration settings. For each field, there are two rules that apply to an initial sync between a supporter and contact as well as a set that applies to ongoing updates. Each time the integration syncs, any updates that have been made in either system will be applied bidirectionally according to these rules.
For example, if the First Name of a contact record in Salesforce is updated and the First Name field mapping is set to "Always use Salesforce value, even if it is blank." then when the integration syncs it will update Engage to match what’s in Salesforce. Conversely, if the field mapping was set to “Use Latest,” than any update on either system that was most recently committed will be applied in both systems.
Using the "Create an Update Entry in Salesforce" Mapping Rule
For any Standard Field, you can use Create an Update Entry in Salesforce as an ongoing rule to queue updates in Salesforce before they’re committed. This rule is designed to give you manual control over when an update from Engage is kept. It gives you the ability to keep contact information clean in Salesforce (as the database of record).
When used, updates to the field will be stored in the Salsa Engage Update object in Salesforce. The update entry will contain all standard fields along with the update made to the field requiring review. Salsa Engage will revert to the Salesforce value for this field on sync and allow the Salesforce manager to decide what to do with the update at their convenience.
In Salesforce, these Salsa Engage Update objects can be reviewed and then dismissed or used to update the contact.
If the update is applied, the update will be applied to the contact record and then update Engage on sync.
You can find a list of all pending Salsa Engage Updates under the App Launcher while using the Lightning Interface or as a tab in the Classic Interface. Search for Salsa Engage Update Queue.
In the integration settings, you can optionally set the integration to delete the synced contact or supporter record if a deletion occurs in either system.
When a contact record is merged with one or more contacts in Salesforce, the integration automatically records these merges and replicates the results in Engage. This includes moving any donations, activity records, email records, etc., to the winning supporter record.
Locating Synchronized Records In Engage
Salesforce records that have been synced to Engage can be identified by the presence of a Salesforce ID in the supporter record. To identify records synchronized to Engage, create a Supporter Query.
- Click Supporters tab > Query tab.
- Click the Create New Query button. The Create a Query page will open.
- Set the first line of the query to "Supporter Fields" "Salesforce ID" "Is Not Blank".
- Choose the fields you want to see in your query results.
- Save the query.
Locating Synchronized Records In Salesforce
Records synchronized from Engage to Salesforce have a unique Engage Supporter ID in Salesforce. You can generate a report in Salesforce that will search on Engage Supporter IDs that are not blank, similar to queries created in Engage that search for supporters with Salesforce IDs that are not blank.