WeGive Documentation home page
Search...
⌘K
Salesforce NPSP
Overview
Introduction to Salesforce NPSP
Setup Requirements
Technical Implementation Guide
Data Models & Integration
Configuration Options
Important Integration Nuances
Data Mapping
Data Mapping Overview
Detailed Object Mappings
Account
Contact
Campaign
Campaign Member
Opportunity & Payment
Lead
Task
Recurring Donation
GAU & Allocation
Soft Credits
Pledge
Payout
Communication Lists & Preferences
Events, Tickets & Registrations
Fundraiser
Support
Dashboard
WeGive Documentation home page
Search...
⌘K
Ask AI
Support
Dashboard
Dashboard
Search...
Navigation
Data Mapping
Lead
Data Mapping
Lead
Documentation regarding WeGive and Salesforce Lead object integration
Lead
Key Concepts
Default Integration Behavior
No Default Integration
: WeGive does not sync Marketing Contacts to Leads in Salesforce by default
Contact-Focused
: All related objects (including Campaign Members) are linked to Contact IDs
Configurable
: While not default, integration with Leads is theoretically possible through:
Salesforce field mapping integration UI
WeGive managed package configuration
Integration Philosophy
Strategic Decision
WeGive has made a deliberate choice not to integrate with Leads by default for several key reasons:
CRM Optimization
Prevents unnecessary data accumulation in Salesforce
Maintains Salesforce as a relationship-focused CRM
Avoids bloating contact records with marketing data
Cost Management
Reduces Salesforce data storage costs
Prevents dramatic increases in data costs
Optimizes Salesforce performance
Data Architecture
Aligns with Salesforce’s design as a CRM (not CDP)
Maintains focus on manually created, relationship-based data
Preserves Leads for marketing tool integration
Alternative Approach
Instead of full Lead integration, WeGive recommends:
Lightning Web Component
Provides access to marketing contact data
Avoids Salesforce data storage costs
Prevents contact record bloat
Maintains clean data architecture
Contact-First Strategy
Focuses on relationship-based communications
Maintains data quality in Salesforce
Aligns with CRM best practices
Important Notes
Current Limitations
No default Lead synchronization
Campaign Members only sync with Contact IDs
Marketing contact data not stored in Salesforce
Future Possibilities
Integration possible through custom configuration
Requires explicit setup in WeGive settings
May be implemented through managed package
Best Practices
Data Architecture
Keep marketing data separate from CRM data
Use appropriate tools for different data types
Maintain clean Salesforce instance
Cost Management
Monitor Salesforce data storage
Avoid unnecessary data accumulation
Consider alternative solutions for marketing data
Integration Planning
Understand current limitations
Plan for future integration if needed
Consider Lightning Web Component approach
Common Scenarios
Marketing Contact Handling
Marketing contacts managed in WeGive
Data accessible via Lightning Web Component
No direct sync to Salesforce Leads
Maintains clean Salesforce architecture
Campaign Member Management
Campaign Members linked to Contacts only
No Lead-based Campaign Members
Maintains relationship-focused approach
Preserves data quality
Future Integration Planning
Assess integration needs
Consider cost implications
Evaluate alternative solutions
Plan for potential custom configuration
Previous
Task
Documentation regarding WeGive and Salesforce Task object integration
Next
On this page
Lead
Key Concepts
Default Integration Behavior
Integration Philosophy
Strategic Decision
Alternative Approach
Important Notes
Current Limitations
Future Possibilities
Best Practices
Common Scenarios
Marketing Contact Handling
Campaign Member Management
Future Integration Planning
Assistant
Responses are generated using AI and may contain mistakes.