Data Mapping
Events, Tickets & Registrations
Detailed mapping documentation for WeGive Events, Tickets, and Registrations to Salesforce custom objects
Events, Tickets & Registrations
The Event mapping between WeGive and Salesforce is a crucial component of the integration, enabling seamless synchronization of event data between the two platforms. This mapping ensures that event details, registrations, and ticket information are properly tracked and managed across both systems. Tickets represent the different pricing tiers and capacity limits for an event, while registrations track individual attendee information, including their ticket selections and payment status. Together, these three components form a complete event management system that handles everything from event creation to attendee tracking.Key Concepts
The integration between WeGive Campaign Events and Salesforce Campaign Events is designed to provide a comprehensive event management solution. Understanding these key concepts is essential for effective implementation and usage.Object Mapping
- WeGive Campaign Events map to Salesforce Campaign Events
- Requires WeGive Managed Package installation
- Bi-directional sync capabilities
- Custom object integration
Managed Package Details
- Custom object name:
wegive__Event__c - Package source: WeGive Managed Package
- Installation required for functionality
- Custom fields included
Sync Behavior
- Bi-directional synchronization
- Real-time updates
- Event creation and modification
- Registration tracking
- Ticket management
Dependencies
- Campaign synchronization
- Contact/Account sync
- Registration management
- Ticket type configuration
Field Mappings
The field mappings between WeGive and Salesforce events are designed to ensure comprehensive data synchronization. These mappings cover all essential event information, from basic details to advanced configuration options.Standard Field Mappings
| Salesforce Field | WeGive Field | Direction | Create Only | Default Mapping | Notes |
|---|---|---|---|---|---|
name | name | Both | No | Yes | Event name |
description | description | Both | No | Yes | Event description |
start_date | start_date | Both | No | Yes | Event start date |
end_date | end_date | Both | No | Yes | Event end date |
location | location | Both | No | Yes | Event location |
status | status | Both | No | Yes | Event status |
type | type | Both | No | Yes | Event type |
capacity | capacity | Both | No | Yes | Maximum attendees |
registration_deadline | registration_deadline | Both | No | Yes | Registration cutoff |
is_public | is_public | Both | No | Yes | Public visibility |
campaign_id | campaign_id | Both | No | Yes | Associated campaign |
Registration Field Mappings
| Salesforce Field | WeGive Field | Direction | Create Only | Default Mapping | Notes |
|---|---|---|---|---|---|
contact_id | contact_id | Both | No | Yes | Registrant contact |
event_id | event_id | Both | No | Yes | Associated event |
registration_date | registration_date | Both | No | Yes | Registration timestamp |
status | status | Both | No | Yes | Registration status |
ticket_type | ticket_type | Both | No | Yes | Selected ticket |
quantity | quantity | Both | No | Yes | Number of tickets |
total_amount | total_amount | Both | No | Yes | Registration cost |
Ticket Field Mappings
| Salesforce Field | WeGive Field | Direction | Create Only | Default Mapping | Notes |
|---|---|---|---|---|---|
name | name | Both | No | Yes | Ticket name |
description | description | Both | No | Yes | Ticket description |
price | price | Both | No | Yes | Ticket price |
quantity_available | quantity_available | Both | No | Yes | Available tickets |
sale_start_date | sale_start_date | Both | No | Yes | Sales start date |
sale_end_date | sale_end_date | Both | No | Yes | Sales end date |
is_active | is_active | Both | No | Yes | Ticket availability |
Important Notes
Understanding these important aspects of the Event integration is crucial for successful implementation and ongoing management.Package Requirements
- WeGive Managed Package must be installed
- Custom objects must be deployed
- Field-level security must be configured
- User permissions must be set
Sync Behavior
- Real-time synchronization
- Bi-directional updates
- Registration tracking
- Ticket management
- Capacity monitoring
Field Considerations
- Required fields must be mapped
- Custom fields can be added
- Field types must match
- Validation rules apply
- Default values supported
Best Practices
Following these best practices will help ensure a smooth and successful event integration:Data Management
- Regular data validation
- Monitor sync status
- Check for duplicates
- Verify field mappings
- Review error logs
Integration Configuration
- Test in sandbox first
- Verify permissions
- Check field security
- Monitor performance
- Regular maintenance
Troubleshooting
- Check sync logs
- Verify connections
- Review error messages
- Test field mappings
- Contact support if needed
Common Scenarios
Understanding these common scenarios will help you effectively manage events across both platforms:New Event Creation
- Create event in WeGive
- Sync to Salesforce
- Configure tickets
- Set up registration
- Monitor sync status
Registration Management
- Process registration
- Update capacity
- Track attendance
- Manage waitlist
- Handle cancellations
Event Updates
- Modify event details
- Update capacity
- Change location
- Adjust dates
- Sync changes