For many nonprofit teams, supporter data becomes fragmented over time. Donations live in one place, event registrations in another, email engagement somewhere else, and staff have to piece together context manually. Altrinum is designed to reduce that fragmentation by treating the constituent profile as the main record for the relationship.
That is why a constituent profile shows more than contact details. Depending on the supporter’s history and the modules your organization uses, it can also bring together giving activity, registrations, email activity, tenant-level marketing status, preferences, and prospect context. The goal is to help staff understand the whole relationship with a person instead of only one channel at a time.
Why constituent profiles matter
A constituent profile is more than an address book entry.
It is the place where staff can answer questions such as:
- Has this person donated before?
- Have they registered for an event or program?
- Are they currently eligible to receive marketing email?
- Have they engaged with past campaigns?
- Does this person already exist in the workspace under a slightly different record?
- Is there prospect context staff should be aware of before outreach?
When these answers are available in one place, staff can make better decisions about stewardship, segmentation, outreach, and reporting.
Why audience groups are separate from constituent records
Audience groups are intentionally separate from the core constituent record because segmentation changes over time.
A constituent profile should represent the person and their history. An audience group should represent a purpose or rule set.
For example, the same supporter might:
- belong to a donor segment this month
- appear in an event follow-up group next month
- be excluded from a campaign because of suppression or topic preferences
- later qualify for a lapsed-donor re-engagement segment
If segmentation were stored directly on the base profile as a permanent identity label, teams would constantly be rewriting records to reflect temporary campaign needs. That usually makes the database harder to trust.
Dynamic groups solve that problem by allowing the segment to be recalculated from current data without changing the constituent’s underlying profile.
Static groups vs dynamic groups
Altrinum supports different ways of organizing audiences because nonprofit teams use lists for different reasons.
Static groups
Use a static group when staff want to maintain a deliberate list that should not change automatically.
This is usually best for:
- hand-curated outreach lists
- board or volunteer review lists
- one-time campaign audiences
- imported segments from another system that need staff review
A static group is useful when the list itself is the decision.
Dynamic groups
Use a dynamic group when membership should be determined by rules rather than manual maintenance.
This is usually best for:
- donors above a giving threshold
- registrants for a specific event
- supporters who opened or clicked a campaign
- people who are eligible for marketing but have not donated this year
- suppression or follow-up segments that need to stay current
A dynamic group is useful when the logic is the decision.
How audience management supports real nonprofit work
Audience management is not only about building email lists. It also supports day-to-day operational decisions across fundraising, programs, and events.
Examples include:
- finding all recent donors for stewardship follow-up
- building a segment of event attendees who should receive a thank-you message
- excluding recent registrants from an invitation campaign
- reviewing people who are suppressed or ineligible before a send
- identifying highly engaged supporters for deeper cultivation
- creating a working list for a campaign without changing the underlying constituent record
The more consistently a team uses constituent profiles and groups, the easier it becomes to reuse data across modules instead of rebuilding lists from scratch every time.
Marketing eligibility is not the same as group membership
One of the most important concepts for staff to understand is that being in an audience group does not automatically mean someone can receive an email campaign.
Group membership answers the question:
“Does this person match the audience criteria?”
Email eligibility answers a different question:
“Can this person be contacted in this way right now?”
A constituent may match a group and still not be eligible for a send because of tenant-level suppression, do-not-contact status, unsubscribe state, or other preference-related controls.
This separation is intentional. It helps teams build useful segments without accidentally bypassing consent and suppression safeguards.
Interest groups and audience groups serve different purposes
Audience groups and interest groups may look similar at first, but they serve different jobs.
Audience groups
Audience groups are staff-facing tools for organizing and filtering people based on rules, history, or operational needs.
Interest groups
Interest groups are part of the communication preference layer and are used when deciding who should receive a campaign or what a person has opted into.
A person might appear in a donor audience group because they meet fundraising criteria, but still be excluded from a specific campaign because they are not eligible for that communication or do not belong to the relevant interest group.
This distinction matters because it keeps operational segmentation separate from communication permission logic.
Why imports are conservative
Constituent imports in Altrinum are designed to be cautious because supporter data is often one of the most sensitive and durable parts of a nonprofit system.
A quick import can create long-term cleanup problems if it:
- overwrites trusted data with lower-quality data
- creates duplicate constituent records
- loosens suppression history accidentally
- treats imported records as permission resets when they are not
That is why the import flow focuses on profile updates, dry runs, conflict review, and duplicate handling before anything is committed.
The system is designed to help teams migrate and enrich data safely, not to shortcut review where review matters.
Recommended mindset for teams
The healthiest way to think about audience management is:
- the constituent profile is the source of relationship context
- audience groups are reusable ways to organize people for work
- imports should improve data quality, not rush past it
- segmentation should stay flexible
- communication eligibility should remain protected by preference and suppression rules
When a team follows that model, audience management becomes much more than a list-building tool. It becomes the shared operational layer that connects fundraising, events, marketing, and stewardship.