Skip to main content

Campaign Data Mapping

This document details the field-level mappings between WeGive campaign records and Blackbaud Raiser’s Edge NXT campaign records.

Object Overview

WeGive Campaign Object

  • Purpose: Represents fundraising campaigns and appeals in the WeGive platform
  • API Endpoint: /campaigns/{campaign}
  • Unique Identifier: WeGive campaign ID
  • Marketing: Controls donation attribution and campaign tracking

Blackbaud Campaign Object

  • Purpose: Represents fundraising campaigns and appeals in Raiser’s Edge NXT
  • API Endpoint: fundraising/v1/campaigns/{campaign_id}
  • Unique Identifier: Blackbaud campaign ID
  • Fundraising Management: Controls campaign goals, appeals, and attribution

Core Campaign Mapping

Basic Campaign Information

Campaign Lifecycle

Financial Information

Campaign Type Mapping

Standard Campaign Types

Campaign Status Values

Appeal Integration

Appeal Hierarchy

Appeal Information

Marketing and Attribution

Source Tracking

Channel Attribution

Segmentation and Targeting

Donor Segmentation

Communication Preferences

Performance Tracking

Campaign Metrics

Conversion Tracking

Budget and Financial Planning

Campaign Budget

Cost Categories

Custom Fields and Attributes

Extended Campaign Information

Stewardship and Recognition

Data Transformation Rules

Name and Description Handling

Campaign Names
  • Preserve original formatting and capitalization
  • Maximum length: 255 characters
  • Special characters allowed and preserved
  • Duplicate name detection within same year
Campaign Descriptions
  • HTML markup removed for compatibility
  • Maximum length: 4000 characters
  • Line breaks preserved where possible
  • Rich text formatting converted to plain text

Date and Time Processing

Campaign Timeline
  • Start dates can be in the future for planned campaigns
  • End dates must be after start dates
  • Timezone conversion for international campaigns
  • Automatic status updates based on dates
Duration Calculations
  • Campaign length calculated automatically
  • Progress tracking updated daily
  • Milestone date tracking
  • Extension handling for ongoing campaigns

Financial Data Processing

Goal and Target Amounts
  • Goals rounded to nearest dollar
  • Percentage completion calculated automatically
  • Progress tracking updated with each gift
  • Historical goal changes maintained
Budget Calculations
  • Cost-per-dollar-raised calculated automatically
  • ROI calculations updated in real-time
  • Variance analysis between budget and actual
  • Efficiency metrics tracked over time

Sync Behavior

Create Operations

New WeGive Campaign → Blackbaud Campaign
  1. Validate campaign data and requirements
  2. Check for duplicate campaign names or codes
  3. Create campaign record in Blackbaud
  4. Set initial status and configuration
  5. Store correlation ID for future updates
  6. Create default appeal if specified
New Blackbaud Campaign → WeGive Campaign
  1. Extract campaign information and attributes
  2. Map to WeGive campaign format
  3. Preserve campaign classification and status
  4. Create WeGive campaign record
  5. Store correlation ID and external references

Update Operations

Bidirectional Updates
  • Campaign name and description changes
  • Status updates (active/inactive/completed)
  • Goal and target modifications
  • Date range adjustments
  • Budget and expense updates
  • Performance metric updates
Restricted Updates
  • Campaign codes typically immutable after creation
  • Start dates may be restricted once campaign begins
  • Historical data preservation for completed campaigns
  • Approval required for major goal changes

Completion and Archive Operations

Campaign Completion Process
  • Status change to “Completed”
  • Final performance metrics calculation
  • Success/failure assessment against goals
  • Archive campaign data for historical reporting
  • Transfer learnings to campaign template library

API Examples

Create Campaign Record

WeGive to Blackbaud Campaign Creation

Update Campaign Progress

Blackbaud to WeGive Campaign Progress Sync

Campaign with Appeals and Segmentation

Complex Campaign with Multiple Appeals

Error Handling and Validation

Required Field Validation

Critical Fields
  • Campaign name/description must not be empty
  • Campaign code must be unique within organization
  • Status must be valid enumerated value
  • Goal amount must be positive if specified
  • Date ranges must be logical (start before end)
Data Quality Checks
  • Name length validation (max 255 characters)
  • Code format validation (alphanumeric plus hyphens)
  • Amount precision validation (2 decimal places)
  • Date format validation (ISO 8601)
  • Appeal consistency within campaign

Common Error Scenarios

Duplicate Campaign Names
  • Error: Campaign name already exists for same period
  • Resolution: Append year or modify name
  • Action: Queue for administrative review
Invalid Campaign Codes
  • Error: Campaign code format invalid or duplicate
  • Resolution: Generate alternative code or modify
  • Action: Log warning and use system-generated code
Date Range Validation
  • Error: End date before start date
  • Resolution: Adjust dates or use open-ended range
  • Action: Log error and notify administrators

Retry and Recovery Logic

Temporary Failures
  • Network timeouts: Retry with exponential backoff
  • Rate limiting: Respect retry-after headers
  • Server errors: Retry up to 3 times with delays
Permanent Failures
  • Validation errors: Log and skip record
  • Authorization errors: Alert system administrators
  • Data conflicts: Queue for manual resolution

Performance Optimization

Batch Processing

Campaign Creation Batches
  • Process up to 25 campaigns per API call
  • Include appeals in campaign creation
  • Validate all campaign data before batch submission
  • Handle partial batch failures gracefully
Update Optimization
  • Delta sync for changed records only
  • Timestamp-based change detection
  • Bulk update operations where supported
  • Performance metric updates in batches

Caching Strategies

Reference Data Caching
  • Campaign information cached for 15 minutes
  • Appeal data cached for 10 minutes
  • Status and type lookups cached for 1 hour
  • Performance metrics cached for 5 minutes
Performance Monitoring
  • Average campaign sync time tracking
  • API response time monitoring
  • Error rate alerting by campaign type
  • Cache effectiveness measurement

Reporting and Analytics

Campaign Performance Analytics

Success Metrics
  • Goal achievement rates by campaign type
  • Average time to reach funding goals
  • Donor acquisition and retention rates
  • Cost-per-dollar-raised analysis
  • ROI calculations and comparisons
Trend Analysis
  • Campaign performance over time
  • Seasonal giving patterns
  • Appeal effectiveness comparison
  • Channel performance analysis
  • Segmentation effectiveness

Comparative Reporting

Cross-Campaign Analysis
  • Performance benchmarking
  • Best practice identification
  • Resource allocation optimization
  • Strategic planning insights
  • Future campaign planning

Best Practices

Campaign Planning

  1. Clear Goals: Set specific, measurable, achievable goals
  2. Realistic Timelines: Allow adequate time for campaign execution
  3. Defined Appeals: Create distinct appeals with clear messaging
  4. Target Segmentation: Use appropriate donor segmentation
  5. Performance Tracking: Monitor progress regularly

Data Management

  1. Consistent Naming: Use standardized campaign naming conventions
  2. Code Standards: Implement consistent code formats
  3. Regular Updates: Keep campaign data current and accurate
  4. Historical Preservation: Maintain historical campaign data
  5. Quality Assurance: Regular data quality audits

Integration Management

  1. Sync Frequency: Appropriate sync timing for campaign needs
  2. Error Monitoring: Proactive error detection and resolution
  3. Performance Tracking: Monitor sync performance and optimization
  4. Backup Procedures: Regular campaign data backups
  5. Testing Protocols: Thorough testing before campaign launch

Troubleshooting Guide

Common Sync Issues

Campaign Creation Failures
  • Verify campaign name uniqueness
  • Check campaign code format and availability
  • Validate goal amounts and date ranges
  • Confirm user permissions for campaign creation
Appeal Sync Problems
  • Review appeal hierarchy relationships
  • Check appeal goal consistency with campaign
  • Validate appeal codes and descriptions
  • Verify appeal type mappings
Performance Data Discrepancies
  • Compare calculation methods between systems
  • Check date range filters for performance metrics
  • Verify gift allocation to correct campaigns
  • Review segmentation and targeting criteria

Data Quality Issues

Missing Campaign Information
  • Check field mapping completeness
  • Verify data availability in source system
  • Review sync scope and filtering rules
  • Validate required field population
Inconsistent Classifications
  • Review campaign type and category mappings
  • Check for custom field configuration differences
  • Validate enumerated value consistency
  • Confirm appeal relationship accuracy

Performance Problems

Slow Campaign Processing
  • Optimize batch sizes for campaign volume
  • Review API response times and bottlenecks
  • Check network connectivity and latency
  • Monitor system resource utilization
High Error Rates
  • Analyze error patterns and common causes
  • Review data validation rule effectiveness
  • Check system capacity and rate limits
  • Validate integration configuration settings

Support Resources

Documentation References

Support Contacts