GoFundraise Customer Care


Salesforce Connector Managed Package FAQ


This article contains FAQ regarding the GoFundraise Salesforce Connector Manage Package Solution. If you are using a Custom Setup see Salesforce Connector - Custom Setup FAQ page.  




How does it work?

The Managed package creates known default objects, record types and picklist values within a Salesforce instance. The data sync then uses the Salesforce batch API connection to upsert data into SF. This allows us to bundle up donations / events / fundraising pages and send them across to SF anywhere from every minute to whatever schedule the organisation requires. The default is every 12 hrs.


What limitations does it have?

The sync map must abide by set rules. It cannot make judgment calls on data like a person can looking at a spread sheet of donations to notice that e.g. John Smith makes two donations of the same amount.

The Managed Package creates and syncs data into specified fields, these cannot be altered. A Hybrid / Custom solution may map field in addition the that of the managed package through a custom sync map.

Managed Package creates fields under the following objects:


The sync deduplicates its own data, but will handle contact deduplication rules which prevent the addition of duplicate contacts by handling the error returned for this scenario. If there is no internal contact deduplication preventing inserting duplicate contact, duplications can occur with existing data. You might need to setup an internal Salesforce workflow to prevent duplication.


How often can it sync?

It uses a cron schedule, so anywhere from every minute to once a year.


What is involved with setting up the sync tool?

Install the GoFundraise Salesforce Connector as per process available later in the article.

Run the automated configuration within the Salesforce App screen.

Contact GoFundraise Customer Care to enable the sync to be setup on the Gofundraise platform.


What is the Salesforce connector? An App? A plugin? How does it link my CRM to my GoFundraise account?

The GoFundraise – Salesforce connector is an API (Application Programming Interface) software connection from GoFundraise to Salesforce. It links GoFundraise to Salesforce not Salesforce to GoFundraise. It is software on GoFundraise that connects and talks to Salesforce.

The GoFundraise managed packaged automatically creates and configures salesforce objects, layouts, views, picklists and permission sets, to ready the salesforce instance to receive GoFundraise data from the sync connector.


How does it connect?

Please follow the process described later in the FAQ

How are invoicing and GST components reflected in Salesforce when using the Salesforce connector?

All transactions through the Salesforce Connector will appear as Gross totals i.e. inclusive of GST/merchant rates/service rates.


How many API calls does the sync tool use?

The sync tool uses a bulk API call. This limits the number of calls to about 9 calls for each batch of donations it syncs with Salesforce. This amount can vary based on error handling and deduplication lookups. The GoFundraise Sync connector attempts to maximise the amount of data per API call based on Salesforce limitations to minimize the number of API calls used on your Salesforce instance.


How many API calls do I get?

You will need to check in your own System Overview, but an Enterprise Edition of Salesforce will normally have 10,000 calls per rolling 24 hrs. You may also get an additional amount of calls per license you have.


Will our Salesforce workflows still run for the imported donations?

Yes, as long as the workflow criteria is still met. You may need to update some workflows to utilize new fields created by the managed package. For example, the NPSP Soft Credit Contact roles need to be updated to include the newly created contact roles from the GoFundraise managed package


How do we distinguish between imported Go Fundraise donations and other donations?

LeadSource will be set to GoFundraise


Regarding transactions, how much of the info can be moved to Salesforce? For example, which level of the details will be transferred to Salesforce for a given transaction? (type of transaction: credit card/Mastercard/PayPal, etc)?

Information filled out on the fundraising page can be pushed into Salesforce.

e.g. Stage, Amount, Fundraiser page (as a Campaign), Product, Close Date, Fundraiser and Donor Contact Roles

The exact fields are available in the managed package FAQ https://support.gofundraise.com/hc/en-us/articles/360054142034-Salesforce-Managed-Package


How will soft credits be reflected in the system?

In native NPSP the contact roles are populated but these need to be included in the NPSP settings in order to apply.


Do we have any release notes that we could share?

We're currently working on release notes to share.


How does the integration with Good2Give work in combination with the Salesforce connector?

Donations and matching amounts passed through to the GoFundraise platform will appear in the data synced into the Salesforce instance. Only the data regarding the donation that is held by GoFundraise is able to be synced in. Not all workplace giving is passed through to GoFundraise from Good2Give.


Do campaigns (fundraising pages, team fundraising pages & events) need to be created in Salesforce beforehand manually?

No, they do not. The sync tool will create a Campaign and Child Campaigns for Events and Fundraising Pages when they are created in GoFundraise. This will allow an email alert to be created in Salesforce so that the new Campaign can be checked and linked to any parent Campaign that is being used. Fund Allocations can also be added at this stage.

Events and Fundraising pages are only deduplicated when synced in by GoFundraise. Any manually created events or pages will not be deduplicated.


Are donations linked to a Campaign?

Each Fundraising Page/Event in GoFundraise is treated as a Campaign in Salesforce. Each donation made to a page will be added to the corresponding Campaign.


How does the system handle contact duplication? How do you prevent duplicates?

GoFundraise tags each contact with its own unique ID. GoFundraise uses email address + firstname + lastname de-duping. If there is an existing deduplication rule within Salesforce to prevent the additional of duplicate contacts, the GoFundraise system will also perform an additional lookup to deduplicate against the existing contact when adding the contact fails.


Who would be able to change the current schedule of integration?

Currently the schedule is set in the Admin section of the sync tool. During setup a sync schedule will be agreed upon. Normally set to twice a day e.g. 8am and 2pm. This can be altered where required. For high volume accounts, more regular sync periods are recommended.


How does the sync schedule work?

The sync schedule is driven by a crontab file. There are 5 sections to the cron schedule, minutes, hours, day of the month, month and day of the week.

# ┌───────────── minute (0 - 59)

# │ ┌───────────── hour (0 - 23)

# │ │ ┌───────────── day of month (1 - 31)

# │ │ │ ┌───────────── month (1 - 12)

# │ │ │ │ ┌───────────── day of week (0 - 6) (Sunday to Saturday;

# │ │ │ │ │ 7 is also Sunday on some systems)

# │ │ │ │ │

# │ │ │ │ │

# * * * * * command to execute

If you wanted 15 minutes past every hour you would use: 15 * * * *

For 6:15am every day : 15 6 * * *

For 6:15am and 1:15pm every day: 15 6,13 * * *


What's the level of customisation of the tool? If fields have to be added in Salesforce at a later stage, who can map them with the connector?

The managed package does not allow any customization in the fields created within salesforce.

Using a hybrid or custom sync product allows customisation to be made on what fields are populated in each object. Currently our admins will have to make customisation updates to the sync. The road map might eventually have a user interface for the sync map.


Who will be the direct contact person for support?

Once the GoFundraise-Salesforce Connector has been successfully setup, contact our Customer Care Team on if any issues develop after the initial setup has been signed off on.


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request