Posted in: CRM Success, Integration
Sales teams need email and calendar activity in Salesforce, but few users want more manual data entry. That creates a difficult choice for administrators: automate activity capture without weakening data quality, reporting, security, or compliance.
A successful Einstein Activity Capture (EAC) setup requires more than enabling a feature. You need to confirm prerequisites, establish governance rules, test real workflows, and monitor the results. This guide covers each setup step, common implementation problems, and the limitations to evaluate before deploying Einstein Activity Capture across your organization.
What Does Einstein Activity Capture Do?
Einstein Activity Capture connects supported email and calendar accounts with Salesforce. Depending on your configuration, it can capture email activity and sync calendar or contact information. It should reduce the amount of work required from sales representatives, but this isn’t always the case.
These functions are related but distinct:
- Email capture makes relevant email activity visible within Salesforce.
- Event sync moves calendar information between connected systems according to configured rules.
- Contact sync keeps supported contact data aligned.
Visibility, storage, retention, reporting, and synchronization options can vary by Salesforce edition, license, configuration, and current product policy. Before deployment, verify technical requirements and behavior against the latest Salesforce documentation. This review is particularly important if captured activities must support standard Salesforce reporting, automation, security policies, or regulatory obligations.
Prerequisites Before Setting Up Einstein Activity Capture
Before setting up Einstein Activity Capture, confirm that your Salesforce environment, email service, users, and internal policies support the planned implementation.
Use this preflight checklist:
- Confirm that your Salesforce edition and licenses support the required capabilities.
- Identify the current permissions and access controls required for administrators and users.
- Verify that your Microsoft 365 or Google environment is supported.
- Confirm that pilot users have active, compatible email and calendar accounts.
- Review identity, authentication, consent, and OAuth requirements.
- Obtain security and compliance approval for the intended data flow.
- Define which users, teams, and workflows will enter the pilot.
- Document ownership for configuration, support, and post-launch monitoring.
Include the Salesforce administrator, IT, security, compliance, sales operations, and representative pilot users in planning. Each group sees different risks.
Review Data Storage, Retention, Reporting, and Compliance
Resolve data-governance questions before activation, not after users begin capturing customer communications.
You should confirm:
- Where captured information is stored
- How long it remains available
- Which activities support required Salesforce reporting and automation
- Who can view captured communications
- How confidential, personal, or irrelevant messages are excluded
- Whether retention behavior aligns with corporate policies
- How disconnected users and deleted accounts are handled
- Who reviews and updates capture rules
Security-conscious and regulated organizations should document these decisions and obtain approval from the appropriate stakeholders. Capabilities change across releases. Since Spring ’26, captured emails sync as standard Salesforce activity records that count toward data storage, and Summer ’26 retired Activity 360 Reporting, Activity Metrics, and the Activities Dashboard. Avoid assumptions from older implementations.
How to Set Up Einstein Activity Capture
The setup has three core parts: enable the feature and assign permissions, connect supported accounts, and configure capture and synchronization. A fourth step, testing, determines whether the configuration works as intended. Let’s look at each step.
1. Enable Einstein Activity Capture and Assign Permissions
In Salesforce Setup, locate the current Einstein Activity Capture settings using Setup search. Review any displayed prerequisites, then enable the required functionality if it is not already active.
Next, assign the current permission sets or access controls required for:
- Administrators managing the configuration
- Users connecting their email and calendar accounts
- Stakeholders reviewing captured activity where appropriate
Follow least-privilege principles: grant only the access each role needs. Every user also needs an active configuration assignment; since May 2026, unassigned users lose EAC access.
Salesforce changes interface labels over time, so verify names against current documentation. For internal instructions, include a sanitized screenshot of the relevant Setup page.
2. Connect Microsoft 365 or Google Accounts
Select your email service. Setup may involve organization-level authorization, individual user authentication, or both. Pre-Spring ’26 Microsoft 365 connections must be upgraded to Microsoft Graph; Salesforce required the upgrade by October 1, 2026.
Coordinate with IT to review:
- Administrative consent requirements
- OAuth policies and approved applications
- Identity-provider restrictions
- Service-account considerations
- Access to both email and calendar data
- Policies that could block or revoke connections
Users may need to authenticate their individual accounts and approve the requested access. A successful sign-in confirms connectivity, not correct capture, matching, synchronization, or privacy behavior. Deploying immediately can spread configuration errors, create inaccurate CRM data, expose unintended communications, and increase cleanup.
Start with a small, representative pilot group. Verify connection status, expected captures and exclusions, record associations, and synchronization. Document and resolve identity or consent errors before expanding access. Include a sanitized screenshot of a healthy connection in administrator guidance.
3. Configure Email Capture and Calendar Synchronization
Create or edit the relevant configuration, assign pilot users, and select the available email capture, event synchronization, and contact synchronization options. Review synchronization direction, default behavior, record association, and the operational effect of every setting before activation.
Do not enable every option simply because it is available. Align the configuration with your data-quality and pipeline-visibility goals.
| Approach | Appropriate When | Primary Evaluation Point |
|---|---|---|
| Selective capture | Users need control over which communications enter Salesforce | User effort and capture consistency |
| Broader automation | The organization values comprehensive activity visibility | Record-matching accuracy and irrelevant data |
| Manual control | Sensitive workflows require deliberate record selection | CRM adoption and administrative burden |
Test how activities associate with contacts, accounts, opportunities, and other relevant records. Incorrect associations can turn Salesforce activity data into noise. Document which behavior users should expect, where they retain control, and how they should report an inaccurate match.
Define Exclusions and Privacy Controls Before Activation
Define what should not be captured before enabling the pilot. Depending on current product capabilities, exclusions may address:
- Internal email addresses or domains
- Personal or nonbusiness communications
- Confidential customers and accounts
- Legal, human resources, or executive correspondence
- Automated notifications and irrelevant system messages
- Other communications restricted by company policy
Exclusions reduce unwanted CRM data and limit unintended visibility, but they require realistic testing. Send approved test messages that should be captured and others that should remain excluded. Confirm the results from multiple user perspectives.
Assign an owner to review exclusions as domains, teams, and policies change. Document each rule, its purpose, and its approval history. Exact privacy controls depend on your Salesforce configuration and current Einstein Activity Capture capabilities.
4. Test the Einstein Activity Capture Setup
A pilot should prove expected captures and expected non-captures. Build an acceptance-test matrix covering:
- Inbound and outbound email
- New, updated, canceled, and recurring meetings
- Excluded addresses, domains, and scenarios
- Correct and incorrect record-matching conditions
- Visibility for different user roles
- Disconnected or expired accounts
- Available reporting and workflow requirements
- Synchronization timing and duplicate prevention
Define measurable success criteria. Activities should associate with the intended records, remain visible only to appropriate users, synchronize within an acceptable timeframe, and support required reporting. The process should also be understandable to end users.
Document every result, unresolved exception, and configuration change. Do not expand beyond the pilot until stakeholders approve the outcome. This validation protects data quality while exposing user experience, security, and compliance concerns before they affect the wider organization.
Troubleshooting Common Einstein Activity Capture Setup Issues
When testing fails, start with the symptom and check the simplest configuration or connection issue first.
| Symptom | Likely Cause | Next Check |
|---|---|---|
| Missing activity | User is unassigned, disconnected, or excluded | Configuration assignment, authentication status, and exclusion rules |
| Incorrect record association | Matching behavior does not fit the workflow | Email-matching flow, related records, and test scenarios |
| Delayed synchronization | Connection or service delay | Account status and Salesforce service information |
| Failed account connection | OAuth, consent, or identity restriction | Email-service policies and administrator approval |
| Permission error | Missing or incorrect access | Current permission sets and user access controls |
| Duplicate calendar entries | Conflicting synchronization behavior | Direction settings and other connected tools |
| Unexpected captured communication | Exclusion or privacy rule is incomplete | Address, domain, and configuration settings |
Retest after one controlled change at a time. If the issue persists, collect configuration details and sanitized examples before escalating. Do not use confidential customer data for troubleshooting.
When Einstein Activity Capture May Not Meet Your Requirements
Einstein Activity Capture may suit organizations that want broader automation and can work within its available configuration, matching, storage, and retention model. It may be less suitable when teams require user-controlled record selection, predictable Salesforce data storage use, stricter privacy controls, or a different end-user workflow.
Evaluate these questions:
- Can users control which Salesforce record receives an activity?
- Can captured data support required reporting and automation?
- Do retention and storage practices meet internal policies?
- Can the organization prevent sensitive communications from being captured?
- Does the workflow encourage CRM adoption without sacrificing accuracy?
- Can administrators configure capture around complex business requirements?
If the answers expose gaps, review Einstein Activity Capture limitations and consider an alternative email-to-Salesforce integration.
LinkPoint Connect from LinkPoint360 provides one-click email recording, configurable synchronization, Automatic Activity Capture, and real-time CRM data within email.
Your Next Steps After Einstein Activity Capture Setup
Complete your Einstein Activity Capture setup in a controlled sequence: verify requirements, approve governance rules, configure a pilot, test realistic workflows, and train users. After launch, monitor data quality and schedule recurring reviews of record-association accuracy, reporting, security, user adoption, and disconnected accounts.
For a more flexible approach to email and calendar integration, request a free LinkPoint360 demo. We can discuss your Salesforce configuration, capture requirements, reporting needs, and end-user workflow.
