When our implementation team integrates Salsa CRM and Salsa Engage for you, the applications are linked together, and you can even launch Salsa Engage from Salsa CRM's Tools menu. They are designed to work in a highly complementary—but independent—manner. This document reviews how Salsa CRM and Salsa Engage work together.
Salsa CRM provides a robust constituent database and donor management system. However, Salsa CRM has few outbound engagement features and is primarily used for data management, cultivating donors, and running reports to understand your donor base and trends.
Salsa Engage is a powerful tool that is primarily focused on supporter engagement, including digital marketing, online fundraising, online advocacy, and peer-to-peer fundraising. However, Salsa Engage does not have the robust donor management features of Salsa CRM. For example, when looking to understand how your marketing efforts are performing, you would use Salsa Engage. When looking to know more about a single individual, you would use the Salsa CRM.
Combined, Salsa CRM and Salsa Engage seamlessly manage key supporter data and transactions, providing a powerful, all-in-one solution for managing supporters and outreach. Records can be selected in Salsa CRM and then pushed to Salsa Engage. For example, you might create a group in Salsa CRM as a target for an email outreach and then sync that group with Salsa Engage. Once records are pushed from Salsa CRM to Salsa Engage, changes to the record in either application will automatically be reflected in all of the fields that are common between the two applications.
Shared, Unique Database ID
Salsa Engage and Salsa CRM each maintain their own database, and when supporter records are in Salsa CRM and Salsa Engage, the two applications work together. To enable this coordination, supporters that have records in both applications are given a unique database ID called the Constituent UUID. This ID keeps records synchronized between the two applications. This isn't necessarily something you have to worry about. The ID is generated and managed automatically, behind the scenes, by Salsa.
Another powerful feature that you get when you use Salsa CRM with Salsa Engage is proactive deduplication. 'Proactive Deduplication' refers to what Salsa CRM does automatically with potential duplicate records that are pushed down to it from Salsa Engage. Salsa CRM reviews new records that were pushed down from Salsa Engage for data that may indicate a record already exists with that same information and gives you a list of these potential duplicates to review and resolve. Salsa CRM then pushes the deduplicated records back up to Salsa Engage. See Proactive Deduplication for Salsa CRM and Salsa Engage for details.
If you need to use a custom field that needs to be common to both applications, both applications feature a 'common' custom field type that shares between the two applications. If you create any custom fields in Salsa Engage, they are automatically synced to Salsa CRM and vice-versa. These display in the Common Fields node of the constituent record. In addition, Salsa CRM has additional custom fields for use cases in which you want to collect and store data that will not be used for online engagement.
Any custom fields that need access control in Salsa CRM must be created in Salsa CRM and cannot be shared to Salsa Engage. To do this, choose instead to create custom fields on the Salsa CRM Main Constituent screen or My Salsa CRM screen.
Fields That Are Shared Between Salsa Engage and Salsa CRM
Once a new supporter submits their information for the first time, or an existing supporter submits their information and some of it has changed, that information syncs to Salsa CRM within minutes through an automated interface between the two systems. However, Salsa CRM does not share information with Salsa Engage automatically. CRM data must be 'pushed' to Salsa Engage, either by syncing constituent records manually or through synced Groups or through the Advanced Query Wizard.
Salsa CRM and Salsa Engage are each specially suited to their own purpose. Consequently, not all fields are shared between the two applications. Any field that is not listed in the sections below is not shared between Salsa CRM and Salsa Engage. These include things like detailed email performance and donation form performance information.
Constituent Info Passed Between Salsa CRM and Salsa Engage
The following fields are shared automatically between Salsa Engage and Salsa CRM...
- organization type
- name, first
- name, middle
- name, last
- name, suffix
- name, nickname
- name, maiden name
- date of birth
- date, deceased
- government ID
- address (including the full country name or two digit, ISO 3166 country code)
- phone, mobile
- email, business
- phone, business
- fax number
- common custom fields
In addition, all custom field values of the type 'common' are shared between Salsa CRM and Salsa Engage.
Donation Info Passed From Salsa Engage to Salsa CRM
All of the above, plus the following donation-related information...
- donor name (last, title, first, last)
- donation amount
- received date
- payment type
- credit card (last 4 digits)
- credit card authorization code
- online dedication
- activity custom fields
View Activity Custom Fields from Salsa Engage
View Activity Custom Fields on a record-by-record basis: In Salsa CRM, open a constituent record, and then click Activities in the Explorer menu.
Single Sign-on for Salsa Engage
If your instance of Salsa CRM is integrated with Salsa Engage, you must have at least the Salsa Engage Supporter permission enabled in your Salsa CRM Role to see the Salsa Engage menu option in the Salsa CRM Tools menu.