Once contact details from an event registration or giving campaign have landed on the Almabase profile — through the connector rules covered in Pushing contact details from Events and Giving to Almabase profiles — the next step is getting them into Raiser's Edge NXT or BBCRM.
This article covers that second hop: pushing the event and giving contact data from Almabase profiles into your CRM.
Prerequisite: The contact details need to be on the Almabase profile first. If you haven't completed that step, see Pushing contact details from Events and Giving to Almabase profiles.
How It Works
Your constituent sync rules control how profile changes travel from Almabase to Raiser's Edge NXT or BBCRM. These rules are configured under Settings → Database → Sync Rules.
The three sync modes
For each type of data (phone, email, address, etc.), you can set one of three modes:
Automatically Update — changes flow directly to your CRM without review
Review Before Updating — changes are flagged in the Data Inbox for your approval. This is the default.
Don't Update — changes are not sent to your CRM
The Data Inbox
When your sync rules are set to "Review Before Updating," updated contact details appear in your Data Inbox after they're applied to the Almabase profile.
You can access the Data Inbox from two places:
Settings → Database → Data Inbox
Reports → Data Inbox
Step by Step
Step 1: Open the Data Inbox
Go to Settings → Database → Data Inbox (or Reports → Data Inbox). You'll see tabs for different data types — Addresses, Phone Numbers, Emails, and others.
Step 2: Filter to your event or campaign
The Data Inbox collects changes from all sources. To focus on the changes from a specific event or giving campaign, use the Source filters to narrow down to Event Registration or Giving Campaign.
Step 3: Review by pattern
The Data Inbox groups similar changes into patterns so you can review them efficiently. After an event, you'll typically see patterns like:
New addresses — guests who shared an address for the first time
New phone numbers — phone numbers from the registration form
New emails — email addresses from the registration form
Click Review all on any pattern to see the individual records.
Step 4: Approve or ignore
For each record, you'll see the new value from Almabase alongside the current value on Raiser's Edge NXT or BBCRM. You can:
Approve — the change is applied to the constituent record in your CRM
Ignore — the change is not sent to your CRM
Use Approve all or Ignore all to process patterns in bulk when you're confident in the data.
Tips
Process the Data Inbox promptly after an event or campaign. Event-related changes are easiest to review when they're fresh and grouped together. Waiting too long means they'll mix with changes from other sources, making the review harder.
Use source filters. The Data Inbox collects changes from everywhere. Filtering by Event Registration or Giving Campaign keeps your review focused on the event or campaign you're working through.
FAQs
My sync rules are set to "Automatically Update" for everything. Do I need to check the Data Inbox?
For contact details from events and giving campaigns, no — they flow directly to your CRM.
I approved data on the Guest Dashboard, but it's not in RE NXT. Why?
There are two review points in the flow. Approving on the Guest Dashboard moves data to the Almabase profile (the first hop). Whether it reaches your CRM depends on your constituent sync rules. If they're set to "Review Before Updating," the data is waiting in your Data Inbox for a second approval.
Can I change sync rules while changes are pending?
Yes. New rules apply to everything processed from that point onward. Changes already sitting in the Data Inbox stay there for review regardless of rule changes — they were captured under the old rules.
When I approve data in the Data Inbox, does it replace what's already in RE NXT / BBCRM?
It depends on how the change is flagged. If it's flagged as New Information, it will be appended alongside what's already there. If it's flagged as an Update, it will replace the existing value.