
CCB
Church Community Builder is one of the leading ChMS platforms, and owned by PushPay.
π How the WeGive <-> Church Community Builder (CCB) Integration Works
Overview
The WeGive + Church Community Builder (CCB) integration keeps your donor, fund, and giving data in sync across both platforms. It's a bi-directional integration, meaning data flows both ways β giving you full visibility and control without double entry.
This article explains how the integration works, what data is synchronized, and how WeGive ensures your systems stay aligned.
π What Is Synced?
The integration covers three core types of data: Donors, Funds, and Transactions. Below is what's synced and which fields are included.
π€ Donors
Direction: Bi-directional
Fields Synced:
- First Name
- Last Name
- Email Address
- Phone Number
- Address (Street, City, State, ZIP)
- CCB Person ID (for linkage)
Donors are matched by email and/or CCB ID. New donors created in either WeGive or CCB are automatically added to the other.
π° Funds
Direction: Bi-directional
Fields Synced:
- Fund Name
- Fund Code (if applicable)
- Fund Description
- Active/Archived Status
- CCB Fund ID (for linkage)
WeGive keeps fund lists aligned with CCB so contributions are always tied to the correct fund in both systems.
π³ Transactions
Direction: Bi-directional
Fields Synced:
- Amount
- Fund (linked by ID)
- Donor (linked by ID)
- Transaction Date
- Payment Method (credit card, ACH, etc.)
- External Transaction ID (e.g., Stripe ID, CCB Batch ID)
- Notes or Memo
- Tax-Deductible Flag
- Recurring Status (one-time or recurring)
Transactions are synced only after their associated donor and fund records exist in both systems. External IDs help prevent duplicate syncing.
π§ How Syncing Works
1. Pulling from CCB β WeGive
WeGive routinely connects to CCB to retrieve:
- New or updated donor records
- Fund records
- Contributions entered directly in CCB
This ensures your WeGive reporting and donor profiles are always up to date.
2. Pushing from WeGive β CCB
When a donation is made through WeGive, it is automatically pushed to CCB:
- Donor and fund records are created in CCB if missing
- Transactions are logged with full detail
- CCB IDs are saved in WeGive for future syncing
When a fund is created in WeGive, it is automatically pushed to CCB:
- CCB IDs are saved in WeGive for future syncing
When a donor is created in WeGive, it is automatically pushed to CCB:
- CCB IDs are saved in WeGive for future syncing
π Security & Access
- CCB credentials are stored securely and encrypted
- All data transfers use encrypted HTTPS connections
- Sync activity is logged and auditable
Only organization administrators have access to view or manage integration settings.
π Sync Frequency
- Push syncs: Occur immediately when new data is entered in WeGive
- Pull syncs: Run automatically on a regular schedule (every 15 minutes)
- Manual syncs: Can be triggered from your admin dashboard
βοΈ Configuration & Customization
Each organization can:
- Enable/disable the CCB integration
- Securely update their API credentials
- Manually trigger a sync
β Summary of Features
Feature Status
β
Bi-directional sync
β Enabled
Donor, fund & transaction sync
β Supported
Auto & manual syncs
β Supported
Sync logging & tracking
β Available
Duplicate protection
β Built-in
Per-organization settings
β Configurable
βNeed Help?
For setup assistance, troubleshooting, or customization requests, please contact WeGive Support or reach out via live chat in your admin dashboard.
β