Salesforce is a cloud-based CRM platform.
We pull all the underlying data from Salesforce (SFDC) into a SQL-enabled environment to allow you to get a more in-depth analysis of your CRM data.
|Capture Deletes||check||Only for replicateable objects|
|Data Blocking||check||Column level, table level, and schema level|
|Re-sync||check||Table level and connector level|
|dbt Package||check||Get the package|
|Service Cloud||Including Salesforce Knowledge|
|Marketing Cloud||Using our Marketing Cloud Connector|
|Engagement||Using our Heroku Postgres or Heroku Kafka connectors|
|Industries||Industry-specific like finance and healthcare|
Follow our step-by-step Salesforce setup guide to connect Salesforce with your destination using Fivetran connectors.
The number of API calls that we use varies from company to company. Fivetran has optimized our Salesforce connector to use the fewest possible API calls necessary. In practice, customers find that Fivetran is not a significant API consumer.
Rolling API quota
Each Salesforce account has a rolling 24 hour API quota. Fivetran automatically reschedules for one hour later anytime 90% of the Salesforce API call quota has been consumed. This ensures there is always sufficient API quota for other business-critical applications.
Monitoring the API usage
The system table FIVETRAN_API_CALL tracks information about API calls that are made to sync the data into the warehouse.
REST and BULK API usage
We use both the REST API and the Bulk API to sync your Salesforce data, the Bulk API only for the historical syncs and the REST API for the incremental syncs. We select the sync strategy depending on the data size and the number of updated records since the last sync. We use multiple techniques to minimize the total number of API calls, specifically the Bulk API calls, because Salesforce limits the number of Bulk API calls.
We disable formula fields by default. However, we can enable them at your request. Be warned — formula fields can cause subtle problems in your data. Before you decide to enable formula fields, read our detailed documentation about formula fields and lookup fields
Salesforce Field History Trackinglink
Salesforce has native functionality that lets you define specific fields for which you want to track history. This functionality is distinct from Fivetran’s history mode. Read our blog post comparing Fivetran history mode to the alternatives to learn if Salesforce field tracking or Fivetran history mode is better for your analytical needs.
If you decide to use Salesforce field history tracking to track and capture all the changes that occur for selected fields, you need to enable it within Salesforce. Enabling field history tracking in Salesforce will create additional tables inside of Salesforce that track all changes for the field.
Fivetran will then import these tables as separate tables during incremental updates. To learn how to enable field history tracking, see the Salesforce Field History Tracking documentation.
IMPORTANT: We have disabled Fivetran history mode for native Salesforce history objects associated with standard objects. The standard objects follow the naming pattern
_StandardObjectName_Historyand are listed in Salesforce's StandardObjectNameHistory documentation.
We do not capture hard deletes for History tables but use the
is_deleted field from Salesforce to capture deletes.
Fivetran follows a one-to-one mapping with all tables in Salesforce. If you can't find something that you're looking for, your Salesforce user may have limited access to the information. Fivetran tries to grab all possible objects, except formula fields.
This schema diagram illustrates how tables relate to one another. It is not a complete Entity Relationship Diagram. It shows relationships for some central entities and workflows. Many standard and all custom entities that are delivered by the Fivetran connector are omitted for brevity.
We also offer you information about the connector from the
fivetran_audit table and the Fivetran