Sync your Salesforce data to Clearbit
The Salesforce data connector allows you to create dynamic Company and Person segments based on Lead, Contact, Account, and Opportunity records.
The data connector syncs your Salesforce data through a simple user-level authentication, and takes only a few clicks to implement.
- Choose (or create) a Salesforce integration user
- Define your object and field-level permissions
- Authenticate with Salesforce
After authenticating, the sync will begin immediately.
However, it may take up to a few hours for all of your data to sync, depending on the number of records in your Salesforce org.
After the initial sync is complete, your Salesforce data will update every 4 hours. For real-time insight into your sales records, we recommend referencing Salesforce directly.
1. Choose (or create) a Salesforce integration user
Because the Salesforce data is accessed at the user level, it is important that the user you choose has the appropriate permission levels.
What's an Integration User? We strongly recommend choosing (or creating) a Salesforce Integration User for the sync. Integration Users ensure that if an actual user leaves your organization, you'll always have a user with the correct permissions available.
Integration User Requirements
- Read access to Salesforce Users, Accounts, Opportunities, Contacts, and Leads
- Read access to all fields that you wish to sync to Clearbit
- API Enabled administrative permissions
2. Define your object and field-level permissions
The Salesforce data connector gives you the flexibility to decide which Salesforce objects, records, and fields you would like to sync with Clearbit.
a. Sync all Objects, Records, and Fields
If you would like to sync all of you Salesforce data to Clearbit, make sure your Integration User has read permissions for all of the following objects (and fields on those objects):
b. Set up a selective sync
Clearbit will only sync objects, records, and fields that the authenticated user has permission to read.
To restrict specific data from being synced and displayed in Clearbit, define your Salesforce profiles and permission sets to restrict the authenticated user's read access to those objects, records, and/or fields.
How do I restrict permissions to certain records? Check out Salesforce Trailhead for instruction on controlling access to objects, fields, and records.
3. Authenticate with Salesforce
- Log in to Clearbit X.
- Navigate to the configuration page and open the Salesforce connection settings.
- Choose the Salesforce environment you would like to connect
- Production - your live production environment.
- Sandbox - typically a partial or full replica of your production account, used to test new configurations and settings before deploying to your live environment.
- Log into Salesforce using your Integration User (or the non-integration user you have chosen)
Having trouble syncing? Make sure the user that you are using to authenticate with Salesforce has the box labeled API Enabled checked (you can find it in Administrative Permissions). Without API permissions, the sync with Clearbit will fail.
After authenticating, the sync will begin immediately. However, it may take up to a few hours for all of your data to sync, depending on the number of records in your Salesforce org.
After the initial sync is complete, your Salesforce data will update every 4 hours.
A note about security
We take data security very seriously, especially when it comes to your Salesforce data. Head to our security policy for more information.
Frequently Asked Questions
Q: What if I only want to sync certain fields over to Clearbit X?
A: Many customers choose to create an Integrations User within SFDC with limited permissions, since the connector will only get access to those fields which that user account has access to. This allows you to mitigate any field-level security concerns. We would suggest using permission sets and profiles within SFDC.
Q: Will this have a material impact on my API calls?
A: Salesforce's bulk API generally allows for 150M records to be read/updated daily, which is plenty of space for many organizations. However, if you are concerned about API usage, you can utilize sharing rules to specify which records your SFDC user has access to.