Looking for some live help? Check out our upcoming Group Trainings! 

Qgiv and Bloomerang have joined forces to create a giving platform that puts relationships at the heart of fundraising! To learn more about the unified solution, check out this handout.

Click here to download a spreadsheet of information we send to Bloomerang by default during export, when applicable. 

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

If you need to contact Bloomerang's support team, follow this link!

Data exported from Qgiv will be added to funds/campaigns/appeals of your choosing in Bloomerang. If you need to create a new appeal and/or campaign during the export process, you do have that option.

Online transactions, Qgiv offline transactions, peer-to-peer offline verified transactions, and refunded/voided transactions are exported. Refunded/voided transactions are only created in Bloomerang if the transaction was exported via the integration before the refund or void occurred.

Contents:

• Getting Started
• General Settings
• Export Settings
  • Acknowledgement Status
  • Tributes
• Matching Logic Settings
• Default Values
• Extra Info
• Optional Mappings
• Custom Mappings
• Running an Export and Export History
  • What Data Gets Exported by Default
• Viewing Your Qgiv Data in Bloomerang
• Backing Up, Re-Authenticating, or Deleting the Integration
• Enabling the Service Integrations Notification 

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

 

Getting Started

Before you can integrate your Bloomerang account with Qgiv, you’ll need your Bloomerang API key.

To find your API key, log in to your Bloomerang account and click the user avatar in the top right of the screen. Then, click Edit My User.

Scroll down to API Keys v2.0, and click Generate to create a new API Key to connect your Bloomerang account to Qgiv.

Give your new API Key a name and then click Generate again.

Copy your new API Key from the table.

With your Bloomerang API Key in hand, log in to your Qgiv account, and click the Integrations item in your organization’s left-hand navigation.

Locate the Bloomerang tile in the CRM section and click Connect.

Enter your API Key and click Connect again.

 

General Settings

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. You'll be prompted to Save after you make changes on a tab.

On the General tab, use the calendar to choose the Export Data Starting On date. If you'd like to export data from a date prior to the current date, you can set your calendar accordingly so historical transaction data will be exported. 

IMPORTANT: The date you set aligns with the transaction dates you'll be exporting. If you set the date to today, only transactions from today and future dates will be exported.

The Export Data Ending On field lets users input a date to end exports from the integration. Leave this field blank if you want the integration to export indefinitely.

In the Frequency drop-down, choose Manual, Hourly, Daily, or Every 15 Minutes exports. 

If you choose Daily exports, you’ll also be able to choose the time (Eastern) for the export to occur.

Beneath the Frequency drop-down is the Maximum Transactions field. This required field specifies the maximum number of transactions Qgiv will export to the integration at a single time. The default setting is to export a maximum of 100 transactions. You can adjust this number higher or lower, but the number field cannot be blank.

Also note that smaller limits provide a safer export, reducing the likelihood of export issues due to a service interruption.
 

 

Export Settings

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 Soft Credits toggle enables the exporting of soft credits for peer-to-peer transactions.

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.  

 

Acknowledgement Status

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

• Yes: Select “Yes” if you want to acknowledge transactions through Qgiv receipts.
• No: Select “No” if you want to acknowledge transactions through Bloomerang CRM.
• Do Not Acknowledge: Select this option if you want to mark the transaction as “Do Not Acknowledge.”

 

Tributes

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

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

 

Matching Logic Settings

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

Your options are to use Qgiv Matching Logic or Bloomerang Matching Logic.

 

Qgiv Matching Logic

You can use Qgiv 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 Qgiv 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 Qgiv 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.

 

Bloomerang Matching Logic

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

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

It looks at:

• Full name (for organizations)
• First name (for individuals; includes common nicknames)
• Last name (for individuals)
• Standardized street addresses
• Email addresses
• Last seven digits of phone numbers

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:

• Email address
• Standardized street address
• Last seven digits of phone number

Full names for organizations must be identical to match.

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

• Last name
• First name, accounting for common nicknames
• Suffix, if both names have suffixes. If only one name has a suffix, the suffix is ignored.

Here’s a handy visual to help:

 

Default Values

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.

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 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).

 

Extra Info

If there’s any extra information you’d like to add to the Donation Note field in Bloomerang 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).

 

Optional Mappings

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.

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, click the Add New Mapping button and then select the Mapping Type from the drop-down.

For example, if you’d like to export data for a specific form, select Standard Qgiv Form > Form from the drop-down menu. Then, use the Form drop-down to select the form.

If you’d like to exclude the Qgiv data from your exports, check the box labeled Exclude from Export.

Excluding can be useful for something like a $0 category for a peer-to-peer campaign. 

 

If you’d like to export the data to Bloomerang, do not check the box, and then select the destination Fund, Campaign, and/or Appeal.

When you’ve configured your mapping, click Add 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.

Peer-to-Peer Classifications

Peer-to-Peer Categories

Peer-to-Peer Restrictions

Peer-to-Peer Store Purchases

You can also map auction transactions.

Auction

Auction Restriction

Auction Package

Auction Item

 

Custom Mappings

You can also add Custom Mappings. You may already have similar mapping set up through the Extra Info fields. If you don't want this information to appear in both places, be sure to delete the Extra Info mappings once you set up your custom mappings.

Custom mappings allow you to dictate which target objects and fields you want data to go into in the integration. Custom fields must be active in the destination before you can map to them from Qgiv. There are three custom mapping types: static, custom field, and standard field. For each type, you can map to a target object + field using the data from that custom type. See the attached standard field mappings spreadsheet for details.

Please note: When using Qgiv Matching Logic, a matched record will not be updated to apply any new information or details, including constituent custom mapping updates. Using Bloomerang Matching Logic will update the records. Transaction mappings will be updated during export regardless of matching logic.

Please note: If a Bloomerang custom field is a "list," the values passed from Qgiv need to match one of the values in that list exactly. If the values don't match, the related transaction(s) will not export. The exception is that the integration will match values regardless of letter casing, so “My Awesome Fund 123” and “my awesome fund 123” would be considered a match.

 

Static

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

 

Custom Field

With custom field mappings, you can map custom field answers in Qgiv 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.

 

Standard Field

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 supports Personal Information Mapping Fields. Select Constituent to find and map the Personal Information fields you can map for export to Bloomerang.

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, but instead get appended to the names that appear in Bloomerang.

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

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!

 

Running an Export and Export History

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.

To verify that accounts were created in Bloomerang, log in and click the constituents icon (just above the pie chart), 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 but will display as "Split Payment" to indicate multiple transactions.

 

What Data Gets Exported by Default

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

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

Constituent Data:

• Name, address, contact information, and communication opt-in status
• If the data matches an existing Constituent in Bloomerang, no updates will be made to the existing object.

Transaction Data:

• Date, gift amount, payment method, Fair Market Value (if applicable), and dedication information (if applicable)

Recurring Schedule Data:

• Start/end date, recurring frequency, amount and the URL of the Qgiv Recurring Details page
• Applies to recurring transactions

 

Viewing Your Qgiv Data in Bloomerang

From your Bloomerang Dashboard, navigate to Reports.

In Reports, view transactions by selecting Transaction List or view constituents by selecting Constituent List.

To view specific transactions, click on the donor Name and then Go to Timeline and select the specific transaction you'd like to view.

The Fund, Campaign, and Appeal options are those you set up in Qgiv.

If you enabled soft credits in Qgiv, a soft credit will be populated here (if applicable).

If you opted to have any notes exported, those will appear in the Note field (if applicable).

You will see transaction information "Processed by Qgiv," and you can view the transaction receipt by clicking the blue button.

 

Backing Up, Re-Authenticating, or Deleting the Integration

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.

Click the Mappings Backup link to access the Mappings Backup & Recovery settings.

From here, you can download your mappings as a CSV file, as well as upload a previously downloaded backup file.

The Re-authenticate link lets users reconfirm their integration credentials or enter credentials for a different account.

When you click Re-authenticate, you'll be prompted 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 this service integration is no longer needed, it can be deleted by clicking Delete Integration in the left-hand navigation.

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

After deleting the service integration, if you need to re-enable 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.

 

Enabling the Service Integrations Notification

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, navigate to the Notifications area of your org-level control panel.  

Click Manage for each user you’d like to receive the notification.  

Then, search for Service Integrations at the top of the screen, or scroll down to Service Integrations in the System Notifications section.  

Check the box next to the notification to activate it. 

Scroll to the bottom of the screen and click Save Settings to save your changes. 

To read more about Notifications, check out this article. 

Looking for some live help? Check out our upcoming Group Trainings!