Data Importer - Using the Data Selector to determine required data fields

Find the right data fields for your data imports

The Data Selector is a convenient tool that helps partners quickly determine which data fields are needed to power specific GiveCampus products and features.

Click here to use it, or enter this URL into your browser: https://datarequirements.givecampus.com/
 

What you can do with the Data Selector

Using the Data Selector, you can:

• Select products and features to see the data fields they require
• Select by plan or edition to view field requirements at that level
• Export the results to a CSV for easy sharing and implementation

How it works

Step 1: Choose what you're implementing

• Select the products and features you plan to use, or
• Select your plan/edition (or both)

Step 2: Review field requirements

You'll see fields categorized as required, recommended, or optional for each product/feature combination.

Automatic Lookup ID Generation in Raiser's Edge NXT

How does GiveCampus generate Lookup IDs for new constituents?

When "automatically generate lookup ID in RE NXT" is selected in the gift importer, GiveCampus follows your existing RE NXT configuration and ID sequence. This means:

• New constituent IDs will match your current RE NXT format (e.g., if your system generates 6-digit IDs starting at 100000, GiveCampus will follow this pattern)
• GiveCampus does not generate padded, leading-zero IDs (e.g., it won't create 10-digit IDs like 0000101424)
• The system respects your RE NXT constituent ID sequence settings

Common variations of this question:

• "What format does GiveCampus use for auto-generated constituent IDs?"
• "Will auto-generated lookup IDs follow my RE NXT sequence?"
• "Does GiveCampus create leading-zero constituent IDs?"
• "How are new constituent IDs formatted in the gift importer?"

API Field Limitations

Missing fields in GiveCampus API

Some fields that appear in GiveCampus may not be available through the API for third-party integrations like Omatic:

• event_unique_identifier - Currently not available in the GiveCampus API
• advocate_link_title - Cannot be populated with Event ID data

Workarounds for missing API fields:

Manual data export: Pull gift data via CSV export from GiveCampus Post-import processing: Add missing field data (like event IDs) after importing gifts into your CRM Submit feature requests: Contact support to request additional API fields

Common variations of this question:

• "Why can't I map certain GiveCampus fields in my integration?"
• "How do I get event ID data through the API?"
• "What fields are available in the GiveCampus API?"
• "Can I create custom fields for API integration?"