The Enterprise Salesforce Connector allows for high-frequency data syncing between Engaging Networks and Salesforce. Unlike the standard nightly sync, this feature pushes and processes transactions approximately every 20 minutes.
Prerequisites
Before enabling high-frequency syncing, ensure your organization meets the following requirements:
-
Salesforce Package: You must be on the latest Salesforce package version (version 1.4 or higher).
-
Provisioning: This is a paid enterprise feature. Once contracted, you must submit a support ticket to have the high-frequency sync enabled on the Engaging Networks side.
Required Salesforce Configuration
Once Support has enabled the back-end setting, the Salesforce Admin must complete these steps to initialize the service:
Prepare Existing Records (Avoid Duplicates)
To prevent the new engine from re-processing legacy data, you must flag all existing Engaging Networks Staging Records (ENSR) with a new Batch ID value.
-
Use a Data Loader tool to export all current ENSR records.
-
Update the
Batch_Id__cfield with a unique dummy value (e.g.,DAILY_SYNC_2026). -
Complete the upsert. If this field is empty, the mapping engine will treat them as new records and may create duplicates.
Failing to add a Batch_Id__c value to existing ENSR records will create duplicate records in your Salesforce organization.
Enable Dynamic Batching
Navigate to Setup > Custom Code > Custom Metadata Types and find EN Settings.
-
Click Manage Records.
-
Edit
Batch Type-
Set value to:
Dynamic
-
-
(Optional) To adjust the gap between syncs, edit the
Dynamic Batch Frequencyrecord. The value is in seconds (default is60).
When Batch Type is set to Dynamic in the Metadata, the regular Process Mapping Rules job will not run, regardless of it being setup.
Data Processing Rules
The Enterprise Connector changes how specific data types are handled:
|
Data Type |
Sync Frequency |
Method |
|
Transactions (Fundraising, Advocacy, Events) |
~10-20 Minutes |
Dynamic Batch Engine |
|
Contact Data (Pull/Push) |
~20 Minutes |
Standard Sync |
|
Email Engagement (EBC, MBC, SBC) |
Once Daily |
Standard Processing |
|
Manual Supporter Updates (MSU, MSC, SSU, SSC, HSU) |
Once Daily |
Standard Processing |
The "Contact Top Up" Rule
Because transactions may arrive in Salesforce before the full Contact sync has finished, we recommend configuring the Contact Top Up rule in your Mapping Rules:
-
Enable Duplicate Rules: In the Contact Top Up Matching Rules, update the Matching Type to Duplicate Rules to utilize your native Salesforce deduplication logic.
-
Sync Extended Supporter Details: To create fuller contact records from this rule, enable “Sync Extended Supporter Details” under Sync Settings in Engaging Networks (requires package 1.4 or later), then map your preferred biographical fields under Mapping Items.
-
Prevent Unintended Syncs: Add a mapping item to set EN Push = TRUE. This signals to your flow rules that the update originated from Engaging Networks, preventing data from being incorrectly queued for sync back to EN and protecting your existing opt-in data.
Troubleshooting Recommendations
-
Unlike the standard Connector, if you encounter errors from Staging Record processing, you will need to clear both the Error Details field AND the Batch ID field in order for it to be picked up again for re-processing.