You are here:
Considerations for Disabling Contacts in an Einstein Activity Capture Configuration
You can prevent contact data from being used by Einstein Activity Capture. Make sure that you understand the effects of disabling contacts.
Required Editions
| Available in: Lightning Experience |
| Available with Einstein Activity Capture Standard in Sales in Starter, Pro Suite, Professional, and Enterprise Editions |
| Available with Unlimited Edition, Einstein 1 Sales Edition, and Agentforce 1 Edition |
| Available with Einstein for Sales, which is included in Einstein 1 Sales Edition and available for an extra cost in Enterprise and Unlimited Editions |
| Available with Sales Engagement, which is included with Sales in Performance and Unlimited Editions, and available for an extra cost in Professional and Enterprise Editions |
| Available with Revenue Intelligence, which is available for an extra cost in Enterprise and Unlimited Editions |
Note We’re reorganizing the Einstein Activity Capture documentation. We’re
moving some information around, but we aren’t deleting anything.
Note By 2025, all Einstein Activity Capture services will fully
migrate to Hyperforce, the Salesforce cloud-native infrastructure architecture, built for
the public cloud. Before the migration to Hyperforce, Einstein Activity Capture data was
stored in Salesforce-managed data centers and hosted on AWS within a Virtual Private Cloud
(VPC). After the migration, all Einstein Activity Capture data and services are hosted on
Hyperforce in the same region.
- To stop users’ contact data from moving between Salesforce and the connected account in all directions, add them to an Einstein Activity Capture configuration with contacts disabled.
- When you disable contacts, here’s what happens to contacts.
- Contact data isn’t synced between Salesforce and the connected account.
- Contact records aren’t created in Salesforce.
- Contact data isn’t available to Einstein features, such as Email Insights and Recommended Connections.
- Contact data isn’t stored on Hyperforce or Amazon Web Services (AWS). Previously captured contact data remains on Hyperforce and AWS.
- If a user is capturing contact data with more than one email account and is in a contact-disabled configuration, contacts from all their accounts stop being captured.
- If you re-enable contacts, we don’t go back and capture contacts from the time when contacts were disabled. We sync new and updated contacts.
Did this article solve your issue?
Let us know so we can improve!
