Salesforce Einstein Activity Capture is designed to reduce manual logging, but the feature only helps if the team understands what it captures and what it leaves out. The value is convenience; the trade-off is that it is not a full replacement for structured CRM activity management.
Salesforce Einstein Activity Capture (EAC) is Salesforce’s built-in feature for automatically syncing email and calendar activity from Gmail and Microsoft 365 to Salesforce — without requiring reps to manually log interactions. For Salesforce admins evaluating their activity logging options, EAC appears to be the obvious choice: it’s included with certain Salesforce editions and eliminates manual email logging. But EAC has significant architectural limitations that aren’t obvious from the product description, and the data it captures has important constraints that affect how it can be used in reporting, forecasting, and AI features like Einstein Relationship Insights. This guide covers what EAC actually does, what it costs, and what its limitations mean for your Salesforce implementation.
That distinction matters when teams look at the pricing and the reporting impact. If the capture layer is not aligned with how the business measures activity, it can create confusion instead of clarity.
EAC Capabilities and Limitations
| Capability | EAC Behaviour | Alternative (Salesforce Inbox / Third-Party) |
|---|---|---|
| Email sync to Salesforce | Syncs emails bidirectionally between Gmail/M365 and Salesforce activity timeline | Full native email logging with subject, body, and metadata |
| Calendar sync | Syncs meetings and calendar events from Gmail/M365 to Salesforce activities | Same via Salesforce Inbox or Outlook/Gmail Add-ins |
| Email storage | Emails NOT stored in Salesforce — stored in AWS S3 (off-platform) | Salesforce Inbox stores email content directly in Salesforce |
| Data access for reporting | EAC data is NOT accessible in Salesforce reports, flows, or SOQL queries | Native Salesforce activity records are reportable and queryable |
| AI data availability | EAC data feeds Einstein but is NOT available in custom AI/ML features | Inbox data is fully accessible for custom AI/ML use cases |
| Data retention | 6-month rolling retention — EAC data older than 6 months is permanently deleted | Salesforce Inbox data follows your Salesforce data retention settings (typically unlimited) |
| Cost | Included with Sales Cloud and Service Cloud (certain tiers) | Salesforce Inbox: $25/user/month add-on for basic tiers |
What “Activity Capture” Actually Means
Einstein Activity Capture does not create standard Salesforce Task or Event records from emails and calendar events. Instead, it creates a separate data structure stored outside of Salesforce’s core data model, in AWS infrastructure maintained by Salesforce. This architectural decision — made to enable high-volume sync without consuming Salesforce storage — has several downstream consequences that admins need to understand:
Reports don’t include EAC data: Standard Salesforce reports (Activities, Task History, Email Activity) do not include data captured by EAC. If a rep has 50 emails logged via EAC, those 50 emails won’t appear in an “Emails by Rep This Week” report. The report will show 0. This is a significant limitation for any organisation that uses activity data for performance management, coaching, or attribution.
Flows and workflows can’t use EAC data: You cannot trigger a Salesforce Flow or Process Builder workflow based on an EAC-synced email. If your automation is supposed to fire when a contact receives an email, EAC won’t trigger it — only manually logged emails (Tasks) or Salesforce Inbox emails will.
SOQL queries can’t access EAC data: Developers and admins querying Salesforce data via SOQL (Salesforce’s query language) will not find EAC data in the Task or EmailMessage objects. This affects any custom application, integration, or data export that relies on Salesforce’s data model.
6-month data retention: EAC data is automatically deleted after 6 months. For organisations that need long-term activity history for relationship management, account handoffs, or historical analysis, this is a critical limitation. Activity data from a customer relationship 12 months ago will not be visible in EAC.
EAC Pricing and Edition Availability
Einstein Activity Capture is included with Sales Cloud Enterprise and above, Service Cloud Enterprise and above, and Salesforce Platform (various). It is NOT included with Sales Cloud Professional or Starter. Customers on lower tiers who want automated email logging must use the Gmail or Outlook integration with manual log tracking, or purchase Salesforce Inbox ($25/user/month) which creates proper native Task records.
When EAC Is Appropriate
EAC works well when: (1) you need basic activity visibility on the contact timeline without requiring reportable data, (2) you’re using EAC as a user experience feature — reps can see their email history without logging to CRM — rather than a data capture feature, and (3) your organisation does not use Salesforce Reports or Flows for activity-based analysis or automation. EAC provides genuine value in these use cases at no incremental cost.
EAC is the wrong choice when: you need activity data in Salesforce reports (performance management, attribution analysis), you use Flows or automations triggered by email activity, you need activity history beyond 6 months, or you’re using Salesforce data in downstream BI or analytics tools that rely on native Salesforce objects.
Alternatives to EAC
Salesforce Inbox: Creates proper Salesforce Task records from emails — these are reportable, queryable, and can trigger automations. Costs $25/user/month. Best for organisations that need full activity reporting from email data.
Gong or Chorus: Call intelligence platforms that log calls as Salesforce Activity records automatically. These platforms also provide meeting summaries, call recordings, and coaching features. If activity logging for calls and meetings is the priority, Gong and Chorus provide higher-quality activity data than EAC for those interaction types.
Third-party email integration tools: Tools like Ebsta or Troops create native Salesforce Task records from Gmail and Outlook activity, providing the reportable data that EAC’s architecture doesn’t support.
The most useful setups are the ones that stay understandable a few months later. If the logic behind a feature no longer matches the team’s process, the implementation is probably too complicated.
Common Problems and Fixes
“We turned on EAC but activity reports still show zero emails”
This is the most common EAC confusion — expecting EAC to create reportable Task records when it doesn’t. EAC activity is visible on the contact/account/opportunity Activity Timeline section but doesn’t appear in Activity reports. Fix: if you need activity data in Salesforce reports, you cannot use EAC alone. Enable Salesforce Inbox (if budget allows) or switch to a third-party email logging tool that creates native Task records. If the use case is only timeline visibility (not reporting), EAC is functioning correctly — the data is there, just not in a reportable format.
“Our EAC data from last year is gone”
EAC’s 6-month rolling deletion has removed data you needed. This is expected behaviour, not a bug, but it’s frequently discovered after the fact. Going forward: if long-term activity history matters, migrate to Salesforce Inbox or a third-party logging solution that creates native Salesforce records with your standard data retention settings. For data already deleted by EAC, there is no recovery option — the data is permanently removed from AWS storage after the 6-month window.
Common Implementation Challenges to Anticipate
Teams working on Salesforce Einstein Activity Capture frequently run into three recurring obstacles: inadequate stakeholder alignment during planning, underestimated data migration complexity, and insufficient end-user training budget. Addressing all three before go-live dramatically improves adoption rates and time-to-value. Build a project team with representatives from sales, marketing, and IT rather than handing the whole project to one function.
Step-by-Step Fix: Build Your Foundation Before Scaling
Successful EAC implementation follows a consistent pattern: start with a clearly defined use case for a single team, measure the baseline, implement incrementally, and scale only after achieving measurable results in the pilot. Avoid configuring everything at once. A phased approach with 30-day review cycles catches configuration errors before they spread.
Measuring Success: KPIs and Review Cadence
Establish three to five quantifiable success metrics before launch: adoption rate, data completeness score, and process efficiency measured as time saved per rep per week. Review these metrics monthly and tie configuration decisions to data rather than gut feel.
Frequently Asked Questions
What are the key benefits of Salesforce Einstein Activity Capture?
The primary benefits are reduced manual logging burden for reps, better activity visibility on the contact timeline, and automatic calendar sync. Organisations using EAC for its intended purpose — timeline visibility without reporting — see higher rep satisfaction with CRM. Results depend heavily on understanding what EAC does and does not do before deploying it.
How long does EAC implementation typically take?
EAC setup for small teams is typically complete in one to two weeks. The technical configuration is straightforward; the main time investment is training reps on what EAC does, what it doesn’t do, and how to interpret activity data on the timeline. Larger rollouts may take longer depending on user count and change management requirements.
What is the most common reason EAC implementations disappoint?
Admins enable EAC expecting full activity reporting and discover the 6-month retention and non-reportable data constraints only after go-live. Thorough pre-deployment evaluation of what EAC can and cannot do — versus what Salesforce Inbox or third-party tools provide — prevents most of these situations.
How do you calculate ROI from EAC?
Measure time saved on manual email logging (typically 5–15 minutes per rep per day) multiplied by rep headcount and average hourly cost. For timeline visibility use cases, the ROI calculation is straightforward. If you need reportable activity data, factor in the cost of Salesforce Inbox or a third-party tool and compare against the value of that reporting capability.