Salesforce

We use Salesforce for bank reconciliation, and without these IDs, we can’t match GiveLively donations to the corresponding Stripe payouts. Adding them would make reconciliation much easier and reduce manual work. We know Payment Platform Charge IDs are available in Zapier and the Line Items report, but since we rely on the Salesforce integration, this doesn’t help us. If possible, including the Payout ID as well would be even better.

Currently, GL sends all donations to SF with the "Acknowledgement" field marked as "Acknowledged." We want the ability to customize this or disable this as it messes with the way we handle acknowledgements internally.

Please add the ability to use a Salesforce integration user. According to the setup guide on your website, "Please note: Give Lively’s Salesforce integration does not currently support the new Salesforce Integration user license type. At this time we recommend utilizing a standard Salesforce user license."

Payment information including Payment Method and Check/Reference Number are only synced to the NPSP Payment object, but not to the Opportunity object. Please allow this information to sync directly to the Opportunity.

Would be great if we could map ticket purchases as a custom Opportunity Record Type called "Ticket Purchase" or something to differentiate between a true donation and a ticket purchase. People can also make a donation, so being able to map donations and tickets separately through the same transaction would be helpful. Because they are not the same, since the latter is in exchange for a good or service.

Administrators should have the option to define the date from which records will sync. This addresses the common situation where an organization has manually entered Give Lively donations before deciding to use the Salesforce integration, which will create duplicate records unless it is set to only sync records that have never been entered.

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

"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"

It would be great if there was a notification sent to all Give Lively admins if there are errors in the sync between Give Lively and Salesforce.