This guide explains how to monitor, manage, and troubleshoot integrations in WeGive, focusing on Salesforce but applicable to other CRMs. It covers integration logs, syncing processes, error handling, record locking, field mapping, and preparation steps to ensure smooth and accurate data flow between systems.
1. Accessing Integration Logs
Where to go:
-
Navigate in WeGive to Data > Integration Logs.
What you see:
-
A central table showing all integration activities between WeGive and external systems (like Salesforce).
-
Each row in this table represents a log entry related to a sync, update, or push event.
Log types:
-
Create / Update logs: Show individual data records that were created or updated (such as transactions, contacts, recurring plans).
-
Poll logs: Show WeGive pulling data from Salesforce, including date ranges and object types.
-
Push logs: Show WeGive pushing data into Salesforce, including inserted or updated records.
-
Push Missing logs: Show retry attempts when WeGive identified records that failed to sync previously.
Why it matters:
-
This table is the central hub for monitoring integration health, tracking what data has moved, identifying errors, and seeing what’s in progress.
2. Understanding Poll Logs
Poll log details include:
-
Date range (from/to): The time window WeGive is pulling data for (usually every 15 minutes by default).
-
Objects pulled: Which data types (such as contacts, transactions, pledges) were included.
-
Progress details: A JSON-style view showing:
-
Which object is being processed.
-
How many records are involved.
-
Current status.
-
How long it’s been running.
-
-
Progress updated at: Timestamp showing the last progress update, useful to check if a sync is still running or stalled.
-
Error count: Number of records that failed to sync, with details available.
When you use it:
-
When a sync seems slow or stuck.
-
When you’ve recently added or updated a large volume of records in Salesforce.
-
When you want a clear view of what data has been brought into WeGive.
3. Manual Syncs
Where to go:
-
Navigate to Integrations > Sync from Salesforce.
Options you have:
-
Sync all data: Pulls everything from the start of time.
-
Sync by data object: Focuses on one type, like just contacts or transactions.
-
Sync since last sync: Picks up only the most recent updates if you need to re-run something.
When to use:
-
After adding a new custom field or object in Salesforce.
-
After a Salesforce maintenance window or downtime.
-
To “force” a fresh sync if you suspect recent data hasn’t come through.
What to expect:
-
These actions will show up in the Integration Logs as
pullorpull allactions.
4. Integration Locks
What they are:
-
If a record fails to sync three times, WeGive adds it to the Integration Locks table.
-
This prevents repeated attempts that would otherwise hammer the Salesforce API and create unnecessary load.
Where to view:
-
Navigate to Data > Integration Locks.
What to do:
-
Review the error reason provided.
-
Resolve the issue in Salesforce or WeGive (often related to validation rules, required fields, or temporary Salesforce record locks).
-
Select the locked record(s) and Delete Lock.
-
WeGive will automatically retry syncing.
Why this matters:
-
This helps you avoid sync loops and focus only on problem records that truly need fixing.
5. Reviewing Push Details
In Integration Logs:
-
You can drill into any push event to see:
-
The exact request payload WeGive sent to Salesforce.
-
Whether it was an insert (new record) or update (existing record).
-
Which fields and values were included.
-
Example:
-
A donation push might:
-
Update an existing contact and campaign.
-
Insert a new opportunity and payment.
-
Assign Salesforce IDs back to WeGive to keep everything linked.
-
Why it’s useful:
-
When a donor or admin asks, “Why isn’t this showing in Salesforce?”
-
To confirm that the right data (amounts, designations, campaign links) was sent.
6. Using Audit Logs
Where to find:
-
On each supporter, transaction, or relevant model page in WeGive, you will see Audit Logs and Integration Logs tabs.
What they show:
-
Audit Logs: Track all changes over time, who made them, and when.
-
Integration Logs: Show sync and push activity related to that specific record.
Use cases:
-
Investigating why a record changed.
-
Confirming whether a system workflow or human action caused an update.
-
Linking system activity to sync events.
7. Sync Best Practices
General recommendations:
-
For recurring donations and pledges, manage updates in WeGive if WeGive is responsible for billing.
-
For offline gifts (checks, cash), you can enter these in WeGive (to keep everything aligned for reporting and donor portal) or just record them in Salesforce.
-
Decide internally who manages what to avoid conflicts.
Why this matters:
-
Ensures your team is aligned on where to make updates.
-
Prevents accidental overwrites or duplicate data.
8. Mapping Custom Fields
Key points:
-
WeGive designations can sync to Salesforce GAUs (General Accounting Units) or custom objects.
-
If your Salesforce instance uses custom objects or categories (such as for campaigns, events, or gift types), you will need to plan mappings.
Next steps:
-
Schedule a data mapping meeting between your Salesforce team, WeGive, and stakeholders after the Salesforce import.
-
Review which fields are standard, which are custom, and define what syncs one-way or two-way.
9. Events and Campaign Syncing
Scenarios:
-
If using Salesforce campaigns to represent events, WeGive syncs them natively.
-
If using a custom event object, you will need a separate discussion and possibly custom integration work.
-
WeGive forms (including checkouts and event registrations) can sync submissions into Salesforce if the WeGive Managed Package is installed.
10. Next Steps for Setup
To prepare for integration success:
-
Install the WeGive Managed Package in Salesforce to extend sync capabilities.