Configuration Options
The WeGive Bloomerang integration provides flexible configuration options to control data synchronization behavior, sync frequency, and integration features.Authentication Settings
API Configuration
API Key Configuration
- Source: Generated from Bloomerang Settings → API Access
- Security: Encrypted and stored securely in WeGive
- Validation: Automatically tested during configuration
- Rotation: Should be rotated periodically for security
Synchronization Controls
Data Type Configuration
Configure what types of data synchronize between platforms:Donors/Constituents Sync
Push Donors Configuration:
- Creates new constituents in Bloomerang from WeGive donors
- Updates existing constituents when correlation ID exists
- Handles both individual and organization donor types
- Syncs contact information including addresses, phones, and emails
- Imports constituents from Bloomerang to WeGive
- Respects existing donor records to prevent duplicates
- Maps constituent types to appropriate WeGive donor categories
- Includes full contact and address information
Transactions/Donations Sync
Push Transactions Configuration:
- Sends successful WeGive donations to Bloomerang
- Maps payment methods (credit card, bank transfer, etc.)
- Links transactions to appropriate constituents and funds
- Includes transaction metadata and processing details
- Imports Bloomerang transactions to WeGive
- Includes donations, pledge payments, and recurring donations
- Maps to existing donors or creates new donor records
- Preserves transaction types and designations
Funds Sync
Push Funds Configuration:
- Creates corresponding funds in Bloomerang for WeGive funds
- Maintains fund naming and organizational structure
- Enables proper transaction designation mapping
- Imports Bloomerang fund structure to WeGive
- Preserves fund categories and hierarchies
- Updates existing funds when correlation exists
Advanced Settings
Default Fund Configuration
Important Notes:
- Must be a valid, active fund ID from your Bloomerang account
- Used when WeGive transactions don’t have specific fund designations
- Prevents transaction sync failures due to missing fund mappings
- Should be your organization’s general operating fund
Sync Timing Configuration
Real-time Sync:
- Immediate synchronization for critical updates
- Triggered by donor actions, donations, and fund changes
- Best for organizations requiring immediate data consistency
- Batch processing at specified intervals
- More efficient for large data volumes
- Reduces API usage and rate limit concerns
Data Flow Configuration
Sync Direction Matrix
Conflict Resolution
When the same record exists in both systems: For Push Operations (WeGive → Bloomerang):- WeGive data takes precedence
- Bloomerang records are updated with WeGive values
- Correlation IDs prevent duplicate creation
- Bloomerang data takes precedence
- WeGive records are updated with Bloomerang values
- Existing relationships are preserved
Integration Features
Test Mode
Error Handling
Logging Configuration
Organization-Specific Settings
Custom Field Mapping
Organizations can configure custom field mappings between WeGive and Bloomerang:- Field Pairing: Map specific WeGive fields to corresponding Bloomerang fields
- Data Type Matching: Ensure compatible data types between systems
- Validation Rules: Custom fields follow the same validation as standard fields
- Configuration Support: Contact WeGive support for complex custom field requirements
Data Filters
API Configuration
Rate Limiting
Batch Processing
Monitoring Configuration
Health Checks
Performance Monitoring
Recommended Configuration Approaches
Standard Configuration (Recommended for Most Organizations)
Purpose: Send WeGive data to Bloomerang while maintaining Bloomerang as the authoritative source Settings:- Push donors, transactions, and funds from WeGive to Bloomerang
- Do not pull data from Bloomerang to WeGive
- Use real-time sync frequency for immediate updates
- Configure a default fund for transactions without specific designations
Bidirectional Configuration (Advanced Users)
Purpose: Keep both systems completely synchronized Settings:- Enable both push and pull for all data types
- Use hourly sync frequency to prevent conflicts
- Requires careful monitoring and data quality management
- Configure appropriate conflict resolution rules
Import-Only Configuration
Purpose: Use WeGive primarily as a donation portal while maintaining records in Bloomerang Settings:- Pull donors, transactions, and funds from Bloomerang to WeGive
- Do not push data from WeGive to Bloomerang
- Use daily sync frequency for batch imports
- Ideal for organizations migrating to WeGive
Configuration Best Practices
Initial Setup
- Start Conservative: Begin with push-only configuration
- Test Thoroughly: Use test connection before enabling sync
- Monitor Closely: Watch logs during first 24-48 hours
- Validate Data: Verify accuracy of synced records
Ongoing Management
- Regular Reviews: Check configuration monthly
- Performance Monitoring: Track sync times and success rates
- Error Analysis: Review and resolve integration errors promptly
- Settings Updates: Adjust configuration based on usage patterns
Security Considerations
- API Key Rotation: Update API keys quarterly
- Access Control: Limit who can modify integration settings
- Audit Logging: Maintain records of configuration changes
- Data Privacy: Ensure compliance with data protection regulations
Troubleshooting Configuration Issues
Common Problems
Issue: Sync operations failing- Check: Verify all required settings are configured
- Verify: Test API connection is successful
- Review: Ensure default fund ID is valid
- Check: Correlation ID mapping is working correctly
- Verify: Email matching is functioning properly
- Review: Sync direction settings are appropriate
- Check: Batch size settings are optimal
- Verify: Rate limiting is not being exceeded
- Review: Sync frequency matches data volume needs