Here you can find information regarding how API calls between Drift and Salesforce function.

Billing Plan: The Salesforce integration is available on the Premium plan and above.

In this article, we'll cover: 

• How Drift Uses API Calls
• FAQs

How Drift Uses API Calls

Drift uses API calls from SFDC for two main reasons:

• Bulk imports
• Activity exports

The first of these (bulk imports) is a single bulk API request with high volume content upon initial sync of things like accounts, then very minimal on a 24 hour basis as we only import the daily changes.

The latter (activity exports) is highly dependent upon conversation volume. Drift will use an API call to send the completed conversation activity into SFDC for every conversation activity. This makes this API call volume more difficult to predict, but also controllable in certain aspects. For example, not every conversation needs to be sent to SFDC if thresholds are set for CQL scores, conversations with anonymous visitors that don't provide their email won't be sent or attempted, etc.

Sales reports in Drift are run by SOQL queries which falls under the general api request limits and we do not store the data in Drift

FAQs

Q: But what if I'm creating leads in a Marketing Automation Platform? Isn't the CQL controlled there?

A: If leads are sent to MAP then that would be the relevant CQL threshold vs the SFDC CQL threshold. It isn't a perfect science of course, since a lead could still technically exist in SFDC without existing in MAP, but it serves as a reasonable approximation for net new leads generated by Drift as well as ensuring that all the appropriate fields are captured to in Drift before creating a lead in MAP/CRM.