Combining iDonate’s digital donation platform with Salesforce’s NPSP Constituent Relationship Manager to provide transformative record management for the modern giving age.
BENEFITS OF INTEGRATION
iDonate’s Salesforce Integration is optimized specifically for the Salesforce NPSP to provide the best user experience possible. Our focus on integrating the iDonate system with NPSP allows iDonate to deliver support and updates to its clients beyond the industry standard.
How do we deliver this support? iDonate leverages our powerful Integration Exchange (iX) to send gift data from all iDonate giving channels to Salesforce using Standard and Custom Objects. iX allows the end user to configure field mappings to Standard Objects while automatically creating Custom Objects for fields unique to iDonate.
TECHNICAL OVERVIEW
Field Mapping
The iDonate Integration Exchange’s Salesforce Integration is designed to be an out-of-the-box-plug-and-play solution with the Salesforce NPSP. Therefore, we’ve mapped much of iDonate’s data to Standard Salesforce NPSP Objects by default.
We’ve also built Custom Field mappings to meet needs that Standard Objects can't. You can use Custom Field mappings to configure where and how you surface iDonate transaction data in your Salesforce NPSP Instance should you choose to do so.
Click here for our Salesforce Custom Field Mapping Guide
Gift Writing
When a donor makes a donation using an iDonate giving form, that information is captured in iX as a transaction. That transaction information is written into Salesforce and is located on the Opportunity, Payment and General Account Unit Allocation (GAU Allocation) records. If you choose to connect iDonate with your Salesforce org, please plan to login to both places regularly! You can monitor how successful data transfer is by using the Transaction History.
Please see the Single Opportunity example below:
One time donation – Opportunity Record in Salesforce
One-Way Sync
The iDonate Salesforce integration is a one-way sync. When records are created, updated, or changed within iDonate, they will be reflected within your Salesforce instance. When records are created, updated, or changed within Salesforce, they will not be reflected within iDonate. This ensures that your iDonate donation history remains a source of truth for donation and donor information.
Record Behavior
There are a lot of pieces that fit together to get your donor’s gift from iDonate’s giving form into your Salesforce instance, but to put it briefly a transaction payload is sent to iDonate’s Integration Exchange, which then organizes and sends that data in a digestible way to Salesforce using an API. In addition to the Opportunity, Payment and GAU Allocation records, the following records will be created or updated in Salesforce when donations are made:
- Contacts:
- Created in Salesforce when a donor gives to your organization for the first time
- Created in Salesforce when a supporter gives to a P2P fundraiser
- Updated in Salesforce when new information is entered and can be matched with an existing contact
- Accounts:
- Created as Households when a new Contact is created
- Campaigns:
- Created in Salesforce when a new iDonate Campaign receives its first gift.
- Created in Salesforce when a new iDonate P2P Fundraiser receives their first donation.
- GAU:
- Created in the same way as a Campaign, when the first donation allocated to a new iDonate Designation is created.
Important Note: If/when a donation is refunded in iDonate, the related Opportunity/Payment information will zero out.
Gift Syncing
To get your donor’s gift from iDonate’s giving form into your Salesforce instance, a transaction payload is sent to iDonate’s Integration Exchange (ix). The Integration Exchange then organizes and sends that data in a digestible way to Salesforce using an API. A few examples of how these systems interact are listed below:
- Contacts are created in Salesforce when a new donor gives to your organization for the first time.
- Contacts are created in Salesforce when a supporter gives to a P2P fundraiser.
- Campaigns are created when a new iDonate Campaign receives its first gift.
- Campaigns are created when a new iDonate P2P Fundraiser receives their first donation.
Donor Matching
Your Organization can control how the integration checks for existing donor records (Contacts) in Salesforce using the Matching and Duplicates rules within Salesforce. This is a process defined by Salesforce, and our integration follows that best practice directive to handle matching. These Duplicate Matching rules are critical for the iDonate integration to function, so that the iDonate integration knows how to match donor records and decide whether to use an existing record or create a new record. Your duplicate rules are best used as a “Report” Only,” not Alert.
Duplicate Rules setup - enable “Report”, do not enable “Alert”
The following links provide further details on how to set up and manage duplicates in Salesforce and NPSP.
Duplicate Management | NPSP Contact Merge
IMPLEMENTATION PROCESS
Curious about the implementation process when integrating iDonate with Salesforce? Click here for our iDonate --> Salesforce Implementation Guide!