​

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:

1. CRM Optimization

   • Prevents unnecessary data accumulation in Salesforce
   • Maintains Salesforce as a relationship-focused CRM
   • Avoids bloating contact records with marketing data

2. Cost Management

   • Reduces Salesforce data storage costs
   • Prevents dramatic increases in data costs
   • Optimizes Salesforce performance

3. 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:

1. Lightning Web Component

   • Provides access to marketing contact data
   • Avoids Salesforce data storage costs
   • Prevents contact record bloat
   • Maintains clean data architecture

2. 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

1. Data Architecture

   • Keep marketing data separate from CRM data
   • Use appropriate tools for different data types
   • Maintain clean Salesforce instance

2. Cost Management

   • Monitor Salesforce data storage
   • Avoid unnecessary data accumulation
   • Consider alternative solutions for marketing data

3. Integration Planning

   • Understand current limitations
   • Plan for future integration if needed
   • Consider Lightning Web Component approach

​

Common Scenarios

​

Marketing Contact Handling

1. Marketing contacts managed in WeGive
2. Data accessible via Lightning Web Component
3. No direct sync to Salesforce Leads
4. Maintains clean Salesforce architecture

​

Campaign Member Management

1. Campaign Members linked to Contacts only
2. No Lead-based Campaign Members
3. Maintains relationship-focused approach
4. Preserves data quality

​

Future Integration Planning

1. Assess integration needs
2. Consider cost implications
3. Evaluate alternative solutions
4. Plan for potential custom configuration