Once you've configured the Classy integration, you'll have some options for mapping your Classy data to Virtuous. In the Sync Settings, you'll configure many of your data settings. Here, we'll dive in on mapping specific data, and talk about some of the rules the sync feature uses in order to map data correctly.
Field Mapping
For starters, you'll have to option to customize mapping for specific fields. The available fields will include custom fields in Virtuous and custom questions in Classy, along with a few standard fields.
Just select the correct Virtuous field on the left and then the correct corresponding Classy field on the right. Make sure to click on the plus icon to save your entry, which will also allow you map another set of values (if needed). This mapping is only used if the Campaign Mapping toggle is off. When Campaign mapping is used, any Classy Custom Questions will be mapped to Custom Fields in Virtuous, but only if the field names are an exact match.
Campaign Mapping
If you wish to customize Campaign mapping, you'll need to toggle the "Campaign Mapping" setting to on (blue). Then you can select specific Classy Campaigns and map then to the correct Virtuous Campaigns and Campaign Communications.
As when mapping individual fields, make sure to click the plus icon when setting your mapping.
The Virtuous Connect Sync will map Campaign data using a set of rules that will vary depending on the type of Classy Campaign used and the settings configured for the sync. The sync will also dynamically create new Segments in Virtuous as needed, eliminating the need to continually monitor Peer-to-Peer fundraiser signups.
We'll take a look at the settings for mapping Peer-to-Peer Campaigns to Virtuous first.
Peer-to-Peer Campaign Mapping
For Peer-to-Peer Campaigns, connecting the Classy Campaign with the correct Virtuous Campaign in the sync settings will allow Virtuous Connect to create Campaign Communications and Segments in Virtuous as gift transactions are received. If a gift has a Fundraiser, then that Fundraiser will be set as the Segment for the Gift. As a reminder, in Virtuous, each Gift is linked to a unique Segment, which in turn is part of a Campaign Communication, which in turn is part of a larger Campaign. For transactions linked to a Fundraiser, the hierarchy will look like this:
Virtuous Object | Classy Value |
Campaign | Campaign |
Campaign Communication | Fundraising Team |
Segment | Fundraiser |
When creating Segments for individual Fundraisers, the sync will search for matching Contacts in Virtuous and automatically set them as the Fundraiser for that Segment, making it easy to see what someone has raised right from their Contact record in Virtuous. In cases where an exact match cannot be identified, you will need to manually add a Contact to the new Segment after it has been created.
There may be cases when a gift is made to a Fundraising Team instead of a specific Fundraiser. In these cases, the Fundraising Team will be set as both the Campaign Communication and the Segment.
Virtuous Object | Classy Value |
Campaign | Campaign |
Campaign Communication | Fundraising Team |
Segment | Fundraising Team |
This structure will allow for clear reporting at the Campaign, Team, and individual Fundraiser level.
Fundraising Campaigns
For non-P2P Campaigns, the Campaign mapping logic is different. If a transaction does not have a Fundraiser or a Fundraising Team, then the sync will look for Source Codes. These are custom values that can be included in a giving URL when sending a fundraising email or even on a specific web page. These codes can then be mapped back to Virtuous with a transaction.
In order to utilize Source Codes, you will need to first create your Campaign, Campaign Communication(s), and Segment(s) in Virtuous. Virtuous will be the source of truth for your Segments in these cases. Then, you can use a Virtuous Segment Code as the first Source Code for a Classy giving URL. (Classy allows up to two Source Codes for a giving URL; only the first will be mapped as the Segment Code. The second is fair game for any other tracking codes you'd like to use!)
For example, if your giving form is at this URL:
And you'd like to track Gifts made on that page using Segment Code "ABC123," then your URL with the Source Code would be:
https://example.org/?c_src=ABC123
Whenever a donor clicks on this link to make a donation, their Gift will import to Virtuous with "ABC123" as the Segment Code.
If a matching Segment cannot be found, the sync will create a new Segment using the Campaign and Campaign Communication specific in the sync settings. This is not recommended, as Segment Codes in Virtuous must be unique, but there is no similar restriction on Source Codes.
If a transaction does not have a Fundraiser, a Fundraising Team, or a Source Code, but it is part of a Campaign that has been Mapped to a Virtuous Campaign and Campaign Communication, then a new Segment will be created, using the Classy Campaign ID as the Segment Code.
Tributes
If a transaction includes Tribute information, then a corresponding Tribute will be created in Virtuous. The Tributee and Acknowledgee data will be mapped directlt from Classy.
Events
When using Classy for Event Registration each Ticket purchase will come through to Virtuous as a Gift. Registrants will be mapped to existing Individuals, or new Contacts can be created in the Gift & Contact Import Tool. All registrants will be set as Event Attendees on the Event in Virtuous.
Managing Project Data
It is strongly recommended that every Gift in Virtuous should have both a Segment and a Project. The sync will automatically handle Segments, but you will need to manage Projects to make sure data in Classy matches data in Virtuous.
In Classy, this will require creating Program Designations. As you create your Program Designations, you'll want to ensure that they match the data in your Virtuous Projects. The mapping from Classy to Virtuous for this data will be:
Program Designation Name - Project Name
External ID - Project Code
Note that both must match (Designation Name must match to Project Name and External ID must match to Project Code) in order for Project data to sync correctly for your Gifts.