Event attendee details sync when:
For example, when event organizers create events in Salesforce, they can invite attendees who are Salesforce users, contacts, or leads only. The attendee field syncs. Attendees who don’t match to a Salesforce record are external attendees and must be invited to events from organizers’ external Microsoft or Google calendars. In these cases, the attendee field doesn’t sync to Salesforce because nothing in Salesforce is a match.
Einstein Activity Capture syncs up to 50 attendees per event.
In Salesforce, event organizers and attendees experience the same events differently.
Events sync for both the organizer and attendees according to the sync direction that admins set for the organizer. Therefore, it’s best for admins to set up event sync for whole teams, not individuals. Otherwise, when an event organizer who isn’t set up to sync events invites an attendee who is set up to sync events, the attendee experiences some unexpected sync behavior. Sometimes, events don’t sync at all.
For events that sync, invitations and cancellations are emailed to attendees from Exchange or Google, not from Salesforce. For Lightning Experience or Salesforce mobile app users, Einstein Activity Capture is required to send event invitations to event attendees. For Salesforce Classic users, Salesforce-sent event invitations are suppressed when Einstein Activity Capture is enabled. This avoids sending duplicate invitations to users.
Attendee responses to event invitations never sync from Salesforce to Exchange or Google. In Lightning Experience and the Salesforce mobile app, it isn’t possible for attendees to respond to event invitations. To avoid overwriting attendance statuses in Salesforce Classic, learn where to respond to event invitations based on their set sync directions.
Attendees who sync their events experience unexpected sync behavior with events created by organizers.
If an event organizer is set up to sync after attendees have been syncing, participants can experience some unexpected behavior for scheduled events.
Attendees can be unintentionally removed from syncing events when all of the following are true.
However, if all of the following are true, the original attendee records can remain invited to syncing events despite having been intentionally removed.
000393758

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.