The settings area, inside Engaging Networks, offers configuration options for the push and pull operations.
When contact data comes from Salesforce, if the field value is blank, then clear the field in Engaging Networks
When Contacts are pulled, if a field on the Contact is empty then clear the value in Engaging Networks for the supporter.
A use case that should be taken into consideration are new Contacts, being created in Salesforce, with Engaging Networks already holding data on those supporters.
Working with key stakeholders to have both systems be as close to each other, prior to launch, should reduce these types of errors. Defining user flows between teams will also address how your organization will be working with both systems.
Respect “EN Account ID” on the Contact record
This setting’s primary design is to help clients who are running multiple EN accounts into one Salesforce org.
When Contacts are pulled, the Engaging Networks will only pull Contacts whose engaging__Account_Id__c matches the client Id.
This has no relationship with the Account object or householding and for most integrations, will likely be unchecked.
Sync Contact data to Salesforce
Start the hourly job to push supporters as Contacts.
Upon enabling this sync method, an internal timestamp is configured to the ‘current’ time. Only supporters who are modified after this time will qualify to be pushed.
If you turn off the sync, this timestamp will be cleared. On re-enabling the timestamp will again follow the logic of using the current time.
A use case here is if you wanted to import a large file of supporters into Engaging Networks and not want that data to cause a large job update to Salesforce. You could turn off the sync, import and once the import has completed – re-enable the sync.
Engaging Networks utilizes Salesforce’s Bulk API to upsert supporters as Contacts. If Matching Rules is enabled, when Engaging Network’s receives Duplicate errors returned on the batch being imported – a secondary job will run to try find suitable Contacts based on the following rules:
Fuzzy match on First Name
Exact match on Email Address
Fuzzy match on Last Name
If a suitable match is found, the Id will be copied to the Contact Id and the supporter record eligible for re-push in the next Contact push.
Define how many rows of data will be pushed in each batch, as Contacts. It is recommended to have as high a batch size as possible, to help reduce queues when high volume contact updates are being made.
If the Batch Size is small and a large update is made across supporters, it may lead to Salesforce API limits being hit.
Sync Contact data from Salesforce
Start the hourly job to pull Contacts. By default all modified Contacts will be pulled.
There is an optional ‘Exclude’ filter, if there is a requirement to not have Engaging Networks pull all Contacts.
Sync Transaction data to Salesforce
Will enable the daily transaction sync to push supporter actions to Engaging Networks Staging Records