Find a constituent and inspect profile, gift, and email history

Find the right record

1. Open School Dashboard → Constituents.
2. Choose Imported Constituents, GiveCampus Constituents, or All Constituents. The default imported tab does not contain every individual in the school.
3. Use Search Constituents for a name or email. To search an institutional identifier, select Search by Constituent ID and enter the identifier with its intended leading zeroes.
4. Open the person's name. For records without a display name, the identifier can be the detail link.

, Imported Constituents have a linked school-level file import; GiveCampus Constituents lack that import link. The latter can be generated by activity elsewhere in GiveCampus. These are source categories, not “donor versus non-donor” or “has an account versus no account.” The list is scoped to individuals and the selected tab; start with All Constituents when the source is uncertain.

Understand the profile

Overview shows constituent details, Primary Data Source, Donor Status, Contact Restrictions, Smart Appeal status and recent Smart Appeal emails. Missing values can reflect absent source data. N/A donor status alone is not proof of no gifts.

Contact restrictions include Smart Appeal Unsubscribed? and Solicit Code(s). Read those with the applicable product's suppression rules; one field is not a complete email/text permission report.

Use the Gift History and Email History tabs for their respective details. Gift History separates One-Time Gifts (date, type, source, designations and amount) from Recurring Gifts. Email History includes separate Smart Appeals and GC Outreach sections. Email History includes sent Outreach and Smart Appeal records. It is not a universal log of every message or mailbox communication. To investigate a missing email, identify the sending product and actual send state.

When a search gives no results

Check the active tab and name/email-versus-ID mode first. Confirm exact identifier formatting and source import status. If the person still cannot be found, provide the intended school, identifier and relevant import to an authorized administrator/support contact. Do not create a second record merely because a filtered search is empty. See identifier management.

Validate constituent giving summaries and degrees through the API

Validate imported fields in the v2 constituent response: lifetime_giving_amount, consecutive_years_giving, fiscal_year_giving_amount, and degrees. The standard constituent Overview and Gift History screens are not an inspector for every imported field: they do not display all three giving aggregates and degree records. The API can store these values even when they are absent from that page. Degree records in this API are distinct from the legacy volunteer-management degree records.

Constituent response does not provide per-field update provenance

The v2 constituent response does not expose a per-field provenance value identifying online donation, event registration, or Engagement Center call as the origin of a biographical change. created_at and updated_at are constituent CRM-data timestamps, not source labels. Internal email import_source metadata is not included in the public email response and should not be assumed to identify those three workflows. For CRM mapping, retain the originating transaction or activity context when ingesting its data; the constituent endpoint alone cannot supply the requested source distinction. Do not fabricate a source field or infer one from a timestamp.