Question

Difficulty: HardEinstein Activity Capture and Sync Configurations

An administrator at a global logistics firm is configuring Einstein Activity Capture (EAC) for different user groups using Microsoft Exchange and Google Workspace. Match each business synchronization requirement to its corresponding EAC configuration setting.

  • Capture email and event interactions for timeline visibility while storing data off-platform in AWS rather than generating standard Salesforce Task/Event database records.Einstein Activity Capture default activity storage model
  • Allow event updates made in Google Calendar to update Salesforce records, but prevent events created in Salesforce from syncing to Google Calendar.Event Sync Direction configured to Google to Salesforce
  • Ensure contacts updated in Salesforce automatically update Microsoft Outlook contacts and vice versa.Contact Sync Direction configured to Both Ways
  • Prevent specific sensitive communications with external vendor domains from being captured and logged on record activity timelines.Excluded Addresses list configured with domain filters

Answer

The business sync requirements match the EAC configurations as follows: 1) Activity capture off-platform storage matches Einstein Activity Capture default activity storage model; 2) One-way event sync from Google to Salesforce matches Event Sync Direction configured to Google to Salesforce; 3) Bi-directional contact sync matches Contact Sync Direction configured to Both Ways; 4) Filtering sensitive vendor communications matches Excluded Addresses list configured with domain filters.
Each business requirement directly corresponds to a specific EAC configuration setting: storing activity data off-platform on AWS corresponds to the default EAC activity storage model; unidirectional sync from external calendars maps to the 'Google to Salesforce' direction; bi-directional contact management requires setting contact sync to 'Both Ways'; and preventing tracking of sensitive domains requires entries in the Excluded Addresses configuration list.

Step-by-Step Solution

1
Analyze requirement 1 regarding activity logging behavior and storage location.
Identify that EAC stores email and event activity data off-platform in secure AWS cloud infrastructure to render items on record timelines, avoiding standard Salesforce Task/Event record creation.
This off-platform architecture is the core design distinction between Einstein Activity Capture and standard activity management.
2
Evaluate requirement 2 regarding external calendar event flow into Salesforce.
Match the one-way inbound calendar sync requirement to the 'Google to Salesforce' Event Sync Direction setting.
Sync direction configurations explicitly control whether calendar data flows unidirectionally or bidirectionally.
3
Evaluate requirement 3 for maintaining identical contact lists across Outlook and Salesforce.
Select 'Both Ways' Contact Sync Direction.
Bi-directional contact synchronization ensures edits in either system propagate to the connected application.
4
Evaluate requirement 4 for restricting sensitive email and event tracking for vendor domains.
Associate domain privacy filtering with the Excluded Addresses feature.
The Excluded Addresses setting prevents EAC from syncing or capturing activity linked to specific internal or external domains.

Key Concept

Einstein Activity Capture Configurations and Synchronization Settings
Rate this question