Would like to be able to have different record types for event tickets vs. regular donations.

"A bit of feedback: I wasn't able to set mappings prior to that initial sync, so those records came over mapped incorrectly. It's simple to fix - there weren't very many records and they are easy to find and update. But it's a bit of a flaw in the process, having the sync kick off before the mapping is complete"

We have had a donation enter Give Lively with just one name. The sync failed as Give Lively attempts to sync to the first name. Since no last name exists, Salesforce cannot create the user.

It would be great to see improvements in the matching logic Give Lively uses when choosing to update existing contacts or create new. Scenarios: 1) Donor makes a gift as jdoe@gmail.com . Jane Doe's Email address and Work Email in Salesforce is recorded as janedoe@company.com , but her Personal Email is jdoe@gmail.com . Currently, Give Lively would create a new contact instead of updating the existing. 2) Donor makes a gift as jdoe@gmail.com . Salesforce has a lead with the email address of jdoe@gmail.com , as well as two different contact records with the same email address. Give Lively picks one and associates the gift. It would be better if the administrator could be alerted to the multiple matches, and given a chance to select which one is correct.

The Give Lively integration will sometimes fail to sync when Salesforce's State & Country Picklists feature is enabled. It would be nice if synced addresses could be made compatible with existing picklist values.

Request from Robert Mulcahy (npsa) to speed up automatic syncs as one hour is too long when testing. Other vendors either sync in real-time or run batch sync every 15-30 minutes.

Right now, the integration does not map to existing SF campaigns.