A busy Salesforce activity timeline can still produce an empty sales report. Salesforce Activity Capture reduces manual logging, but reporting depends on how your organization captures, stores, and relates those interactions.
For a SaaS team, that difference affects follow-up reviews, pipeline coverage, and rep coaching. Timeline visibility alone doesn’t prove that an email exists as a reportable Salesforce record.
Start with the storage model, then configure capture around the reports your team needs.
Key Takeaways
- Captured emails aren’t always stored as standard Salesforce records; the email sync configuration matters.
- Standard activity reports need reportable records, appropriate relationships, and user access.
- Validate capture, storage, report inclusion, and visibility separately before using activity counts to evaluate sellers.
Understand What Salesforce Activity Capture Stores
Salesforce calls the product Einstein Activity Capture (EAC). It connects Microsoft or Google accounts with Salesforce and associates email and calendar activity with relevant CRM records.
Captured email can live outside the main Salesforce database
Without Sync Email as Salesforce Activity, captured email resides on Salesforce’s Activity Platform Hyperforce rather than the main Salesforce instance. An email can therefore appear on a record’s timeline without becoming an ordinary activity row in standard reports.
When that feature is enabled, Salesforce syncs emails into the main instance as Task and Email Message records. Those records count toward core storage. Salesforce’s email activity sync release notes describe support for reporting and API access.
Don’t assume enabling the setting converts every historical message. Validate the available history before promising retrospective reporting.
Calendar records need a separate check
Events can sync to the main Salesforce instance as Event records, subject to configuration and retention policies. Confirm that a calendar interaction created a Salesforce Event before expecting it in an activity report.
Manually logged calls and tasks already use Salesforce activity records. However, they still need the correct relationships and report filters.
A timeline answers whether a user can see an interaction. A report also depends on storage, relationships, filters, and access.
Confirm Editions, Licenses, and Permissions
Check Salesforce’s current Einstein Activity Capture documentation before implementation. Edition names, entitlements, and available settings can change.
Verify the organization’s entitlement
Salesforce lists Standard EAC availability with Starter, Pro Suite, Professional, and Enterprise. It separately documents availability for Unlimited, Einstein 1 Sales Edition, and Agentforce 1 Edition. Other licenses and purchased features can affect access.
Its Standard EAC permission-set guidance documents access for 100 users, with Standard Einstein Activity Capture (Additional User) addressing users beyond that allowance. Confirm your organization’s entitlement rather than treating this as a universal limit for every EAC license.
For Microsoft connections, review the authentication method. Salesforce warns about Exchange Web Services retirement in October 2026 and advises upgrading to Microsoft Graph.
Separate setup access from report visibility
Assign eligible pilot users the appropriate EAC permission set. For Standard EAC, use Setup > Permission Sets > Standard Einstein Activity Capture > Manage Assignments.
Keep administrator privileges separate from seller access. Then review object permissions, field-level security, record sharing, and report-folder access.
A permission set doesn’t automatically grant access to every related Account or Opportunity. Test with the seller’s actual permissions, not only an administrator account.
Configure Capture Around Your Reporting Requirements
Use a small pilot before connecting the whole sales team. Salesforce’s official EAC rollout instructions provide the current implementation reference.
The following sequence is a recommended reporting-first approach:
- Create a configuration. In Setup, search for Einstein Activity Capture, then open Settings > Configuration > New Configuration. Name the configuration clearly enough to identify its team and purpose.
- Choose the capture and sync options. Review email, event, and contact settings separately. Where available, enable Sync Email as Salesforce Activity when standard email reporting is required. Confirm calendar sync behavior and direction before saving.
- Set exclusions and sharing. Exclusions prevent designated addresses or domains from contributing captured activity. Sharing controls who can view captured information. Review both against your privacy requirements.
- Assign users and connect accounts. Add the intended pilot users, then have them connect their supported Microsoft or Google accounts. Permission assignment alone doesn’t establish the mailbox connection.
Document each selected option and its business purpose. For example, capturing customer correspondence supports account continuity, while excluding internal communications prevents inflated seller activity counts.
After connection, open Status and Metrics to inspect email and event sync status. Salesforce documents diagnostics for the last seven days, including failure information. This page helps investigate connectivity; it isn’t a sales-performance dashboard.
Don’t promise immediate synchronization. Instead, confirm successful processing before evaluating whether a test interaction reached its intended report.
Build Reports From Verified Salesforce Records
As of October 2026, build new reporting on standard activity report types. Starting Summer ’25, Salesforce stopped making Activity 360 Reporting, Activity Metrics, and Activities Analytics Dashboard available for new setups.
Its September 2026 retirement notice says retired Activity 360 objects and report types stop returning data. Activity Metrics fields also stop populating. Existing legacy configurations aren’t a dependable foundation for new reporting.
Choose the report type by business question
Salesforce recommends standard reports such as Activities with Accounts and Activities with Opportunities. Start with the relationship you need, then inspect the available activity-type and subtype filters.
Use this distinction when planning reports:
| Reporting need | Required foundation |
|---|---|
| Email activity counts | Synced, reportable email activity records |
| Meetings by account | Salesforce Event records with appropriate relationships |
| Calls by seller | Logged call activities and consistent ownership |
| Opportunity engagement | Activities related to the intended Opportunity |
The report type doesn’t create missing relationships. An email visible on a Contact timeline doesn’t automatically qualify for an opportunity-level report.
Define the count before adding a chart
Decide whether you count activity records, distinct customers contacted, or opportunities with qualifying engagement. These answer different questions.
Also distinguish activity owner from opportunity owner. A sales development representative can perform outreach on an account owned by an account executive.
For pipeline reviews, pair activity measures with outcomes such as qualified meetings or stage progression. Raw email volume doesn’t establish buyer interest, and captured correspondence doesn’t automatically establish campaign attribution.
Watch for Reporting Pitfalls That Change the Story
Salesforce documents why captured emails can be missing from expected reporting surfaces. Diagnose the storage path before changing report filters.
Missing rows don’t always mean missing work
A seller can have visible email history while a standard activity report returns no email rows. Check whether email exists only on the capture platform or also as Salesforce records.
Next, inspect date filters, activity types, related records, and permissions. Don’t treat the standard Last Activity field or legacy Activity Metrics fields as complete measures of captured engagement.
An administrator seeing a row that a manager can’t see usually calls for an access review, not a mailbox reconnection.
Extra rows can inflate performance
Manual email logging alongside automatic sync can create duplicate-looking interactions. Calendar updates and inconsistent relationships can also complicate reconciliation.
Inspect the underlying records before assuming a chart measures distinct outreach. A Contact linked to multiple deals requires special care: account-level engagement doesn’t prove that each open Opportunity received meaningful attention.
Likewise, excluding an internal domain changes the expected totals. Record that decision so managers don’t interpret a deliberate exclusion as a capture failure.
Run a Practical Acceptance Test Before Rollout
The following checklist is a recommended validation process, not a claim that Salesforce provides one complete built-in test.
Use controlled accounts and distinguishable messages. Where your environment supports it, test safely outside normal production workflows. Record expected results before checking dashboards.
- Send and receive test emails involving a known Contact. Confirm timeline visibility, then separately verify whether Task and Email Message records exist.
- Create a calendar meeting involving that Contact. Check the resulting Salesforce Event, owner, date, and related records.
- Log a call manually. Confirm that the report includes it once and separates it appropriately from email and meetings.
- Test an excluded address or domain. Verify that capture follows the exclusion policy, without treating this as proof that every copy disappears elsewhere.
- Run account-level and opportunity-level reports. Compare their detail rows with the tested relationships and explain any differences.
- Repeat the report checks as a seller and manager. Review sharing, field access, and report access when results differ.
- Disconnect and reconnect a pilot account through the supported workflow. Check diagnostic status and investigate gaps or duplicate-looking records afterward.
For each case, record the source interaction, relevant timestamp, Salesforce record IDs where available, and report inclusion result. This makes later troubleshooting repeatable.
Approve rollout only when you can explain every missing or unexpected row. After launch, sample recent activity regularly and assign someone responsibility for connection failures and reconciliation.
Plan Retention, Privacy, and Historical Comparisons
Capture retention varies by license and edition. Salesforce documents a six-month maximum for Standard EAC captured activity in its retention guidance. Don’t apply that window automatically to every license or storage path.
Timeline expiration can affect historical comparisons. Separately, emails synced into core Salesforce storage require their own storage and lifecycle planning.
Define the business purpose, retention trigger, accountable owner, and disposal process for each activity category. Legal, privacy, security, and business owners should approve periods for applicable jurisdictions and contracts.
Include exports, integrations, archives, and backups in that policy. Clearing a Contact’s email address doesn’t necessarily anonymize linked correspondence.
When preserving history, retain meaningful activity dates and source references where supported. Otherwise, imported or reconstructed records can distort period-based reporting.
Frequently Asked Questions
Does captured email automatically appear in every Salesforce report?
No. Reportability depends on the email storage configuration, report type, relationships, filters, and access. Even email stored as standard records won’t appear in an unrelated or restrictive report.
Can activity capture replace manual sales updates?
It reduces communication logging, but sellers still need to maintain deal context. Meeting outcomes, next steps, Opportunity Contact Roles, and stage decisions require an explicit process. Capture alone doesn’t explain why a deal progressed or stalled.
Make Reportability the Acceptance Standard
Salesforce Activity Capture is dependable when you validate the full path between a mailbox interaction and a report row. A successful connection is only the beginning.
Build around verified records and relationships, then test the same reports your sellers and managers will use.
That approach makes a busy timeline useful evidence rather than a misleading promise of complete sales reporting.
