Virtuous Integration Overview

WeGive's Virtuous integration provides bi-directional sync between your WeGive platform and Virtuous CRM. Once connected, donor records, transactions, recurring donations, funds, campaigns, and contact information stay in sync across both systems automatically.

This article covers what the integration does at a high level. For setup steps, see Connecting WeGive to Virtuous.

What Data Syncs

The integration keeps the following data in sync between WeGive and Virtuous. All data types sync bi-directionally, meaning changes made in either system will be reflected in the other.

Sync Timing

Data flows between WeGive and Virtuous on two different schedules depending on the direction:

WeGive to Virtuous syncs in real time. When a donation is made, a donor is created, or a record is updated in WeGive, that data is pushed to Virtuous immediately.

Virtuous to WeGive syncs automatically every 15 minutes. WeGive pulls the latest changes from Virtuous on this interval. You can also trigger a manual sync at any time from Data > Integrations.

Integration Modes

WeGive supports two modes for sending donation data to Virtuous:

Batch Integration (Recommended) groups donations into batches and sends them to the Virtuous Import Tool. This gives your team a chance to review, validate, and match donors before the data is committed to your Virtuous database. Batch mode also reduces API calls, which helps avoid rate limit issues with larger donation volumes. For a full walkthrough of how the batch workflow and Import Tool work, see Batch Integration & the Virtuous Import Tool.

Real-Time Integration pushes each donation directly into your Virtuous database the moment it's received. There is no review step. This mode works well for organizations with low donation volume and minimal duplicate risk, but it comes with a higher chance of hitting Virtuous API rate limits and no opportunity to catch data issues before they enter your CRM.

You select your integration mode during setup. See Connecting WeGive to Virtuous for details.

Virtuous API Versions

WeGive supports two versions of the Virtuous API:

Version 1 (v1) identifies contacts using a single Virtuous ID. This is the original API structure.

Version 2 (v2) identifies contacts using both a contact ID and a contact individual ID, which provides more precise matching for organizations that manage individual contacts within larger household or company records.

Both versions support the same integration features. The difference is in how donor records are identified and matched between the two systems. You'll select your API version when connecting the integration. If you're unsure which version your Virtuous account uses, check with your Virtuous account representative or see Connecting WeGive to Virtuous for guidance.

What This Integration Does Not Support

Not everything in Virtuous syncs to WeGive, and not everything in WeGive syncs back to Virtuous.

Tags Tags are not synced between WeGive and Virtuous. Both systems require tags to be managed independently.

Event Registrations Event registration data does not sync between WeGive and Virtuous. If you need event registration history in WeGive, historical records can be imported manually via CSV.

Communication Lists Communication lists from WeGive do not sync to Virtuous. Audience segmentation and communication preferences managed in WeGive stay in WeGive.

A Note on "Bi-Directional" Bi-directional sync applies only to the specific data types listed in the table above. It does not mean all data in both systems flows back and forth. If you have a workflow that depends on a specific data type syncing, confirm it's in the supported list before building around it.

Why Some Features Are Limited: Virtuous API Constraints

Several of the limitations above are a direct result of constraints in the Virtuous API, not decisions made by WeGive. Specifically:

Virtuous enforces a hard cap of 1,500 API requests per hour. For organizations with large donor bases, this makes certain types of syncing - like tags or communication lists - impractical at scale. Attempting to sync large volumes of this data would consume the API limit and disrupt other integration functions for hours at a time.

Additionally, the Virtuous API does not support creating tags programmatically, which is why tag syncing is not possible regardless of volume.

We recommend the Batch Integration mode (described above) for any organization with significant donation volume, as it is specifically designed to work within these rate limit constraints.

What's Next

Ready to get started? Here's the recommended path:

1. Review the Prerequisites & Before You Begin article to make sure your accounts are ready

2. Follow the steps in Connecting WeGive to Virtuous to set up the integration

3. Import your historical data using the Migrating Your Historical Data guide

4. Familiarize yourself with Monitoring Your Integration to keep an eye on sync health