Activate the Bloomerang CRM integration to connect donations made through Bloomerang Fundraising (formerly Qgiv) to constituents, funds, campaigns, and appeals in Bloomerang CRM. By connecting your data between these two Bloomerang applications, you can track constituent donations and engagement scores more accurately.

Use these resources to learn more about Bloomerang CRM:

To view a quick-start setup video, click below.

To find your API key:

When you first connect to the Bloomerang CRM integration, Bloomerang Fundraising automatically takes you to the integration’s Settings page for further setup.

To manage the Bloomerang CRM integration at any other time, do the following:

Use the Mappings, Settings, and Export History tabs to do the following:

You’ll be taken to a screen where you can configure your settings. Settings are organized into tabs along the left side of the page.

Settings are organized into tabs along the left side of the page. You'll be prompted to Save after you make changes on a tab.

On the General tab, view and manage the following export parameters:

The next tab houses the Export settings.

Exclude Offline & Matching Donations, when toggled on, excludes offline and matching donations from exports.

IMPORTANT: If you choose to export offline and matching donations, only verified transactions will be included.

The Exclude Facebook Donations toggle excludes donations made through Facebook.

The Export GiftAssist as Separate Line Item toggle makes it possible to export GiftAssist as a separate line item from the donation itself.

This is particularly useful when exporting transactions that have multiple line items, such as an event registration with an additional donation. If Export GiftAssist as Separate Line Item is enabled, the GiftAssist amount will appear as a separate part of the transaction. If Export GiftAssist as Separate Line Item is not enabled, GiftAssist will be divided evenly among each of the transaction's line items.

Enable Recurring Donation Support enables the creation of Recurring Schedules when exporting recurring gifts. Each payment of the recurring gift will be associated with the schedule in the CRM.

The Enable Donation Fundraisers toggle attributes peer-to-peer donations to the participants who raised the funds. The participant's name will be recorded in the Fundraiser field in the CRM.

Please note: If you had previously enabled Soft Credits for the integration, you'll see an additional toggle labeled (Deprecated) Enable Soft Credits for Sub-Registrations. This is a legacy setting that has been replaced by the new "Registration Sync" feature. With this legacy setting enabled, registration fees for sub-registrants will be recorded in the Soft Credits field.

Sync $0 transaction as interactions exports $0 transactions, such as free registrations, as "interactions," rather than as $0 "donations."

The Override Contact Opt-in toggle tells the integration not to select "Opted Out” for the Email Interest Type on new constituent records. In other words, enabling this toggle will set Email Interest to "All," regardless of whether a constituent chooses to opt in to communication.

With this setting disabled, each new transaction from a donor will update their Email Interest Type. In other words, if a donor has previously opted in to communication but does not opt in when making a new donation, their Email Interest will change to Opted Out the next time the donor's data is exported to Bloomerang CRM.

The final setting determines the Acknowledgement Status of exported transactions. Your options are Yes, No, and Do Not Acknowledge.

The integration will automatically map dedications in Bloomerang Fundraising to Bloomerang CRM Tribute records during export. If a matching Tribute can't be found, it will create a new Tribute record.

Note that, in Bloomerang CRM, the available tribute types are "In Honor Of" and "In Memory Of." If the dedication type in Bloomerang Fundraising is something other than those two options, the integration will default to "In Honor Of" when exporting to Bloomerang CRM.

Next, determine how you'd like to configure the integration’s Matching Logic.

Your options are to use Bloomerang Fundraising Matching Logic or Bloomerang CRM Matching Logic.

You can use Bloomerang Fundraising Matching Logic with the Individual Constituent Matching Logic and Company Constituent Matching Logic drop-down menus.

The options here determine how the integration will identify existing records in the CRM to import Bloomerang Fundraising information to if they're already in the database.

Using the "Last Name" options, the matching logic can match records by household, so if two people with the same last name, street address, and zip code donate, the integration can apply the gift to an existing record without creating a new record.

For example, Robert Smith can donate as "Mr. and Mrs. Smith" or Jane Smith, who lives at Robert Smith's address, can make a donation and the matching logic will apply the gift to Robert Smith's record in the database.

IMPORTANT: In the case of “Email OR” matching, both sides of the OR statement are equally weighted. In other words, if you select “Email OR (First Name AND Last Name AND Zip Code),” the integration will prioritize finding matching name and zip code equally with finding a matching email address, rather than looking for a matching email address before moving on to other criteria. In the event the system finds two different records with matching criteria, tiebreaker logic will determine which record to match with.

The integration can also match on secondary email addresses that you have saved in the database.

Please note: When using Bloomerang Fundraising Matching Logic, a matched record will not be updated to apply any new information or details, such as a mailing address change or answers to constituent custom fields.

If you’d rather use Bloomerang CRM matching logic, which will update constituent records, toggle on the Use Bloomerang CRM Matching Logic toggle.

This will hide the Bloomerang Fundraising Matching Logic drop-downs. Checks for duplicate records will happen on the Bloomerang CRM side. When determining a duplicate, the system searches an index of the database to get a list of potential matches.

It looks at:

For individuals, both first and last names must match.

Second, the system pulls the accounts for the potential matches from the database and determines if each account is a duplicate.

A potential match is a duplicate when the account IDs match, or when the name matches and one of the following matches:

Full names for organizations must be identical to match.

For individuals' names to match, these must be identical:

Here’s a handy visual to help:

On the Default Values tab, choose a Fund, Campaign, and Appeal from the drop-down menus. The selections you make will be your default mapping locations. Selecting a fund is mandatory, but campaigns and appeals are optional selections.

All activity will be exported to these default values if you don’t add any additional mappings and will be used as the backup mapping locations if a particular transaction hasn’t been mapped elsewhere. This information is pulling directly from your instance of Bloomerang CRM.

In the Campaign and Appeal drop-downs, you'll see a Create New - If it Doesn't Exist option. When selected, if a transaction doesn’t match a configured mapping, a Bloomerang CRM campaign and/or appeal will be created (if it doesn’t exist) using the form name with which the transaction is associated. A mapping will then automatically be configured between that form and the new campaign and/or appeal.

When choosing to create just an appeal or a campaign, the resulting mapping will use the default value for the other object (e.g. Appeal = “Create New” and Campaign default = “General,” the resulting mapping will use the form name for the appeal, and “General” for the campaign).

If there’s any extra information you’d like to add to the Donation Note field in Bloomerang CRM upon export, you can choose from the options in the drop-down menu on the Extra Info tab.

You can read more about what those extra info fields mean here.

You can make multiple selections – they’ll appear one at a time below the drop-down menu as you select them.

Not all information is available for each transaction type (e.g. Participant Name will only show up for peer-to-peer registrations).

Once you’ve saved, click the Mappings tab to display your Optional Mappings options. This is where you’ll configure mappings if you’d like specific data sets mapped to something other than the default values in the settings area.

Click here to download a spreadsheet of additional fields in Bloomerang Fundraising you can map to Bloomerang CRM.

Mappings can be grouped by Mapping Type or by Form using the Group by drop-down menu.

You can also filter your mappings to display only specific Mapping Types or only certain Forms and Events.

To add a new mapping:

You can Edit or Delete a mapping by clicking the three dots at the right side of the mappings table.

If you’d like to delete multiple mappings, check the box next to the mapping’s names, and then click Delete Mappings at the top of the table.

The process is similar for each data set shown in the Optional Mappings area. There may be some slight variations in how many choices you have in each drop-down.

For example, if you’re mapping restrictions, you’ll see another drop-down menu, and still another if you’ve set up sub-restrictions.

When mapping events, you’ll be given the option to drill all the way down to event packages, if desired.

You can also map text campaigns:

Peer-to-peer events just require a form selection and export destination.

You can choose to export other peer-to-peer data, as well.

You can also map auction transactions.

Custom mappings help you choose which target objects and fields you want your data to connect to in the integration. Custom fields must be active in the destination before you can map to them from Bloomerang Fundraising.

There are three custom mapping types:

For each type, you can map to a target object and field using the data from that custom type. For more details, download the standard field mappings spreadsheet.

The matching logic you use determines whether matching records in Bloomerang CRM will update with new details:

Transaction mappings will be updated during export regardless of matching logic.

With static field mappings, you can add static values in Bloomerang Fundraising to target records in the integration service.

With custom field mappings, you can map custom field answers in Bloomerang Fundraising to target fields based on unique custom field reporting labels. For example, you can track custom fields for your fundraising events, such as gathering meal choices.

With standard field mappings, you can map standard field values to a target field.

Some values will be specific to a transaction line item (e.g. restriction name), while others will be for the entire transaction (e.g. transaction ID).

Click here to download a spreadsheet that details all Service Integration Standard Field mappings.

The integration with Bloomerang CRM supports Personal Information Mapping Fields. Select Constituent to find and map the Personal Information fields you can map for export to Bloomerang CRM.

These fields include: FacebookID, TwitterID, LinkedInID, Website, Gender, Birthdate, Job Title, Middle Name, Suffix, and Employer

For Gender valid values are: Male, Female, Other

For Suffix valid values are: Jr, Sr, II, III, IV, V, Esq, PhD, MD, DDS

Additionally, they can now map name suffixes and middle names. These will not appear in their own fields in Bloomerang CRM, but instead get appended to the names that appear in Bloomerang CRM.

In addition to Constituent fields, you can map Bloomerang Fundraising data to Interaction and Transaction fields in Bloomerang CRM.

Please note: If you try to map to the same target object + field (regardless of the type), we will only save the most recent mapping.

Don't forget to save your work!

When you’re ready to run an export, click Export, which is located in the upper-right corner of your settings window. This is only necessary if you chose the Manual export option.

Otherwise, Hourly exports are scheduled to run once per hour at 15 minutes past the hour, but they are not guaranteed to run at exactly 15 minutes past. Actual run times depend on the server load. Daily exports will run at the time you chose.

IMPORTANT: If you're exporting for the first time or have a large number of transactions to bring over, we'd recommend setting your export start and end dates to export one week at a time to avoid hitting API limits.

You’ll receive a message in a pop-up alerting you that your export was completed. If successful, you’ll see the following:

Clicking View Export History will open the Export History Report, but will display only the records associated with this export.

If there were any issues during the export, you’ll see a message similar to the following:

At the top of your integration management screen, you’ll see an Export History tab. Here, you’ll see some basic information about your past exports, including the Export ID, Date and Time, Status, and Total Transactions.

Clicking the Export ID will take you to the more detailed Export History report, filtered by the transactions that were exported in that batch.

To view the full Export History report, click View All Export History.

When you do so, you’ll open the Export History Report, which includes a table which details all exported records across your service integrations.

In the Export History Report you may notice an icon that looks like the outline of a person with a plus sign. This means a new record was created as the result of a new donor or registrant.

Additionally, you may notice an additional alert icon in the Export Status column. Hover over the icon to see more details. The message will also display in the Export History Report.

Follow the link to learn more about the Export History Report.

If you've enabled Registration Sync and synced registrants from an event to your CRM using the tool, you'll also a Registration Sync History table on the Export History tab.

To verify that accounts were created in Bloomerang CRM, log in and click the Constituents icon, search for the donor, click on the donor, and then click Timeline.

To verify donations, click on the pie chart along the left side of the screen, go to Reports, and then Transaction List. Check amounts, constituent, and mapped information (fund, campaign, appeal).

Please note: Multi-restriction and multi-package transactions will be grouped into one record in Bloomerang CRM but will display as "Split Payment" to indicate multiple transactions.

When you export Bloomerang Fundraising data to Bloomerang CRM, certain details will be sent, depending on the type of data. If you set up no additional mappings, this is the Bloomerang Fundraising data that will be used to create or match objects in Bloomerang CRM.

For a more detailed explanation of where Bloomerang Fundraising data maps in Bloomerang CRM, check out this spreadsheet.

Constituent Data:

Transaction Data:

Recurring Schedule Data:

To view Bloomerang Fundraising export data in Bloomerang CRM:

The following appear in the transaction:

If you have a lot of optional mappings, you may want to back them up to a CSV file. This is useful if you need to deactivate a service or adjust your connection and want to make sure your mappings are safe.

To back up your mappings:

Click Re-authenticate to reconfirm your Bloomerang CRM integration credentials or enter credentials for a different account.

When you click Re-authenticate, Bloomerang Fundraising prompts you to activate the integration or cancel the reauthentication process. Clicking cancel keeps the integration set up the way it was before clicking Re-authenticate.

If you no longer need the Bloomerang CRM integration, delete it by clicking Delete Integration in the side navigation.

You'll be prompted to confirm your choice to delete the integration by typing the word DELETE.

If you need to re-enable the integration after deleting it, you can reconnect just like when you originally set up the service integration.

To save you time and prevent you from accidentally creating duplicate records, you'll be prompted to Restore export history when you establish your integration again. Note that this will not import any past integration settings. If you would rather start with a clean slate, select Start from scratch instead.

To be notified via email when a service integration becomes inactive, the integration is locked for an extended period, or a transaction fails to export, you can turn on the Service Integrations notification.

To manage notifications:

To read more about Notifications, read Org-Level Notifications.

For live help, check out our upcoming Group Trainings!