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

# Campaign Data Mapping

> Detailed field mapping for campaigns between WeGive and StudioEnterprise

# Campaign Data Mapping

This page covers how WeGive Campaigns map to StudioEnterprise Source Codes.

**StudioEnterprise Object**: Source Code
**Sync Direction**: Pull only (StudioEnterprise → WeGive) — push is not
yet supported for this object

## Core Identity Fields

| WeGive Field | StudioEnterprise Field | Notes |
| - | - | - |
| `donor_direct_id` | Source Code | Primary correlation key |

## How Campaign Attribution Works

StudioEnterprise organizes campaign attribution as a multi-level hierarchy
(Source Code rolling up through several parent levels to a top-level
Campaign). WeGive's integration reads this full hierarchy and flattens it
into a single Campaign record per Source Code, so a gift's Source Code
resolves directly to the correct WeGive campaign without requiring your
organization to separately map each hierarchy level.

Like Funds, Campaigns are reference data synced before gift and recurring
plan data, so those records can resolve to a real WeGive campaign on
import.

When a gift is pushed to StudioEnterprise without a specific campaign
attribution, it uses your organization's configured **default Source
Code** (set in [Configuration
Options](/external/onboarding/donordirect/configuration-options)) rather
than being rejected.

## Not Yet Supported

<AccordionGroup>
  <Accordion title="Year-specific historical hierarchy changes">
    StudioEnterprise supports a source-to-element mapping that can change from
    year to year. The current integration uses the hierarchy as currently
    configured — year-accurate historical lineage (which parent a Source Code
    rolled up to in a prior year, if that's since changed) is not yet
    reflected.
  </Accordion>

  <Accordion title="Push (WeGive → StudioEnterprise)">
    Campaigns are currently pull-only. Creating or updating Source Codes in
    StudioEnterprise from WeGive campaign data is not yet supported.
  </Accordion>
</AccordionGroup>

## Related Documentation

<CardGroup cols={2}>
  <Card title="Transaction Mapping" href="/external/onboarding/donordirect/data-mapping/transaction">
    See how gifts reference campaign attribution
  </Card>

  <Card title="Fund Mapping" href="/external/onboarding/donordirect/data-mapping/fund">
    See how fund designation works
  </Card>
</CardGroup>

For additional help with campaign mapping, contact our support team at
[support@wegive.com](mailto:support@wegive.com).


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