Once you have reviewed the configuration for the OneCause integration, this article helps you understand how data from OneCause translates to Virtuous CRM+. This article covers how all data, including Gifts, Event data, Projects, and more maps from OneCause to CRM+.
Gift Transactions
Transactions processed in OneCause sync to Virtuous CRM+ every three hours as pending transactions. They are, then, bundled for import nightly and available to review each day as part of your regular import process.
Standard field mapping for Gifts:
| Virtuous Field | OneCause Field | Notes |
|---|---|---|
| Transaction Source | N/A | Will be set as “OneCause” |
| Transaction ID | Supporter Activity ID | |
| Reference ID | Supporter ID | If Supporter Type is Company, will use Supporter Company ID |
| Name | Supporter Company Name | Only used if Supporter Type is Company |
| First Name | Supporter First Name | |
| Last Name | Supporter Last name | |
| Supporter Identity Email | ||
| Phone | Supporter Phone | |
| Address 1 | Supporter Address | |
| Address 2 | N/A | |
| City | Supporter City | |
| State | Supporter State | |
| Postal | Supporter Postal Code | |
| Country | Supporter Country | |
| Gift Date | Payment Date | |
| Gift Type | Payment Type | Google Pay, Apple Pay, and Free will all be mapped as “Other" |
| Amount | Activity Total Amount in Dollars | |
| Notes | Integration Description | |
| Is Private | Is Anonymous | |
| Segment | Various | See below |
| Project | Fund External ID | See below for details |
| Premium | Various | See below |
Segment Mapping
As detailed in our article on configuring the sync, there are customizable rules for mapping Segments with Gift Transactions in which you can set defaults, or catch-all Segments, and create custom mapping for specific Segments.
Segment Defaults
In the sync settings, you provide a default Campaign for event transactions and a Campaign and Communication for Fundraising Pages. These serve as the "home base" the sync uses for creating new Communications and Segments as needed.
When an event transaction syncs, the integration first looks to see if there are any custom mapping rules set for the event. If not, it checks to see if the event already exists as a Campaign Communication under the default Campaign. To do so, the integration looks for an exact match between the Event Name and the Communication Name. If there is no matching Communication, the integration creates it.
The integration, then, uses the Event Name, Purchased Item Type, and Event ID to see if a matching Segment already exists. If not, a Segment is created. The integration creates multiple Segments for each event, broken down by the Purchased Item Type in OneCause:
- Ticket
- Donation
- Sponsorship
- Live Auction
- Silent Auction
- Raffle
There may also be a Segment created for Fixed-Price Items (see below).
Custom Segments
If the above structure does not fit with your existing Campaign structure, you have the option to customize the Segment mapping instead for specific Events. Create the Campaigns, Communications, and Segments as you'd like, and then select the correct Segment for each of the above Purchased Item Type categories in the integration settings. Custom mapping always takes precedence over default rules.
Fixed Price Items
Fixed Price Items can represent many things in OneCause. They may be ticket add-ons, additional purchases related to an event, or a way to track specific donation efforts as part of an event. Because of their flexible nature, Fixed Price Items have their own rules for syncing to Virtuous CRM+.
By default, Fixed Price Items sync as purchases, which means they do not create Gift Transactions. Instead, these are logged in the OneCause Activity Custom Collection on a Contact record. This way, e-commerce amounts are not treated as Gifts, included in Receipting, or included in Contact giving totals for analysis and segmentation.
When synced as purchases, each transaction syncs via the Contact Import as Custom Collection data. Supporter data maps in the same way as the supporter data for Gift Transactions. The Custom Collection fields map as follows:
| Virtuous CRM+ Field | OneCause Field | Notes |
|---|---|---|
| Activity Type | Purchased Item Type | Will be “Fixed Price Item” |
| Activity Detail | Integration Description | |
| Activity Date | Payment Date | |
| Amount Paid | Activity Total Amount in Dollars | |
| Quantity | Quantity | |
| Event Name | Origin Name | Will be the Event Name from OneCause |
| Activity ID | Supporter Activity ID |
However, in the integration settings, you may choose to sync Fixed Price Items as Gifts instead. In this case, any Fixed Price Item transactions will be synced via a Gift Import, using the mapping specified above for Gifts.
When Fixed Price Items are synced as Gifts, you will also have the option to create Premiums for each Item. See Premium mapping below.
Premiums
To offset the value of any benefits received and ensure the tax-deductible amounts of Gifts are accurate, Premiums are automatically created for:
- Tickets
- Sponsorships
- Auction Items (live or silent)
- Raffles
- Fixed Price Items (if the option is selected in settings)
Each ticket type for each event is created as a unique Premium, as is each Sponsorship type, Auction Item, Raffle, and Fixed Price Item. The Price, Fair Market Value, and Cost for each Premium is set to the Activity Value in Dollars value from OneCause.
| Virtuous CRM+ Field | OneCause Field | Notes |
|---|---|---|
| Premium: each Ticket Type | Ticket type | |
| Premium: each Sponsorship Type | Sponsorship type | |
| Premium: each Auction Item | Auction Item | |
| Premium: each Raffle | Raffle | |
| Premium: each Fixed Price Item | Fixed Price Item | only if synced as Gift |
| Premium Price | Activity Value | |
| Premium Fair Market Value | Activity Value | |
| Premium Cost | Activity Value |
Projects
Projects in Virtuous are linked to Funds in OneCause. When a Fund is included on a OneCause transaction, if that Fund has an External ID set in OneCause, that ID will be mapped to the Project Code for a Gift in CRM+. If there is no External ID set for a particular Fund, Gifts designated to that Fund will not have a Project designation in CRM+.
Event Registrations
Because OneCause is an event platform, event registrations sync from OneCause to Virtuous. This data is synced separately from Gifts—meaning that if someone buys a single ticket to your event, you see both a Gift representing the transaction and a Contact import to capture the event attendee data.
Event tickets will be mapped to the Contact import as follows:
| Virtuous CRM+ Field | OneCause Field | Notes |
|---|---|---|
| Reference Source | N/A | Always set as “OneCause” |
| Reference ID | Supporter ID | If the ticket holder is not a “Supporter” on OneCause, then will use Event Guest ID instead |
| First Name | First Name | |
| Last Name | Last Name | |
| Phone | Phone | |
| Event ID | Event External ID | If there is no value set, then this will be excluded and the fields below will be used to populate the OneCause Activity Custom Collection instead. |
| Activity Type | N/A | Will be set as “Event Ticket” |
| Activity Detail | Ticket Type Name | |
| Event Name | Event Name | |
| Activity Date | Created Date |
As mentioned in the table above, if a OneCause Event is linked to a Standard Event in Virtuous CRM+, then each ticket holder will be added to the Event as an Event Attendee. If a OneCause event is not linked to a Virtuous Event, then the attendee data will be added to the OneCause Activity Custom Collection on the Contact record.
OK, that’s it! If you have other questions about the sync between Virtuous CRM+ and OneCause, be sure to check out our FAQ.