The Salesforce and Engaging Networks connector app should be configured and maintained by a Salesforce Administrator. Given the potential risks to data integrity posed by an incorrect setup, the ultimate responsibility for the setup rests with you. It’s recommended to take the Academy course and familiarise yourself with the associated Salesforce Connector Documentation. Engaging Networks would advise working closely with an expert Salesforce integration specialist and liaising closely with the necessary stakeholders at your organisation.
The Salesforce connector (called the Engaging Networks connector app in Salesforce) connects Engaging Networks to your Salesforce CRM, allowing you to sync contacts and transactions seamlessly.
To discuss licensing or to upgrade to the latest version, please contact your Account Success Manager or submit a request via the Salesforce AppExchange.
Salesforce Connector | Engaging Networks Connector App: Documentation
It is not recommended to attempt to install or set up the Salesforce Connector without familiarising yourself with this documentation:
-
Contact(s) mapping, syncing, merging and duplicate management
-
Transactions mapping, template rules and campaign linking
-
Transaction Mapping to Staging Record Process
-
Mapping Rules Templates
-
Mapping Rules Template Collection
-
Salesforce Connector: Installation and Setup
Once you’ve familiarised and understood the documentation, you can follow the steps below to install and set up the connector:
Salesforce Connector Release Notes - Version 1.4
We are excited to announce version 1.4 of our Salesforce Connector, which introduces a new architectural foundation required for our latest integration options as well as several key enhancements and features that will better serve our Salesforce clients.
Key New Features
Enterprise Salesforce Connector
Our newly released Enterprise Salesforce Connector allows for high-frequency transaction data syncing between Engaging Networks and Salesforce. Unlike the standard nightly sync, this feature pushes and processes transactions approximately every 20 minutes. On the Salesforce package side, we have made several major enhancements to provide the option to process staging records in near real-time when using the enterprise EN feature.
Several steps are required in order to enable this real-time processing in the Salesforce package. For more information and to find setup steps, view the Supportal article here. Reach out to your Account Success Manager if you are interested in enabling the Enterprise Salesforce Connector on your service plan.
This feature requires Salesforce Connector package 1.4 or later and to update your service contract with Engaging Networks to pay for the more frequent sync. Reach out to your Account Success Manager for more information.
Kindsight Ascend Integration
Engaging Networks now offers a specialized integration path for organizations using Kindsight Ascend. As an enterprise-grade fundraising CRM built on the Salesforce platform, Ascend requires a specific data flow to ensure your constituent and gift data are processed accurately through its unique architecture.
This integration utilizes a modified version of our standard Salesforce Connector, designed to work with Ascend’s Interims and RTv2 objects to ensure data is cleaned and deduped before it enters your database of record. By enabling "Sync Extended Supporter Details" in your sync settings, (requires package 1.4 or later) supporter biographical data is bundled into the Transaction Sync, allowing for accurate routing into Ascend’s specialized objects.
Implementation requires upgrading to the latest Salesforce Connector package and importing the provided Ascend-specific mapping rules, among other setup steps. For detailed technical specifications, activation requirements, or assistance with your implementation, please review this Supportal article or contact our Support team.
This feature requires Salesforce Connector package 1.4 or later.
Support for Person Accounts (Nonprofit Cloud)
Functionality has been added to support syncing Contacts into environments using Nonprofit Cloud (NPC) and Person Accounts.
Previously, on the duplicate check from Engaging Networks to Salesforce when syncing a new supporter, when a Person Account was matched, the endpoint defaulted to returning the Account ID instead of the required Contact ID.
Updated Logic: The system will now correctly return the Contact ID and write it back to the supporter record when a Person Account is found.
Additionally, we have ensured that merges on Person Account records are now properly reflected in Engaging Networks when using the “Reflect merges” setting in your sync.
Contact Top Up Rule - Duplicate Check
A new option on the Matching Rule object allows the matching process to use existing Salesforce duplicate rules instead of the static logic defined per rule. To enable this, set the Matching Type to "Duplicate Rules” inside of the Contact Top Up’s matching rule to utilize your native Salesforce deduplication logic. This “Duplicate Rules” setting is now also available for other mapping rules if you find there are other matching scenarios it would help address.
Recommended Optimizations for Contact Top Up Rule
Given the additional options on the Contact Top Up rule, we would recommend implementing the following enhancements to your existing rule to take advantage of the new features. Update your Contact Top Up mapping rule after installing the latest package:
-
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.
Bug Fixes and Performance Updates
-
Mapping Rule “Save & Close” error: The "'Page doesn't exist' error on mapping rule save and close" has been resolved.
-
Merge Audits tab: There is now a Merge Audits tab available in the EN Connector App to make it easier to track merges that should reflect in Engaging Networks.
-
Supporter data fields added to ENSR: Additional supporter data fields have been added to ENSR records to house data that flows when “Sync extended supporter details” is enabled in Engaging Networks. This is primarily to support the Kindsight Ascend version of the integration. See the Supportal article here.
-
Transaction Date/Time conversion issue: Previously, an issue caused the Transaction Date/Time field to double-convert timezones, resulting in the wrong time being displayed on ENSR records. This package introduces a fix:
-
A new field, Transaction_Date_Time_v2__c, now captures the correct date/time via a trigger when a record is created or updated.
-
The existing Transaction Date/Time field has been updated to reference this new correct value.
-
Action Required: If your organization implemented local workarounds (e.g., custom formulas or automation) to correct the previously incorrect Transaction Date/Time field, you must now remove these local fixes, as the field now contains the correct value by default.
-
Note: This change only affects new or updated ENSR records and will not fix existing records.
-
How to Update your Package
Contact Engaging Networks Support to get the link to update your current package version.
Note: While updating to the latest Salesforce package is not required to maintain your core data sync, we highly recommend it. Updating ensures full feature compatibility and access to recent fixes.