This document describes when and how the integration syncs one-time or recurring Engage donation data to Salesforce opportunity objects, and how Ticketed Event or Peer-to-Peer registrations, donations, tickets, and purchasers link to the Salesforce opportunities and contacts.
Successfully submitted online Engage donations create Salesforce opportunities through the integration, based on the configured default Stage. Whenever the integration syncs, it will also link the opportunities to the matching contact record. If no contact record exists or still needs to be created (for example, if the contact is in the Salsa Engage New Supporter Queue) then the opportunity does not get created without an existing contact record to which it would be connected. This will prevent opportunities from being created without a contact.
The article on Setting Up the Integration discusses default opportunities that may be configured for successful, unsuccessful, and recurring donations. A default opportunity Record Type may also be configured and is optional.
How Donations Map to Salesforce
This diagram demonstrates how key data elements fit together between a donation in Salsa and an opportunity in Salesforce.
NOTE: Any imported donations that are in Engage prior to synchronization are not pushed to Salesforce.
Every piece of the transaction (each ticket, each optional purchase, each additional donation) will be recorded as a separate opportunity, not as part of the sum of the transaction.
Primary Campaign Source links the Campaign to the opportunity.
How Recurring Donations Map to Salesforce
Recurring donations submitted through Salsa Engage sync create a new entry in the custom object Salsa Engage Recurring Donation, which records the terms of the commitment. This diagram demonstrates how key data elements fit together between a recurring donation and installment payments in Salsa and the various tables in Salesforce.
Salsa Engage processes the donations at each interval (monthly, etc.), and the successful donations will sync to Salesforce as opportunities. These opportunities will additionally be mapped to the associated Salsa Engage Recurring Donation record.
NOTE: for NPSP users, the Salsa Engage sync will not utilize the built-in NPSP recurring donation functionality. The integration ignores the Recurring Donation object installed by NPSP and doesn’t update or map to any installments created by that functionality.
NOTE: In the future, we will provide the ability to pull opportunities from Salesforce to Engage. For now, it is just a one-way transaction from Engage to Salesforce.
How Events/P2P Transactions Map to Salesforce
Engage Event and Peer-to-Peer (P2P) activity pages support one or more purchases in a single page submission. Event tickets can include an additional donation, or even an additional item purchase, like walk t-shirts, etc. Each component of a submission, i.e., donation, ticket purchase, t-shirt purchase, creates a distinct opportunity in Salesforce. This diagram demonstrates how key elements fit together between Event/P2P transactions in Salsa and the various tables in Salesforce:
Note that for each of these Event and P2P submissions, a new entry is made in the custom object Salsa Engage Event Submission. Each opportunity created by the Event or P2P submission is related to the corresponding entry in Salsa Engage Event Submission and link out to the fields for that object. This allows you to build reports in Salesforce connecting the submission with each opportunity. This also separates donations from ticket purchases or other purchases made through an Event or P2P page, providing enhanced segmentation and total gift reporting.
The custom object called Salsa Engage Event Submission in Salesforce allows users to see opportunities connected to a single activity.
If someone purchases a free ticket to an event, they’ll only be added as a campaign member and no opportunity will be created.