You can set up Salesforce Integration from the Dashboard Integration page.

3. Once entered, you will be redirected to Salesforce to authorize Gradual's access.

4. Once authorized, you will be redirected back to Gradual to set up the object mappings.

From the Object Mapping setup page, you can easily set up the Gradual object to the Standard Salesforce Object mapping.

Currently, Gradual supports mapping:

Gradual Members --> Salesforce Contacts OR Leads

Gradual Events --> Salesforce Campaigns

Gradual Event Attendees --> Salesforce Campaign Members

You can choose to map members to either Leads or Contacts in Salesforce. Choose which field you want to use to match objects. We recommend using email for this mapping as it is most common. However, you can map based on another field like Gradual UserId, but note that you will need to ensure that an appropriate corresponding field exists on the Salesforce record like "Gradual UserId" and that data will need to be backfilled into your Salesforce org for existing users for the match to be successful.

If we do not find a matching record based on the matching criteria, you can choose to create a new record.

If Gradual creates the record, you can also use field mappings to send fixed values to Salesforce fields in the Members mapping section. For example, you may choose to map Lead Source to a constant value instead of relying only on a Gradual field.

Once configured you can set up field mappings for the remaining available Gradual user fields:

In the Members data mapping section, you can map a constant value to a Salesforce field instead of a default Gradual field.

To do this:

This is helpful when you want Gradual to always send the same data to Salesforce for a specific field, such as setting Lead Source to Community Event and Lead Source Detail to 'Gradual' or a specific event.

A few important notes about constant values:

For each field you can decide if you want Gradual to update the data or just reference based on the Update Policy.

Data Mapped from Gradual Users to Salesforce Contacts or Leads:

You can also sync onboarding question responses from Gradual to Salesforce.

Onboarding questions sync to a single custom field on the Salesforce Contact object: GradualOnboardingQuestion__c. This field stores onboarding question and answer pairs as JSON.

Before enabling this sync, create the GradualOnboardingQuestion__c custom field in Salesforce. When onboarding question sync is enabled for the first time, Gradual will display a confirmation message reminding you to create this field first.

Supported answer formats include:

If an onboarding question is deleted in Gradual, that question will be removed from the JSON on the next sync for that member update.

You are able to set up member profile data to sync one way or both ways with Salesforce. Select the appropriate arrows to have data sync from Gradual to Salesforce, from Salesforce to Gradual, or in both directions.

For onboarding question sync:

Conflict resolution options for onboarding question sync are:

Constant value mappings are only supported for one-way sync from Gradual to Salesforce.

Gradual will create new SFDC campaigns and map the registrants for that event as campaign members. The mapping is set up similarly to the member mapping.

First, choose which field you want to use to match objects. If your event names may change or you have a specific syntax you use for campaign names in SFDC, we recommend using the Gradual EventID as your matching value. You'll need to create a matching field on your Campaign record in Salesforce called Gradual EventID. This will ensure that even if the event name changes in Gradual or the campaign name changes in Salesforce, the link will remain and not be broken.

Then you can choose what other data you wish to map to the SFDC campaign.

Data Mapped from Gradual Events to Salesforce Campaigns:

if the "Map event attendee to Campaign Member" option is selected. Users who register for events will be mapped as campaign members.

We also support syncing all Gradual activities to Salesforce custom objects.

Regardless of the method used to create the Gradual Activity object, we will sync the following data to that object:

Below are the events that Gradual will sync to the new Gradual Activity custom object in Salesforce once the GradualActivity sync is enabled.

There are two methods to create and connect the Gradual Activity custom object.

The first is using our installed package available via here.

This will install the custom object as an app in your SFDC org. Based on whether or not you've selected mapping members to leads or contacts will determine whether the Gradual Activity custom object is related to the lead or contact.

The other method is to create the custom object manually using the instructions below.

In order to enable this mapping, you first need to set up a custom object in Salesforce.

Please name the object GradualActivity and do not change the default API name, which should be GradualActivity__c.

Once the custom object is created, please add the fields exactly as shown in the below image:

Once the Gradual Activity Object is created via either method above, you can enable the GradualActivity mapping in the dashboard and we will sync data from Gradual to Salesforce periodically(Every 10 minutes).

You have the ability to sync forum posts to cases inside of Salesforce. Once enabled in the integration settings, admins and forum moderators will see the option to sync forum posts to salesforce in the post settings.

Below is the data that will sync over to the Salesforce Case

The Salesforce integration includes an Error Logs page to help admins review connection, sync, and API limit issues.

The following error categories are included:

Examples of errors that may appear in this log include connection failures, Salesforce permission errors, source of truth conflicts, lookup policy skips, missing Salesforce fields or objects, field type mismatches, duplicate rule rejections, record lock errors, flow trigger failures, invalid onboarding question JSON, required field errors, and API rate limit pauses.

​