> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wegive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Lead

> Documentation regarding WeGive and Salesforce Lead object integration

# Lead

## Key Concepts

### Default Integration Behavior

* **No Integration**: WeGive does not sync Marketing Contacts, or any other data, to the Salesforce Lead object. The integration contains no read or write path for Leads.
* **Contact-Focused**: All related objects (including Campaign Members) are linked to Contact or Account records. Marketing contacts in WeGive are excluded from the Contact push.
* **Not Configurable**: Lead sync cannot be enabled through the field mapping UI or the managed package. Supporting Leads would require changes to the integration itself.

## Integration Philosophy

### Strategic Decision

WeGive has made a deliberate choice not to integrate with Leads 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 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

## Related Documentation

* [Contact](./contact)
* [Campaign Member](./campaign-member)

*Verified against the integration source, September 2026.*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.