Virtuous CRM enables you to track donor history, generate and send multiple types of donation receipts, and manage communication with your donors. Integrating your RaiseDonors account with Virtuous will simplify these tasks and give you the full financial picture for your donors!
There are four events that can trigger RaiseDonors an event within Virtuous CRM:
- New Donation
- Pull donation history for donor portal
- Refunding donation
- Updating donor information
Note: we're walking through integrating the Virtuous integration, not the Virtuous Sync integration. Read more about Virtuous Sync here.
Data mapping
RaiseDonors data will flow to Virtuous fields using these mapping fields below.
Note: this is applicable to each project in a donation. If a donation has multiple project designations, then this mapping will be applied multiple times to send gifts to Virtuous. Certain fields will remain the same in this situation and be pushed into Virtuous multiple times (ex: RaiseDonors.Donation.Id, DateCreated, SourceCode, Donor info, etc).
RaiseDonors Data | Virtuous Data |
Donation.Id | N/A |
Donation.Amount | Gift Amount |
"Once" or "Monthly" for recurring gifts | Pledge Frequency |
Donation.DateCreated | Gift Date |
Donation.Comments + Simple or Verbose Notes (*) | Gift Notes |
"Credit Card" or "ACH" depending upon gift type | Gift Type |
card brand (if gift type = CC) | CreditCardType |
empty value, not used | Project Id |
Donation.SourceCode | Segment Code |
Donation.Donor.FirstName | First Name |
Donation.Donor.LastName | Last Name |
Donation.Donor.Id | Reference ID |
Donation.Donor.Email | |
Donation.Donor.Phone | Phone |
Donation.Donor.BillingAddress.Address1 | Address1 |
empty value, not used | Address2 |
Donation.Donor.BillingAddress.City | City |
Donation.Donor.BillingAddress.State | State |
Donation.Donor.BillingAddress.Postal | Postal |
Donation.Donor.BillingAddress.Country | Country |
If Multiple Projects... | |
Donation.Project[x].Amount | Project Amount |
Donation.Project[x].Code | Project Code |
Donation.Project[x].Name | Project Name |
If Premium... | |
Donation.Page.ProductCode | Premium Code |
Donation.Page.ProductName | Premium Name |
Donation.Page.QuantityIncluded |
Premium Quantity |
If Anonymous... | |
isPrivate=true |
Private Gift |
If Media Outlet... (note: these must manually be kept in sync across platforms) |
|
Media Outlet Code |
Media Outlet |
If Shipping Address (with Product)... (note: if these custom fields in Virtuous are not created, the shipping address will be included in the gift note) |
|
Shipping Address |
Custom Field: Shipping Address |
Shipping City |
Custom Field: Shipping City |
Shipping State/Province |
Custom Field: Shipping State/Province |
Shipping Postal Code |
Custom Field: Shipping Postal Code |
Shipping Country |
Custom Field: Shipping Country |
*RaiseDonors Simple and Verbose notes will be mapped to Virtuous Gift Notes and will include the following:
Simple notes:
- RaiseDonors Donation ID
- Authorization # from gateway
- Recurring or one-time donation
- Referring URL
- Transaction ID
- Page
- And any comment that may be included with the donation
Verbose notes:
- RaiseDonors Donation ID
- Authorization # from gateway
- And any comment that may be included with the donation
- Test mode?
- Recurring?
- Payment type (cc / ach) and card brand if CC
- Motivation code
- Source code
- Referring URL
- Google UTM codes
- IP Address
- If premium, premium code and name
- If media outlet included, media code
- Shipping address information, if included
Gifts to Multiple Projects
A donation in RaiseDonors must be attributed to a Project. If a donation is only attributed to one project, then only one gift will be created in Virtuous. It's possible for a donation in RaiseDonors to be allocated across multiple projects. Here is how a page/campaign can be set up to support multiple projects.
It's important to understand that if a donation is attributed to multiple projects, then 1 gift with multiple designations will be created in Virtuous. In the example below, 1 gift will be created in Virtuous:
Gift #1 - $75
Designation #1 - $50
Designation #2 - $20
Designation #3 - $5
Recurring Donations
Regarding recurring donations that may or may not have an associated premium, the integration works as follows if the donation is a premium (meaning it has a SKU).
- If it's a one time donation, include the SKU information.
- If it's the first instance of a recurring donation, include the SKU information.
- If it's a second, third, etc (n+1) recurring donation, it does a check to see if there is a SKU for the "Recurring Product Code". If a SKU exists there, then the system includes the recurring product SKU/Code with the donation. If no Recurring product code SKU exists, then the donation is sent as a normal donation, with no premium/sku information.
The original source code for the initial recurring donation will remain with each future donation from that recurring profile. However, there is an override feature if you wish to force a specific segment code for all recurring donations.
Synchronizing Virtuous Contact ID with RaiseDonors
When RaiseDonors pushes a donation to Virtuous, the RaiseDonors Donor ID is also included and stored in Virtuous. This is key as this is how the donor portal history data is retrieved. Additionally, RaiseDonors will ping Virtuous once a day to acquire the Contact ID and store this value locally in RaiseDonors.
Organization vs Individual giving
RaiseDonors supports the distinction between a donor and an organization when integrating with Virtuous. If the organization name is provided with a donation, then the donation will be sent to Virtuous as an 'Organization'.
ISO codes for Country and State
RaiseDonors allows you to customize the formatting of addresses when sending data to Virtuous. Specifically, the Country can be formatted in:
- ISO3 ex: USA
- ISO2 ex: US
- Full Text ex: United States
The State can also be formatted as:
- ISO2 ex: TX
- Full Text ex: Texas
Tax deductive vs Non-Tax deductible gifts
In the world of RaiseDonors, we don't yet track if a "page" or "project" or "donation" is tax deductible or not. RaiseDonors always assumes a donation is tax deductible. But in the realm of Virtuous, there is the ability to track if a gift is tax deductible or not.
To control the gift coming into Virtuous as tax deductible or not, it's a matter of placing the donation into the appropriate Project in Virtuous.
Looking at the mapping chart, you can see that the RaiseDonors "project" maps to the Virtuous "project". If the donation in RaiseDonors is attributed to "Project A" and in Virtuous "project A" is setup to be tax deductible, then the gift will be seen as tax deductible in Virtuous.
However if in virtuous "project A" is not setup as tax deductible, then the gift will not been seen as tax deductible in Virtuous.
The designation of a gift to be tax deductible vs non-tax deductible is all controlled thru the setup of the project in Virtuous - and the mapping of the project in RaiseDonors to the project in Virtuous.
Fair market value
RaiseDonors does not directly send fair market value to Virtuous through this integration. Yet, RaiseDonors does allow you to provide FMV information - and this is used in various places (receipts, donation data, etc).
Virtuous requires you to specify the FMV at the "premium" level when creating a new premium in the Virtuous environment. When a donation comes into Virtuous from RaiseDonors, the premium "code" configured in RaiseDonors will be matched to a premium "code" in Virtuous. Once the match has been established, Virtuous will then apply the FMV settings it has locally, to the donation.
To ensure FMV calculations are correct in both RaiseDonors and Virtuous, ensure that you are configuring the FMV data in both systems - before donations take place.
Recurring donations and Pledges
RaiseDonors does not directly support the concept of a pledge. A donation is either recurring or not. However, Virtuous does support pledges. The pledge feature in Virtuous can be globally enabled or disabled.
When RaiseDonors receives the first recurring donation in a schedule, the integration with Virtuous will set the frequency to "monthly". This is picked up by Virtuous and the system auto-creates a pledge for that gift, if the pledge feature is enabled.
There are a few scenarios that lend itself to a poor experience with pledges. RaiseDonors has no way to contact Virtuous to notify Virtuous that a recurring schedule has been modified. The donor could have changed the amount, could have terminated the schedule, etc. The update to the pledge in Virtuous will be a manual process.
Donor Portal
RaiseDonors collects data real-time in the donor portal when viewing giving history. The data returned from Virtuous contains transactions collected outside of RaiseDonors. That data is then merged with any/all donations processed thru RaiseDonors (including recurring) and displayed to the donor.
Virtuous has contacts and individuals. By default, the contact is mapped to the donor in RaiseDonors. Meaning a donor may see the entire household giving history when viewing their giving history.
Only donations processed thru RaiseDonors are available to have the email re-sent. And only donations processed through RaiseDonors are able to display Gift Aid status (if available).
United Kingdom Gift Aid
RaiseDonors supports Gift Aid for organizations processing in GBP thru their gateway. To facilitate Gift Aid requests from the donor into Virtuous, you can configure a custom field to collect the 'date' of the Gift Aid request with the associated donation. Virtuous has recommended providing a custom field named 'Gift Aid Submit Date'. The value sent along in this custom field will be the creation date of the donation, in your organizations time zone. Ex: MM/dd/yyyy.
How is data imported into Virtuous?
RaiseDonors sends data in near real-time to Virtuous, but that doesn't mean it's ready for querying, reports, and/or viewable in Virtuous. To see how that process works, please check out Virtuous Support.