Setup Guide

Set up Salesforce as a destination in RudderStack.

This guide will help you set up Salesforce as a destination in the RudderStack dashboard. It also lists the configuration settings required to correctly send data from the supported sources to Salesforce.

warning

Before you get started, note the following:

  • RudderStack does not support dev instances of Salesforce. See FAQ for more information.
  • (Optional) It is recommended to create a new Salesforce account to use with RudderStack to protect any confidential information in your existing Salesforce account.
  • To give RudderStack the required API permissions, create a new user account in your Salesforce dashboard by going to Setup > Administration Setup > Users > New User and select System Administrator as the profile type.
  • Make sure to turn off two-factor authentication for your Salesforce account so that RudderStack can authenticate successfully.
  • Make sure the Salesforce objects are searchable and fields are creatable before sending events. Otherwise, it can result in errors during event transformation or delivery.

Connection compatibility

Destination info
  • Status: Generally Available
  • Supported sources: Android, iOS , Web, Unity, AMP , Cloud, Warehouse, React Native , Flutter, Cordova
  • Refer to it as SALESFORCE_OAUTH in the Integrations object.

Connection modes
SourceCloud modeDevice modeHybrid mode
AMPsupportednot supportednot supported
Androidsupportednot supportednot supported
Cloudsupportednot supportednot supported
Cordovasupportednot supportednot supported
Fluttersupportednot supportednot supported
iOSsupportednot supportednot supported
React Nativesupportednot supportednot supported
Unitysupportednot supportednot supported
Warehousesupportednot supportednot supported
Websupportednot supportednot supported
Supported message types
SourceIdentifyPageTrackScreenGroupAlias
Cloud mode
Supported sourcessupportednot supportednot supportednot supportednot supportednot supported

Setup

In your RudderStack dashboard, add a source. Then, from the list of destinations, select Salesforce v2.

Connection settings

SettingDescription
Account settingsClick Create Account > Connect with Salesforce v2 and grant RudderStack the necessary permissions to access your Salesforce account.
Map RudderStack properties to Salesforce propertiesThis setting is toggled on by default and lets you map the RudderStack event properties to the corresponding Salesforce fields.
Use contact ID for converted leadsToggle on this setting if both the lead and contact fields are the same.
Consent management settingsSpecify the Consent management provider from the dropdown and enter the corresponding consent category IDs.

See the Consent Management guide for more information on configuring the consent settings.
warning
The Salesforce v2 destination does not support the sandbox mode.

Next steps

FAQ

Which Salesforce Edition should I use to access the API?

Before connecting to the Salesforce API with RudderStack, make sure you are using the right Salesforce edition. You must have either the Enterprise, Unlimited, Developer, or Performance editions to access the API.

See this Salesforce help article for more information.

How do I check the number of Salesforce API calls left for the day?

To check the number of Salesforce API calls, go to Setup > Administration Setup > Company Profile > Company Information. You should then be able to see a field called API Requests, Last 24 Hours, which contains the number of API calls left for the day.

Does RudderStack support dev instances of Salesforce?

No, RudderStack does not support Salesforce dev instances (for example, https://companyabc-dev-ed-develop.lightning.force.com/) currently.

How to fix “No such column ‘X’ on object of type Y” errors?

If event delivery to Salesforce fails due to the non-existence of a provided field - even though the field does exist - check the field-level security settings for that field in Salesforce.

When the field is not marked as visible to the role your RudderStack Salesforce user is using, you will get this error. To fix it, make the field visible to the appropriate role.



Questions? Contact us by email or on Slack