Changelog

Follow up on the latest improvements and updates.

RSS

Your Data Inbox now groups similar flagged changes into patterns — like "New Emails" or "Email Type Change from Alumni Finder Email to Personal" — so you can review and act on them as a group instead of one by one.
What's new:
  • Flagged changes within each entity tab (Email Address, Phone, etc.) are automatically grouped into patterns based on the type of change
  • Click
    Review all
    on any pattern to see every record in the group, with Almabase and Raiser's Edge data side by side
  • Filter by source — Event Registration, Giving Form, Email List Upload, or others — to narrow down which changes you want to act on
  • Hit Approve all or Ignore all to process the entire filtered set at once
data_inbox_email_announcement
After a homecoming or giving day, what used to take hours of one-by-one review is now done in minutes.
This is already available in your Data Inbox — go to
Settings → Database → Data Inbox
to try it out.

new

Communication Centre

Send emails from your own domain

Your bulk and system emails — newsletters, campaign updates, event invitations, password resets — can now be sent from your institution's own domain instead of the default masked Almabase domain.
For example, if your Almabase site is at alumni.bluefield.edu, emails previously went out from addresses like johndoe@alumni.bluefield.edu. You can now configure an unmasked email domain (like bluefield.edu) so those same emails go out from johndoe@bluefield.edu — a domain your constituents already recognize.
How to set it up:
• Go to Settings > Site Settings > Domain Setup
• Add your unmasked email domain and click Get DNS records
• Have your IT team add the DNS records with your domain provider
• Once validated, reach out to our support team or your CSM to enable it
domain-setup-navigation
One-to-one emails continue to send from the masked domain — no changes there.
For the full setup guide, check out our help article: Link

improved

fixed

Giving

Admin Experience

Mega Update List - Campaign Hubs got an upgrade!

Campaign Hubs have a significant update across the board — more challenge types, more admin control, and a cleaner experience for donors.
Custom challenge type Campaign Hub now has a fourth type:
Custom challenge. No fund, no goal — just a name, a description, and a toggle when you're ready to mark it complete. Use it for any challenge that doesn't fit matching-gift, participation, or fund-highlight.
Fix a wrong challenge type (before any gifts arrive):
The challenge type locked permanently the moment you saved — forcing delete and recreate if you chose wrong. Now the type picker stays editable until the first gift is received. Once a gift lands, the type locks automatically and a tooltip explains why.
Matching gift challenges:
add a total fundraising goal Matching-gift challenges can now have a Total goal — a top-line fundraising target that sits above the match cap. When the match pool runs out, the card no longer says "complete"; it keeps the thermometer moving toward the full goal. The match always applies to the first gifts received; once the cap is used, remaining giving counts toward the total goal without matching. No prize field — the match itself is the incentive.
Start and end times for all challenge types:
Participation, fund-highlight, and custom challenges now have optional start/end date-time fields — the same ones matching-gift already had. Set an end date and donors see the familiar "Ends in …" chip on the card. No end date set means no time-based UI at all.
"Goal matched" — late donors still count:
When a matching-gift or participation goal is already met, cards used to read "Challenge complete," making late donors feel like giving was pointless. Cards now read "Goal matched" with helper text "Your gift still makes an impact." Donors who give after the goal is met continue to appear in the donor list, as long as the challenge is still active.
Live card preview:
A "Preview card" button in the drawer header shows exactly what the donor-facing card will look like — before, partway through, and after completion — using your live, unsaved form state. No saving required.
Gift count and end date on the hub list:
Each campaign row in the hub list now shows a quick-glance meta line below the name: total gift count and end date — or a "Completed" pill for custom challenges. No need to open a campaign to check its status.
Card icons + optional featured image:
Every challenge type can now use a card icon (a curated set, tinted with your site's primary color) when no image is uploaded. Featured images are now optional across all types. Existing campaigns are unaffected.
Smarter card-summary field:
The Summary (Card preview) field now locks automatically when the selected type has a goal thermometer competing for the same card space — matching gift always; participation once a goal is entered. It stays editable for custom challenges, fund-highlight, and participation without a goal. Any summary you've typed is preserved if the type or goal changes.
Two long-standing friction points in the data pull process from Raiser's Edge NXT or BBCRM are now resolved.
Almabase filter option
  • Target a specific subset of existing records for a refresh, such as the Class of 2000 or donors from San Francisco, without building a separate list or query in your CRM.
  • Build a filter in Data Studio, copy the criteria, and paste them into the pull setup.
  • Only matching records that already exist in Almabase are updated. No new records are created.
image
Separate entity selection for new and existing records
  • When running a pull in Create and update mode, you can now choose entities independently for new records and for existing ones.
  • Pull all fields for new constituents while limiting which fields are refreshed for records that already exist.
  • This protects data your constituents have already updated themselves from being overwritten by CRM data.
image
Your email click rate no longer counts clicks on the unsubscribe link. The click rate now reflects only clicks on the content links in your email — buttons, hyperlinks, and calls to action.
What this means:
  • Click rates give you a cleaner picture of how recipients are engaging with your email content
  • If you compare click rates on older emails to recent ones, older emails may show a slightly higher rate — that's because unsubscribe clicks were previously included in the count
  • The actual engagement with your content links hasn't changed — only how the metric is calculated
No action needed on your end. This change applies automatically to all emails going forward.
You can now configure the default communication consent for all channels — Email, Phone, Text, and Post — on the sign-up form.
Why this matters:
Previously, new users could be unintentionally marked as unsubscribed from communication channels when they signed up, depending on how the form defaults were set. This meant admins had to manually fix consent settings for new signups, or risk not being able to reach them.
Now you can set each channel's default to
Opted in
or
Opted out
at the site level, so every new sign-up starts with the consent state you intended.
image
The Feedback section on your event and giving page reports now includes an
"Export all reviews"
button.
Previously, you could see the star rating breakdown and click "See all reviews" to read individual responses — but there was no way to export them. Now you can download all ratings and comments as a file.
Use it to:
  • Record feedback externally for your team's records
  • Share reviews with stakeholders who don't have admin access
  • Follow up with guests or donors who rated their experience low
You'll find the
"Export all reviews"
link at the bottom of the Feedback section in your event or giving page reports.
image
When you open a communication group and click "View Members," you now see a deliverability breakdown at the top — how many members will receive the email and how many won't, with the percentage for each.
What you can do:
  • Use the Will receive and Won't receive tabs to filter the member list
  • See the specific reason each member won't receive (Bounced, Unsubscribed, Invalid, etc.)
  • Click "Export non-deliverable" to download the full list of members who won't receive, so you can update email addresses, reset statuses, or reach out directly
  • Search for a specific member by name or email
This helps you understand your group's reach before you hit send, and take action on the members who would otherwise be missed.
image
The anonymous gift checkbox now appears on the pre-payment form — before donors reach the checkout screen. This way, donors can decide to give anonymously upfront, rather than after they've already entered payment details.
What else is new:
Admins can optionally move the
Employer
and
Tribute
fields to the pre-payment form as well, keeping the checkout screen focused entirely on payment.
These changes apply to all giving pages automatically. No setup needed — just configure which fields appear on pre-payment vs. post-payment in your giving page settings.
image
We've redesigned the Guest and Gift Mapping experience to help you find and map constituents faster.
What's new
View all the information you need in one place
The mapping screen now displays more source information, so you can confidently identify the correct constituent without switching between multiple screens.
Search Almabase and your external database together
Instead of searching each system separately, you can now search across both Almabase and your external database in a single step, making the mapping process much faster.
A streamlined mapping workflow
We've consolidated the mapping experience into a single screen, allowing you to review information, search, and complete the mapping without unnecessary navigation.
Availability
The new mapping experience is now available in the Sync dashboards and related mapping screens.
We're continuing to use the previous mapping experience in the Guest Manager and Gift Manager, where additional data movement workflows are still supported.
As always, we'd love to hear your feedback!
redacted_mapping
Load More