Salesforce integration settings
If this is your first time viewing the Salesforce integration settings, we recommend reviewing them all to make sure they are configured to your needs.
Settings for the Salesforce base (NPSP) integration are found in the GoFundMe Pro Control Panel. To get to settings:
- Log in to Salesforce
- Select the App Launcher
- Search for and select GoFundMe Pro Control Panel V2
- Select the Settings tab
A dropdown list will appear, then select the settings menu you want to view.
Note: Any changes to your settings are not retroactive. Changes only apply to new or updated records.
Account & Contact
Under Account & Contact, you can manage how the Salesforce integration creates and updates Accounts and Contacts. Once you make the changes you need, select Save.
Enhanced Contact Matching
Enhanced Contact Matching prevents duplicate contacts. While Salesforce has an efficient tool for this, Enhanced Contact Matching automates the contact matching process. To ensure this feature works properly, be sure to review your Matching and Duplicate rules before turning this on. Learn more about Enhanced Contact Matching.
NPSP Email Matching
This feature is for users with the NPSP Extension installed. Learn how to set up the NPSP Extension.
Turn on this setting to use a matching feature that compares email addresses across all NPSP email fields (Home, Work, and Alternate). The match is performed after your other duplicate rules. However, no other duplicate rules are necessary for this feature.
| Setting | Description |
| Enable SF Enhanced Contact Matching |
Active: Matching and Duplicate rule settings are used to handle duplicate contact management. Before turning this one, please review Matching and Duplicate Rules. Inactive: Email will be used to find the best match. |
| NPSP Email Matching |
Active: Use a matching feature that compares email address across all NPSP email fields. Inactive: Contact matching will not compare email address across NPSP email fields. Note: If Enhanced Contact Matching is enabled, NPSP email matching is performed after your active duplicate rules. |
| Add Contact Mailing Address as Other |
Active: Contact mailing address information is added to the “Other Address” field. Inactive: Contact mailing address information is added to the standard address fields. |
| Update Existing Contact Birthdate | Deprecated: Birthdate custom question in GoFundMe Pro must be custom mapped. |
| Update Existing Contact Phone |
Active: When an Existing Contact is found, update the standard Contact phone number field with information from GoFundMe Pro. Inactive: Existing Contact phone number will not be updated with information from GoFundMe Pro. |
| Use GoFundMe Pro Supporter information for Contact matching and creation |
Active: GoFundMe Pro Supporter information for transactions will be used to create or match contacts. Inactive: Billing information for transactions in GoFundMe Pro will be used to create or match contacts. |
| Set Default Account Record Type | Applies the specified Record Type to all Account records created by GoFundMe Pro. Note: This setting is not used if NPSP is installed in your instance. |
| Add Contact Address to Account |
Active: The address attributed to a Contact will be populated in the standard Account address fields. Note: This setting is not used if NPSP is installed in your instance. Inactive: The address attributed to a Contact will not be set on the Account. |
| Set Default Contact Record Type | Applies the specified Record Type to all Contact records created by GoFundMe Pro. |
| Update Existing Contact Name |
Active: Updates existing Contact First/Last Name fields with data from GoFundMe Pro. Inactive: Contacts will be matched and used to set the value for lookups on other objects, but Contact data will not be updated. |
| Update Existing Contact Address |
Active: Updates an existing Contact record with address data from GoFundMe Pro. Inactive: Contacts will be matched and used to set the value for lookups on other objects, but Contact data will not be updated. |
Donation
Under Donation Management, you can manage settings related to Donations (Opportunities). This includes Contact Roles and recurring donations. Once you make the changes you need, select Save
| Setting | Description |
| Set Default Closed Won Stage Name | Stage name for successful (Closed Won) donations processed by GoFundMe Pro |
| Set Default Opportunity Type | Sets a default Opportunity Type field for all GoFundMe Pro Opportunities |
| Enable Parent as Primary Campaign Source |
Active: For Peer-to-Peer and Registration with Fundraising campaigns, use the GoFundMe Pro parent Campaign as the Primary campaign for an Opportunity Inactive: Donations to individual and team fundraising pages sync to their related child Campaign |
| Prevent Creation of Matched Gift Opportunity | Deprecated: Prevent matched donations from GoFundMe Pro automatically creating separate Opportunity records. |
| Opportunity Contact Role Soft Credit |
Define a label for the Contact Role that receives soft credit for a donation. Soft credit is for donations that a contact did not make but may have influenced. For example, they were a fundraiser or team captain. |
| Default Opportunity Contact Role | Define the text for the Role field when a Contact Role is created on an Opportunity. ‘Donor’ is the default value |
| Set Default Opportunity Record Type | Sets the Opportunity Record Type that is assigned to all GoFundMe Pro Opportunities/Donations |
Parent as Primary Campaign Source
If enabled, donations to individual and team fundraisers will be attributed to the GoFundMe Pro parent campaign record instead of the child campaigns.
Campaign
Under Campaign, you can manage settings related to Campaigns. This includes GoFundMe Pro campaigns, fundraising pages, fundraising teams, and campaign members. Once you make the changes you need, select Save.
Note: Using Automatic Campaign Member Management in NPSP settings will create campaign member statuses according to NPSP configuration.
| Setting | Description |
| Set Default Campaign Record Type | Applies the specified Record Type to all Campaign records created by GoFundMe Pro. |
| Add Donor as Campaign Members |
Active: Donors are added as Campaign Members. Inactive: Donor Campaign Member records will not be created. |
| Add Donors as Child Campaign Members |
Active: Donors are added as Campaign Members to individual and team fundraiser campaign records. Inactive: Donors are only added as Campaign Members to the parent Campaign. |
| Add Fundraiser as a Campaign Member of a Team |
Active: A fundraiser is added as a Campaign Member of their related Team Campaign. Inactive: An individual fundraiser is not added as a Campaign Member for the Team Campaign. |
| Add Fundraiser to Parent Campaign |
Active: An individual fundraiser will be added as a Campaign Member of the parent GoFundMe Pro Campaign. Inactive: An individual fundraiser will not be added as a Campaign Member of the parent GoFundMe Pro Campaign. |
| Disable Attendee as Campaign Member |
Active: Campaign Members with a status of "Attendee" will not be created for Ticketed or Registration with Fundraising campaign types. Inactive: Campaign Members with a status of "Attendee" will be created for Ticketed or Registration with Fundraising campaign types. |
| Use Internal GoFundMe Pro Campaign Name |
Active: The internal GoFundMe Pro Campaign Name populates the standard Name field instead of the public name. Inactive: The public GoFundMe Pro Campaign Name populates the standard Name field instead of the internal name. |
| Prevent Attendee to Contact Creation for Ticketed Events |
Active: Attendees will not create Contacts, Opportunity Contact Roles, or Campaign Members only for "Ticketed" Campaigns. Inactive: Attendees will create Contacts, Opportunity Contact Roles, or Campaign Members only for "Ticketed" Campaigns. |
| Select Campaigns for creating Contacts | Use this setting to select specific Campaigns that you’d like to create Contacts for Attendees. This setting supports selecting up to five campaigns at once. Selecting at least one campaign is required before running the job to create contacts. |
| Create Attendees as Contacts | Use this button to start Contact creation for Attendees of a Ticketed Event campaign. If the GoFundMe Pro Related Entity does not have a lookup to the GoFundMe Pro Member field (Attendee Contact), this job will use the First Name, Last Name, and Email from the GoFundMe Pro Related Entity to either find an existing Contact or create a new one. Note: This will not update a Contact if one is set on the GoFundMe Pro Member field already within the GoFundMe Pro Related Entity record. |
Data Processing
Under Data Processing, you can manage settings related to data processing and auto-correction.
Important: Changing the Data Processing settings can cause unexpected results and we recommend reading the descriptions of the different data processing options before adjusting the settings. If you have any questions about these settings, please contact us.
Data Processing Settings
| Setting | Description |
| Enable All Triggers |
Active: All triggers utilized by the Salesforce integration will be enabled and the integration will be process data. Inactive: All triggers utilized by the Salesforce integration will be disabled and the integration will be stopped. |
| Data Process Mode |
Choose between two different modes for data processing: Batch: asynchronous method that processes API Requests 1 by 1 as they come into Salesforce. This is the default method for all organizations when the package is installed. Dynamic Bulkfication: asynchronous method that processes API Requests in bulk, up to 20 records at once, reducing the possibility of data skew and data loss. This method is best for high volumes of data processing and data integrity concerns. Because of its efficiency, bulkification processing will likely add time to records being processed during high volume and, as a result, will slow down the "real-time" sync, but will ultimately ensure data parity with improved data quality. |
| Dynamic Bulkification Batch Size | This field defines the batch size of records to be processed by the integration via Dynamic Bulkification. The default batch size is 10, and the value entered must be between 2 and 20. |
Data Auto Correct Settings
| Setting | Description |
| Retry Data Processing Attempts | This setting determines the number of times a failure will attempt to retry. By default, it is set to 5. |
| Payout Update Retry Attempts | This setting determines the total number of days a failed payout API request will attempt to retry nightly. |
Bidirectional Data Sync Settings
| Setting | Description |
| Activate Bidirectional Syncing |
Active: The integration will sync updates made in Salesforce to records in GoFundMe Pro. Inactive: The integration will NOT sync updates made in Salesforce to records in GoFundMe Pro. |
| Retry failed outbound requests | This setting is part of the bidirectional sync feature and is used to initiate a resync of all outbound API Requests that are in a status of "Awaiting Retry". |
Scheduled Jobs
Under Scheduled Jobs, you can view all active GoFundMe Pro scheduled jobs in your Salesforce instance. Additionally, any job can be rescheduled with the current user.
| Job | Description |
| Reschedule Jobs as User | This button can be used to reschedule all GoFundMe Pro jobs. The jobs will be rescheduled using the user that clicks the button. |
Below are all of the available scheduled jobs that the Salesforce integration uses:
Note : GoFundMe Pro was previously known as Classy, so that name may still appear in custom objects, fields, and labels in Salesforce.
| Setting | Description |
| ClassyDataSyncV2 | Nightly job that will reconcile transactions, campaigns, and fundraising pages between Salesforce and GoFundMe Pro to ensure data integrity between the two systems. This job only searches for missing data from the previous day. |
| ClassyHousekeeping | Nightly job that cleans old system records (for example, GoFundMe Pro Log, GoFundMe Pro API Request, and GoFundMe Pro Bulk Upload objects) based on the Package settings. |
| ClassyRecurringProfileRollupBatch | Nightly job that updates all GoFundMe Pro Recurring Donor rollups. |
| ClassyScheduleApiContactMatching | Runs hourly to link existing Contacts to a GoFundMe Pro Supporter record in Salesforce. |
| ClassyScheduleApiFetchChannelTransactionBatch | Job is scheduled if GoFundMe Pro for Facebook, GoFundMe Pro for Instagram, or GoFundMe Pro for Double the Donation integrations are turned on in the Control Panel Channel Integration settings. Once the setting is on, this job runs once hourly at the 15-minute mark to fetch GoFundMe Pro for Double the Donation, GoFundMe Pro for Facebook, and GoFundMe Pro for Instagram donations that are created as offline donations in GoFundMe Pro. |
Package
Under Package Management, you can manage settings related to your general Salesforce integration configuration. This includes Custom Field Mapping and enabling debugging. Once you make the changes you need, select Save.
| Setting | Description |
| Enable Custom Field Mapping Tool |
Active: All custom mappings created via the Field Mapping tool will be automatically mapped during record creation. Inactive: The Custom Field Mapping tool will be disabled. All custom mappings created via the tool will not map during record creation. |
| Delete API Request Days In Past | For the GoFundMe Pro API Request custom object, all data older than the value set (min: 30) on this field will be deleted on a nightly basis. |
| Delete Bulk Upload Days In Past | For the GoFundMe Pro Bulk Upload custom object, all data older than the value set (min: 30) on this field will be deleted on a nightly basis. |
| Enable Debugging with GoFundMe Pro Log |
Active: Exceptions and debugging data will be recorded in the GoFundMe Pro Log custom object. Inactive: Exceptions and debugging data will not be recorded in the GoFundMe Pro Log custom object. |
| Delete GoFundMe Pro Log Days In Past | For the GoFundMe Pro Log custom object, all data older than the value set on this field will be deleted on a nightly basis. |
NPSP
Under NPSP settings, you can manage settings related to your NPSP extension. Once you make the changes you need, select Save.
Note: If you do not have the NPSP extension this option will not appear. You can learn more about setting up the extension with our installation guide.
| Setting | Description |
| Create & Update NPSP Recurring Donations |
Active: When new GoFundMe Pro Recurring Donors are created, NPSP Recurring Donation records will be created. Any subsequent transactions associated with a recurring donation in GoFundMe Pro will create a Recurring Donation record if one does not already exist. Inactive: The Salesforce integration will not create, nor update, NPSP Recurring Donations. |
| Create & Update NPSP GAU Allocations |
Active: All Campaigns, Recurring Donations, and Opportunities created via GoFundMe Pro will create an NPSP GAU Allocation record. Opportunities receive their Primary Campaign Source’s GAU Allocation. Inactive: The Salesforce integration will not create, nor update, GAU Allocations. |
| Set Default GAU |
Allows an organization to associate an existing GAU with all new GoFundMe Pro Designations. The value for this setting must be an existing GAU’s Salesforce ID. If left blank, a new GAU will be created for each Designation. |
| Create & Update NPSP GAUs |
Active: The Salesforce integration will create and update GAUs. Inactive: The Salesforce integration will not create, nor update, GAUs. |
| Use Classy Opportunity Name on Resync |
Active: Any updates to a GoFundMe Pro transaction will use the Classy Opportunity naming convention. Inactive: All Opportunity creations and updates will honor the NPSP naming convention. For that reason, we recommend that this setting remain disabled. |
| Pledged opportunity stage name | Select the StageName your organization uses for future opportunity installments with Recurring Donations. Setting the StageName here will allow the NPSP extension to identify and remove the correct installments each month. If no StageName is selected, the default value will be Pledged. If the incorrect StageName is selected, the integration will not be able to correctly remove the future installment Opportunities associated with the NPSP Recurring Donation record. |
| Create and Update Payments | When this is turned on, payment records will be created and updated through the GoFundMe Pro integration. If you use the Automatic Payment Creation setting in NPSP, we recommend the Opportunity record type used by the integration is excluded from automatic payment creation. |
| Refunded Opportunity Stage Name | If the Create and Update Payments setting is on, you can set a custom stage name for opportunities that reflect a refunded transaction in GoFundMe Pro. |
Channel Integrations
Under Channel Integrations, you can manage settings related to other integrations that sync to Salesforce. Once you make the changes you need, select Save.
You will need an active Facebook integration subscription in order to enable and use these features. If you do not have a Facebook integration subscription, contact us.
If you have a subscription and need help setting it up, follow our instructions on getting started.
GoFundMe Pro for Facebook
| Setting | Description |
| Enable GoFundMe Pro For Facebook Sync |
Active: Facebook Channel Transactions will be synced to Salesforce in 15 min intervals. The APEX job ClassyScheduleApiFetchChannelTransactionBatch is scheduled in your Salesforce instance. Inactive: The integration will stop but all existing data synced will remain in Salesforce. The APEX job ClassyScheduleApiFetchChannelTransactionBatch is deleted from your Salesforce instance. |
| Last Job Sync | This shows the timestamp of the last Facebook sync. Updated after every successful sync. |
| Do not sync before this date | Any facebook transactions with a created date before this date will not be synced to salesforce. |
| Bucket Account Name Facebook | When a contact cannot be created this bucket account will be used as the account attached to the opportunity. If a contact is created the opportunity Account Id will be replaced with the contact Account Id. |
| Contact Creation Options |
Facebook users are in control of what donor information is available to any integrations. Only 2% of facebook users provide their email address. Donor information on a transaction is only made available to integrations 2-3 days after the transaction date. Once available we will create contacts according to this setting. Options are:
|
GoFundMe Pro for Instagram
| Setting | Description |
|
Enable GoFundMe Pro For Instagram Sync
|
Active: Instagram Channel Transactions will be synced to Salesforce in 15 min intervals. The APEX job ClassyScheduleApiFetchChannelTransactionBatch is scheduled in your Salesforce instance. Inactive: The integration will stop but all existing data synced will remain in Salesforce. The APEX job ClassyScheduleApiFetchChannelTransactionBatch is deleted from your Salesforce instance. |
| Last Job Sync | This shows the timestamp of the last Instagram sync. Updated after every successful sync. |
| Do not sync before this date | Any Instagram transactions with a created date before this date will not be synced to salesforce. |
| Bucket Account Name Instagram | When a contact cannot be created this bucket account will be used as the account attached to the opportunity. If a contact is created the opportunity Account Id will be replaced with the contact Account Id. |
| Contact Creation Options |
Instagram users are in control of what donor information is available to any integrations. Only 2% of Instagram users provide their email address. Donor information on a transaction is only made available to integrations 2-3 days after the transaction date. Once available we will create contacts according to this setting. Options are:
|
GoFundMe Pro for Double the Donation
| Setting | Description |
| Enable GoFundMe Pro For Double the Donation Sync |
Active: Double the Donation Channel Transactions will be synced to Salesforce in 15 min intervals. The APEX job ClassyScheduleApiFetchChannelTransactionBatch is scheduled in your Salesforce instance. Inactive: The integration will stop but all existing data synced will remain in Salesforce. The APEX job ClassyScheduleApiFetchChannelTransactionBatch is deleted from your Salesforce instance. |
| Last Job Sync | This shows the timestamp of the last GoFundMe Pro for Double the Donation sync. Updated after every successful sync. |
| Do not sync before this date | Any Double the Donation transactions with a created date before this date will not be synced to salesforce. |
| Bucket Account Name Double the Donation | When a contact cannot be created this bucket account will be used as the account attached to the opportunity. If a contact is created the opportunity Account Id will be replaced with the contact Account Id. |
Frequently asked questions
Are changes to settings retroactive?
No, they are not retroactive. Changes only apply to new or updated records.