An email address property is required to complete the setup below. If you are not currently sending email addresses into Heap as a property, use the addUserProperties API to set this up. If you cannot send email addresses into Heap for data privacy reasons and are planning to use the Salesforce integration to conduct account-based analysis, review Measuring Account Health for steps to set up account-based analysis manually.
Our Salesforce integration allows you to import any built-in or custom fields on your Salesforce account and contact objects. These will map to accounts and users in Heap, respectively.
The Salesforce integration is currently not bi-directional. Data from Heap cannot be sent into Salesforce via this integration.
To set up our Salesforce Integration, navigate to Capture > Sources > Salesforce. On this page, click the ‘Connect’ button.
You will be redirected to log in with your Salesforce account and add Heap as an authorized client. Note that you must be a Salesforce admin to complete this step.
Once the authorization is approved, you’ll be redirected back to the Heap Salesforce page, where you can start adding contact and account properties to use in your analysis.
It may take up to several hours to import new Salesforce fields into Heap.
After the first sync, each time you add new properties, we’ll import that property for all contacts and accounts that have been active in Salesforce for 1 year prior to the day you set up the integration. Activeness is measured by the last update time of the contact and account record.
In the event that someone on your team deletes or renames a property in Salesforce that has already been imported into Heap, we will no longer sync data from that property or display it on the configuration page. However, you may still see the old property when running analysis queries. For assistance, reach out to email@example.com.
If you require a more complex import of Salesforce information, reach out to your Account Manager or to firstname.lastname@example.org.
Frequently Asked Questions
Does this integration work with Salesforce sandboxes?
No, unfortunately, you cannot connect a Salesforce sandbox using this integration.
How many API credits with the integration consume?
Our integration runs hourly and uses 2 credits to query the account and contact objects to check for changes, and then use 1 additional credit for every 2000 record changes within that hour. We impose a daily limit of using no more than 10,000 credits per day, though we almost never hit this limit.
We would like to create a new user to run this integration. What are the minimum permissions the SFDC user needs to have for the integration to work properly?
You can create a permission set with read and view all permissions for Contacts and Account objects, read permissions for all Contact and Account fields, and “API Enabled” under system permissions.
What if our Contact to Account relationship is not 1:1 (i.e. one Contact could belong to more than one Account)?
Heap will only maintain a 1:1 relationship between Contact and Accounts. This means the user in Heap connected to the Contact will be assigned the most recently updated Account.