​
Salesforce NPSP Overview

The Salesforce Nonprofit Success Pack (NPSP), managed by WeGive but editable by users, is the most flexible and powerful integration that WeGive offers, and the most powerful, adaptable platform for connected donor experience with a marketing automation and fundraising platform in one that works out of the box, available for Salesforce NPSP.

​
Integration with WeGive

Our donor experience platform (WeGive) integrates with Salesforce NPSP to provide:

  • Real-time donor data synchronization
  • Automated gift processing
  • Donor portal functionality
  • Campaign and appeal tracking
  • Custom reporting and analytics
  • Omni-channel marketing sends
  • Transactional messaging
  • Marketing automation system
  • Consent management
  • MORE AAAA

​
WeGive Syncs to the Standard Salesforce NPSP Objects (At least that’s what we suggest!)

​
The following standard Salesforce NPSP objects are most relevant to our implementation by default (some are standard Salesforce objects, some are standard with NPSP only):

Accounts, Contacts, Campaigns and Campaign Members, Opportunities and Payments, Recurring Donations, Soft Credits, General Accounting Units and Allocations **are all standard, default objects in Salesforce NPSP **and sync to standard, default objects in WeGive.

Although you do not have to, we always suggest that you sync your WeGive platform to the standard objects in NPSP: trust the Salesforce well-architected data model.

This documentation provides a dedicated page for each of those data objects, where we give you our suggested field mapping based on the Salesforce default fields for those objects. WeGive and Salesforce can sync on any custom fields or objects, but we do suggest you use the standard data model and the existing fields to optimize for scalability.

​
Accounts

Accounts sync into WeGive as households and companies, so we can automatically relate all of your marketing (activities, consents, and segmentation), all your fundraising (web sessions, giving conversion, and fundraising performance), and all your post-donation experiences (impact reporting, tax-receipting, and analytics) with the correct contact, campaign, soft-credit and opportunity/payment relationships - all based on Salesforce ID instead of static data created outside of Salesforce.

​
Contacts

Contacts sync into WeGive as individual supporters and are based on their Contact ID. All objects related to contacts (and their fields) are pulled into WeGive as and then WeGive is able to help you segment those contacts based on their historical data in Salesforce, recognize them when they interact with your marketing, giving site, or portal, and personalize what they see or experience in order to give them a better donor experience and maximize your digital relationship.

WeGive also gives organizations the ability to import any number of ‘Marketing Contacts’ into WeGive from another integration or manual import. This allows you to _(optional) _not sync these individual supporters to Salesforce, and gives you the ability to _(optional) _sync those contacts to Salesforce only when they perform an action, like donating for the first time (which is also customizable).

We do not suggest that you sync Salesforce leads into WeGive as marketing contacts, but that you reserve marketing contacts for external systems outside Salesforce, enabling those systems to finally provide a unified view of data next to and with Salesforce.

​
Campaigns and Campaign Members

Campaigns sync into WeGive as Campaigns. When creating campaigns in WeGive, you can select a single pre-existing parent Campaign in Salesforce, giving you the flexibility for an infinite number of hierarchies, complete individuality and sibling equality for all campaigns, or the ability to roll every campaign up under a single parent Campaign. Campaign membership syncs to campaign membership in WeGive, but we do not suggest you import all historical campaign memberships. Depending on your Salesforce agreement and data storage, you may not want to sync campaign membership at all - so consult with your WeGive implementation lead before connecting those objects.

​
Opportunities and Payments

Opportunities and Payments sync to Payments in WeGive, and the nuance of the opportunity type and stage is taken into account, along with payment type and other meta data that’s highly relevant for tax receipting, revenue categorization, and portal visibility.

​
Recurring Donations

Recurring Donations sync to Recurring Plans in WeGive. You do not have to sync recurring plans in WeGive to the standard NPSP object for managing recurring plans, but we suggest that you do. This is a notable departure from how other fundraising platforms have historically handled recurring donation sync in Salesforce as they have typically sent data one-way into Salesforce on a custom object for recurring plans. Using the default NPSP object and syncing bi-directionally allows for powerful, yet flexible administrative control on recurring plan billing across systems and provides your team with the ability to leverage offline recurring plan data and acquire plans into a more sustainable portal system with special automation and workflows made specifically for acquiring existing recurring donors into a digital experience.

​
Soft Credits

Soft Credits in Salesforce can mean 3 different things: Account Soft Credits, Partial Soft Credits, and Opportunity Contact Roles. As we explain in the dedicated Soft Credit section, WeGive syncs to Account Soft Credits and Partial Soft Credits by default. These are important so that your marketing team can use this data to segment audiences and so those donors see what they are supposed to see in their portal for their giving history, for their impact stories and numbers generated by WeGive, and for the Tax Statements generated by WeGive (not to mention the same data in their related household and company views).

​
General Accounting Units and Allocations

WeGive integrates with all your GAUs and Allocations in Salesforce. GAU sync allows us to give your marketing and stewardship roles excellent historical segmentation for donor portal impact reporting, marketing communications and data/performance analysis, but also custom Designation Lists or URL-based checkout rules that give your IT team what you need for running new or complex existing checkous with thousands of GAUs without sacrificing your desired user experience or your data model integrity or risking manual cleanup on the backend.

​
WeGive Also Syncs to Custom Objects in Salesforce (That we can provide you in a managed package)

​
The following custom Salesforce objects are most relevant to our implementation for users who want more control inside of Salesforce.

Pledges, Payouts, Events and Event Registrations, Communication Lists and Communication Consents, and Fundraisers **are all custom objects in Salesforce provided by WeGive’s managed package **and sync to standard, default objects in WeGive.

Although you do not have to, we always suggest that you sync any of the default WeGive objects that don’t have a standard objects in NPSP with a custom object provided by our managed package: trust WeGive’s well-architected data model for the objects ‘lacking’ in NPSP.

This documentation provides a dedicated page for each of those data objects.

​
Pledges

There is not an ideal default object in Salesforce NPSP for Pledges. WeGive provides you with a free object for Pledges in the managed package.

​
Payouts

There is not an ideal default object in Salesforce NPSP for Payouts, especially as it relates to reconciling donations based on initiated date with the ability to take designation, revenue type and donor type into account. WeGive provides you with a free object for payouts in the managed package.

​
Events and Event Registrations

There is not an ideal default object in Salesforce NPSP for Events, Event Registrations and associated event revenue. WeGive provides you one that syncs perfectly with your marketing platform and giving platform, so you can run events without having to go to another platform that creates another fragmented data silo.

​
Communication Lists and Communication Consents

There are objects in Salesforce for Communication Subscriptions and Consents to those, however, they are only available through marketing products in Salesforce and are not made for Nonprofits. WeGive provides a custom object to manage multi-channel communication consents (Email, SMS, Direct Mail, Portal Messaging) and any number of public or private communication lists.

​
Support and Resources

​
Getting Started

To work with our NPSP implementation, you’ll need: Access to our Salesforce instance, appropriate security permissions, and an understanding of basic NPSP concepts