Campaign Data Mapping
This page details the field-level mapping between WeGive campaign and campaign-fundraiser records and Blackbaud Raiser’s Edge NXT campaigns and appeals.Campaign Field Mapping (Raiser’s Edge → WeGive)
WeGive’s
campaigns table doesn’t have a category, status, or lookup-code column, so those don’t sync at the campaign level.
Appeals Map to Campaign Fundraisers, Not a Nested Campaign Sub-Object
Blackbaud “Appeals” are a separate pull toggle from campaigns, and map to WeGive’scampaign_fundraisers table — they’re their own object, not embedded inside the campaign record:
Appeals also connect to gifts: a gift split’s
appeal_id links to a campaign fundraiser’s Raiser’s Edge ID — see Gift Mapping for how outbound gifts set this.
What Isn’t Mapped
No code path exists for: campaign type/category at the campaign level (only appeals get a category-derived description), campaign or appeal status beyond the appeal’s active/inactive flag, budget or expense tracking, performance metrics (donor counts, response rates, conversion rates), donor segmentation/targeting rules, or custom fields.Sync Behavior
Pulled on the same fixed 15-minute cron as everything else in this integration. Appeal sync has its own on/off toggle (Pull Appeals) separate from campaign sync.
Getting Help
- WeGive Support: [email protected]
- Blackbaud Sky API Campaign/Appeal Docs: Sky API Documentation