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.

Salsa Engage and Salsa CRM are designed to work in complementary yet independent ways.

Salsa CRM includes a robust constituent database and donor management system, but has few outbound engagement features. Use it primarily for data management, cultivating donors, and running reports.

Salsa Engage focuses on supporter engagement, including digital marketing, online fundraising, online advocacy, and peer-to-peer fundraising.

When 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. 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

CRM and Engage coordinate by automatically issuing supporters with records in both applications a unique database ID called the Constituent UUID that keep records synchronized.

When Salsa Engage pushes records to Salsa CRM and Salsa CRM finds a matching user ID, this means that the constituent was synced previously.

The following updates are made in CRM:

Standard supporter fields - These include First Name, Last Name, Title, Suffix, Birth Date, and Custom Fields.
Supporter addresses - The Primary address is updated in Salsa CRM if the record from Salsa Engage matches the first alphanumeric string of the first line of the street address and 5-digit zip. A new address is created in Salsa CRM if the record from Salsa Engage does not match first line of the street address and 5-digit zip.
Supporter email address, Supporter phone number, or Supporter Social information - The data from Salsa Engage becomes primary and the original, Salsa CRM data becomes secondary.

When Salsa Engage pushes records to Salsa CRM and Salsa CRM does not find a matching user ID, Salsa CRM performs a search on full first name, last name, and email address.

If an exact match is found on first name, last name, and email, Salsa CRM updates the record just as if the incoming record had a matching user ID, or;
If there is not a full match, Salsa CRM searches its database for the first three letters of the supporter's first name + full last name OR complete primary email. If a match is found, the Proactive Deduplication service is updated, or;
If there is no match between the first three letters of the supporter's first name plus full last name OR complete primary email, Salsa CRM assumes that there is no match and creates a new, active record.

Proactive Deduplication

Proactive Deduplication is an automated service for Salsa CRM and Engage clients that removes duplicate records synced from Salsa Engage. Salsa CRM reviews new records for data that may indicate a record already exists with exact same information. Salsa CRM then produces a list of these potential duplicates to review and resolve. Salsa CRM then pushes deduplicated records back up to Salsa Engage. See Proactive Deduplication for Salsa CRM and Salsa Engage for details.

Custom Fields

If you want to use a custom field that is common to both applications, use the 'common' custom field type. If you create 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 other custom fields for collecting and storing 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 Shared Between Salsa Engage and Salsa CRM

Salsa CRM syncs new and updated records within minutes through an automated interface between the two systems but only shares information with Salsa Engage when the data are pushed to Salsa Engage, either by syncing constituent records manually, through synced Groups, or through the Advanced Query Wizard.

Each application has some data fields unique to that system. Any field not listed in the sections below is not shared by Salsa CRM and Salsa Engage, such as detailed email and donation form performance information.

Federal, state, and local congressional district information is identified in Salsa Engage and shared with the Salsa CRM constituent, with data stored in the Address section. Physical location, designated by Latitude and Longitude, is also shared with Salsa CRM.

Constituent Information Passed Between Salsa CRM and Salsa Engage

The following fields are shared automatically between Salsa Engage and Salsa CRM:

organization type
title
name, first
name, middle
name, last
name, suffix
name, nickname
name, maiden name
date of birth
date, deceased
gender
government ID
address (including the full country name or two digit, ISO 3166 country code)
Congressional District
State Upper District
State Lower District
County District
City District
Latitude
Longitude
Opt In Status
Opt In Date
Opt Out Date
phone, mobile
email, business
phone, business
fax number
common custom fields

Using Groups to Pass Constituent Info to Salsa Engage

Read the Salsa CRM article on how Salsa CRM passes Groups of constituents to Salsa Engage.

Donation Info Passed From Salsa Engage to Salsa CRM

All of the Constituent Fields plus the following donation-related information is shared automatically between Salsa Engage and Salsa CRM:

batch
donor name (last, title, first, last)
donation amount
received date
fund
campaign
appeal
payment type
credit card (last 4 digits)
credit card authorization code
online dedication
designation
activity custom fields

Salsa Engage donations paid online automatically sync with Salsa CRM and are automatically added to their own CRM donation batches. These batches are labeled SED [date] (Salsa Engage Donation).

View Activity Custom Fields from Salsa Engage

To view Activity Custom Fields on a record-by-record basis:

Open a constituent record.
Click Activities in the Explorer menu.
Click the Activity for which you want to view the Activity Custom Field.
- If the donation was made offline, for example, it will open the CRM donation record.
- If the donation was made online, for example, it will open the transaction record in Engage.

If you need an aggregate report of Activity Custom Fields, generate a constituent or donation Advanced Query. Activity Custom Fields have their own table.

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.