Kindful has an integration with Qgiv. Qgiv was born from a desire to offer user-friendly, easy-to-use services that could process charitable donations, event registrations, pledges, and more.
Data exported from Qgiv will be added to funds/campaigns/appeals of your choosing in Kindful. If you need to create a new appeal and/or campaign during the export process, you do have that option.
This article explains how to connect your Qgiv account to your Kindful account. Follow the guide below to successfully connect Qgiv to Kindful and see your Qgiv data automate into Kindful.
To integrate your Kindful account with Qgiv, click the Service Integrations item found under Reporting in your organization’s control panel.
You'll be taken to a screen where you'll enter your Kindful credentials.
The Frequency drop-down allows you to choose from Manual or Continuous exports.
Directly below the frequency drop-down, you'll see a toggle that says Mark Transactions as Acknowledged. Toggle this on if you'd like us to flag transactions in Kindful as already having been acknowledged. Keep in mind the Acknowledgements Tool if you choose to set this.
You can use the calendar selector to choose the date on which you’d like to start exporting data.
The API Connection shows you if your API status is active. It will turn green once you're all set up.
In the Fund and Campaign drop-down menus, the selections you make will be your default mapping locations. This is a required step.
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 Kindful.
If there’s any extra information you’d like to add to the Transaction Admin Note Field field in Kindful upon export, you can choose from the options in the Extra Info drop-down menu.
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).
When you’ve configured your settings to your liking, click Save. You’ll need to click Save even if you haven’t made any changes. You may also choose to Cancel your actions or Delete Integration.
Once you’ve saved, click the arrow shown below 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.
For example, if you’d like to export data for a specific form, click Form, then select Add Mapping.
In the Qgiv Data drop-down, you’ll need to select which Qgiv form from which you’d like to export data.
In the Kindful Data drop-down, you’ll first need to select if you want to set up a mapping or exclude the data.
If you chose Map To:, your next step is to select the export destination in Kindful.
If you'd like to add more than one mapping in each section, click the Add Mapping icon. When you’ve configured your mappings in a section, click Save. You may also choose to Cancel your actions or Delete Export Type.
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. Donations made using the multiple restrictions option will be split up into multiple donations.
When mapping events, you’ll be given the option to drill all the way down to event packages, if desired.
Peer-to-peer events just require a form selection and export destination.
You can choose to export other peer-to-peer data, as well.
Running an Export (Qgiv)
When you’re ready to run an export, click Run 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, 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 time depends on server load.
Please note: The date you set aligns with the transaction dates you'll be exporting. If you set the date to today and choose the continuous option, only transactions from today and future dates will be exported. If you'd like to export past data, you can easily set the calendar accordingly and run a manual export to get historical transaction information before setting the continuous export option.
You’ll receive a message in a pop-up alerting you that your export is underway.
If you click View Export Details, you'll be taken to a table showing your exported transactions. Here's a quick rundown of what's happening behind the scenes:
- Qgiv exports all transactions
- Qgiv marks the transactions being exported as in progress
- Every 5 minutes, Qgiv checks the status of all in progress exports and updates the status if it has changed (to success / failure for example)
- If the status is still in progress after 12 hours, Qgiv marks it as failed
Pending exported transactions are indicated above the table and by the hourglass at the end of each row. Online, Qgiv offline transactions, and peer-to-peer offline verified transactions are exported. Refunds, voids, and charge backs are not exported.
Once transactions have gone through, the table will update to show a successful export, as shown below.
If there were any issues during the export, you'll receive a message letting you know.
To the right of your settings, you’ll see an Export History table which displays the name and date of each export. It holds up to 10 entries and contains export history for all service integrations you’ve set up.
To view all export history, click the View All Export History button below the table.
When you do so, you’ll see a more detailed table which includes an overview of transactions that were exported, including how many were successful and how many failed.
A green dot means the export was successful; gray means it was unsuccessful.
You can click View Details to be taken to the Export Details table shown earlier.
If you do have any unsuccessfully exported transactions, the Success/Failed numbers above the table will reflect that information. If a transaction wasn’t successful, you can click the eye icon at the end of the row of a failed transaction in the table to view the error message.
If the error relates to an email address and/or is something that can be fixed, you can do so by clicking the transaction ID to make the necessary change. You can then use the red X icon to remove that transaction from the table. When you run another export, the transaction will be exported at that time. If any additional errors are present, you’ll note those as you did the previous error.
When you remove a transaction from the list, you’ll receive a verification message:
Transaction removed from Export history
The Success/Failed numbers above the table will update accordingly.
Kindful handles duplicate contact matching, so Qgiv has no way to determine if a new contact was created. Duplicates are checked for based on the following: First Name + Last Name + Email OR Company Name + Email.
Kindful transactions have an “Allow Public Name Display” field that is not accessible via the API, so you may see an “Anonymous” entry added to the Admin Note field when applicable.
Kindful contacts do not have a concept of opting in to communication, so that value does not get transferred over.
Please note: Multi-restriction and multi-package transactions get split up into multiple Bloomerang donations. If you have GiftAssist enabled, those amounts get divided up across transactions. In case there is a remainder, one donation may get a bit more than the rest.