Skip to main content

Setting Up Campaign, Appeal, and Package Codes on Your Gifts Before Syncing to RE NXT

Learn where to configure campaign, appeal, and package codes on gifts syncing from Almabase to RE NXT, how the override hierarchy works, and what other gift attributes you can set.

Written by Sarita Markande

When gifts sync from Almabase to Raiser's Edge NXT, each gift can carry campaign, appeal, and package codes — tags that tell your advancement office how to categorize the gift in RE NXT. Getting these right means your team doesn't have to manually tag every gift after it lands in RE NXT, and your reporting stays accurate from the start.

Where You Can Set Campaign, Appeal, and Package Codes

There are two places where these codes can be configured, each serving a different purpose:

1. At the Giving Page Level

This is the most common approach. When a giving page is tied to a specific campaign or appeal, set the codes directly on the page so every gift made through it is automatically tagged.

To set page-level codes:

  1. Open the giving page in the Almabase admin

  2. Go to Campaign Settings → Other Settings

  3. Under Set Gift Sync Metadata, select the appropriate campaign, appeal, and/or package from the dropdowns

These dropdown values are pulled directly from your RE NXT instance — you cannot create new campaigns, appeals, or packages from within Almabase. If you need a new code to appear, create it in RE NXT first; it will show up in the Almabase dropdowns the next time the list refreshes.

Any gift made through this page will carry these codes when it syncs to RE NXT — unless overridden at a higher level (see the override hierarchy below).

2. At Sync Time

When you create a gift sync batch, you can set campaign, appeal, and package values that apply to all gifts in the batch that don't already have page-level codes assigned. This is useful when you're syncing gifts from multiple pages that should all share the same campaign code, or when a page wasn't configured with codes ahead of time.

Think of sync-time codes as the safety net — they fill in the blanks for any gift that doesn't already have codes from its giving page.

The Override Hierarchy

When the same gift has codes configured in more than one place, Almabase uses a clear priority order. The most specific setting wins:

  1. Individual gift edits (highest priority) — If you manually edit a gift's campaign, appeal, or package before syncing, that value is used regardless of anything else.

  2. Page-level codes — Codes set on the giving page override sync-time values.

  3. Sync-time codes (lowest priority) — These apply only when no higher-level value exists.

Example: You set campaign to "Annual Fund 2026" at sync time. One of your giving pages has campaign set to "Giving Day 2026" in its page settings. A donor gives through that page. The gift syncs with campaign = "Giving Day 2026" because the page-level setting outranks the sync-time value.

Tip: Most teams set sync-time codes as a catch-all, then configure page-level codes for pages tied to specific campaigns. Individual gift edits are used only when you need more precision for a particular gift.

Other Gift Attributes You Can Set

Beyond campaign, appeal, and package, you can also configure additional fields that apply to synced gifts. These are set at sync time and include:

  • Gift Type — e.g., Donation, Gift-in-Kind, Pledge (default: Donation)

  • Gift Subtype — A further classification within the gift type

  • Post Status — Whether the gift should post to the general ledger (default: Do Not Post)

  • Post Date — The date for GL posting

  • Receipt Status and Acknowledgement settings

  • RE NXT Custom Fields — Any custom gift fields your organization has defined in RE NXT

These ensure gifts arrive in RE NXT with consistent categorization, reducing the amount of manual cleanup your team needs to do after a sync.

FAQs

Q: I don't see a campaign/appeal/package I need in the dropdown. What do I do?

Create the code in RE NXT first. Almabase pulls these values directly from your RE NXT instance. Once it's created there, it will appear in the Almabase dropdowns the next time the list refreshes.

Q: Do I have to set campaign, appeal, and package codes on every gift?

No — these are not mandatory fields. Gifts will still sync to RE NXT without them. Only set these up if your organization requires these values to be assigned to gifts before they reach RE NXT.

Q: Can I set different codes for different gifts on the same giving page?

Not directly on the page — page-level codes apply to all gifts from that page. However, you can edit individual gifts before syncing to assign different codes.

Q: How do I sync donor-covered transaction charges to a separate fund in RE NXT?

When donors choose to cover transaction fees, you can configure where those charges land in RE NXT separately from the donation itself.

Go to the giving page's Campaign Settings → Other Settings → Gift Sync Metadata and configure the fund for transaction charges.

When a gift with donor-covered charges syncs, a split is created automatically: the donation amount goes to the fund the donor selected, and the transaction charges go to the fund you specified in the metadata settings.

Did this answer your question?