Setting Up and Using Integration Logs

Integration Logs are your window into every sync between WeGive and your connected CRM (Salesforce, Bloomerang, Donor Perfect, Neon, Planning Center, Raiser's Edge, Virtuous, etc.). Anytime data moves in or out of WeGive, a log entry is created so you can confirm the sync ran, see what was affected, and troubleshoot anything that didn't go through.

This article walks through how to access Integration Logs, what each column and status means, and how to use the page to investigate sync issues.

Who Can Access Integration Logs

Integration Logs are available to users with Admin or Development roles. If you don't see Integration Logs in your dashboard, ask an Admin in your organization to update your permissions.

How to Find Integration Logs

In the WeGive dashboard, navigate to Data → Integration Logs.

You'll see a table of every sync operation, with the most recent at the top. The page also has a sibling view at Data → Integration Logs Ignored, which holds logs that have been intentionally excluded from the main view (more on that below).

What Gets Logged

WeGive logs two kinds of sync operations:

Pull operations move data from your CRM into WeGive on a schedule (every 15 minutes by default). These are typically used to bring donor records, campaigns, or other reference data over from your CRM.

Push operations move data from WeGive into your CRM in real time, as soon as the underlying record is created or changed. Most transactional activity (donations, donor updates, recurring plans) flows this direction.

A single log entry corresponds to one sync attempt for one record (or one batch, depending on the operation type).

Reading the Integration Logs Table

Each row in the Integration Logs table includes:

• ID — the log entry's unique identifier, useful when sharing with WeGive support

• Model — what type of record was being synced (Donor, Transaction, Campaign, Fund, Recurring Plan, Pledge, Soft Credit, etc.)

• Model ID — the specific record being synced; you can use this to look up the donor or transaction in WeGive

• Integration Type — which CRM the sync was for (Salesforce, Bloomerang, Donor Perfect, Neon, Planning Center, Raiser's Edge, Virtuous)

• Type — what action was performed (Pull, Pull-All, Push, Create, Update, Batch, Push-Missing)

• Status — the result of the sync (see status reference below)

• Details — a clickable link with the full payload, response, and any error messages

• Progress / Progress Updated — for long-running pulls, shows the current step and when it last updated

• Pull By — the user who initiated a manual pull (blank for scheduled pulls)

• Initiated — when the sync was started

• From / To — date range covered by the sync, when applicable

• File — for sync types that produce a downloadable log file, a Download Log button appears here

Status Reference

Filtering and Searching

The Integration Logs table supports the same filter patterns as other WeGive data tables. You can narrow the list by:

• Integration Type — limit to one CRM

• Model Type — show only Donors, Transactions, Campaigns, Funds, Recurring Plans, Pledges, Soft Credits, or any of the other 18+ supported model types

• Status — for example, filter to Error and Error Execution to see only failed syncs

• Date Range — Initiated date or Progress Updated date, with relative options like "last 7 days"

• Text search — search by Model ID, Pull By, or Details content

Filters stack, so you can pull up something like "all Salesforce Donor pushes that errored in the last 24 hours" in a few clicks. This is the fastest way to scope down when a customer reports a specific sync issue.

Downloading a Detailed Log File

For pull operations and certain other sync types, the File column shows a Download Log button when a file is available. Clicking it generates a signed download URL and pulls the full log file, which contains the complete request and response payloads, timestamps, and any errors. This is the most detail you can get on a sync without engineering involvement.

Troubleshooting With Integration Logs

When a customer reports something didn't sync, walk through these steps:

1. Find the record in WeGive. Get the Model ID (donor ID, transaction ID, etc.) so you can search for it in the logs.

2. Filter the logs. Set Integration Type to the relevant CRM, Model to the record type, and search by the Model ID.

3. Check the most recent entry's Status.

   • If it's Processed, the sync succeeded from WeGive's side. Any missing data in the CRM is likely a CRM-side display or mapping issue.

   • If it's Error or Error Execution, open Details (and download the log file if available) to see the exception. Common causes include missing required fields, duplicate records, and CRM API outages.

   • If it's Pending or Running, the sync hasn't completed yet. Pull operations run every 15 minutes, so a recent change may simply be queued.

   • If it's Partial, some records in the batch failed. Open Details to find the specific records and reasons.

4. Look for repeated failures. If the same record has failed three times in a row, WeGive stops retrying it and creates an entry in Integration Locks (see below). Resolving the underlying issue and clearing the lock lets the sync retry.

Integration Logs vs. Integration Locks

These are easy to confuse but serve different purposes:

Integration Logs record every sync attempt — successful or not — and are the primary place to look when investigating a single sync.

Integration Locks (at Data → Integration Locks) are a safeguard against infinite retry loops. After a record fails to sync three consecutive times, WeGive moves it to Integration Locks and stops retrying it. Once you've fixed the root cause (typically by updating the record in WeGive or the CRM), archive the lock and WeGive will resume syncing that record on the next cycle.

Integration Logs Ignored

The Integration Logs Ignored view (Data → Integration Logs Ignored) holds log entries that WeGive has filtered out of the main view. These are typically created when a record has been excluded from sync intentionally — for example, after a record hits the lock threshold and is marked to skip future retries until it's manually re-enabled. Most users don't need to interact with this view; it's primarily useful when investigating why a specific record is no longer attempting to sync.

When to Reach Out to Support

If you've reviewed the relevant log entry and the Details payload doesn't make the cause clear — or you're seeing widespread Error Execution statuses across an integration — share the log ID and Model ID with WeGive support so we can investigate further.