Enhanced NXT constituent enrichment

For GiveCampus integrations and API.

Enhanced import can update additional biography including birth date, map constituent codes into affiliation data, and import class years through the enhanced education-query process with its configured year cutoff. It also imports selected custom fields. Do not assume sports/Greek-life/campus activities automatically become native activity records: confirm the NXT storage field and selected mapping, or use a mapped constituent file for unsupported data. Preserve stable constituent identity and test representative records before a broad enrichment.

Can I map NXT Nickname or Preferred Name into GiveCampus First Name?

The standard NXT constituent integration uses a fixed mapping: NXT First Name populates GiveCampus First Name. That mapping cannot be changed to use a nickname instead. With Enhanced Constituent Import enabled, NXT Preferred Name separately populates GiveCampus Preferred First Name.

A previous CSV import may have placed a nickname into both fields. Switching to the direct NXT import can therefore change what a First Name merge field displays. In your GC Outreach email, use the Preferred First Name merge field when that is the name you intend to use. The preferred-name merge field can fall back to First Name if no preferred name is available; it does not guarantee a nickname for every recipient.

The name in the email body and the greeting on a personalized giving form are configured separately. To review the form greeting, open GC Outreach → Segments → select the custom segment → Personalization → select the personalization → Edit Personalization and check the greeting-name selection and any recipient overrides. A correct greeting on the form does not prove the email used the preferred-name merge field. Send a test with a constituent's details populated and check both the email and its personalized link before sending broadly.

Why is a phone number visible in NXT but missing from Outreach texting?

Check which GiveCampus phone field receives it. Preferred Phone identifies a preferred contact number; it does not by itself mean that the number is a mobile number. For constituent-based texting, map the actual mobile phone type to Cell Phone.

1. Open School Dashboard → Integrations → Blackbaud RE NXT.
2. Open the constituent-import configuration: Constituents in the newer integration screen, or Import Configuration in the tabbed screen.
3. In the enhanced import settings, review Phone Type Mapping. For Cell Phone, choose the NXT phone type your institution uses for actual mobile numbers. Do not map a home or office number as Cell Phone simply to make it appear in a texting audience.
4. Save the configuration and review a representative constituent after the import has processed. Confirm the number is in the intended field before regenerating or reviewing the Outreach recipients.

Mapping Preferred Phone alone is not a substitute for mapping Cell Phone. Missing or invalid numbers, opt-outs and recipient filters can still exclude a person after the mapping is corrected. If the imported record remains wrong, ask Support to inspect the import results rather than repeatedly changing the mapping. CSV-uploaded recipient phone numbers are a separate source and should be checked in that upload.