---
schema_version: "1"
id: 93a1284607013c3feda731a2cee6c4e36e3858d2d4d93a18c14a129ec933fcfb
title: Considerations for Excluding Data from Einstein Activity Capture
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/aac_add_excluded_addresses_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.aac_add_excluded_addresses_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 6521e048eb14a083ffaa18ec3e7d2ba8456a19736bd144b5d19e9f167490760e
description: Admins and users can prevent emails and events connected with a particular email address, domain, keywords, or sensitive content from association with Salesforce records. You can also prevent events from syncing between Salesforce and connected accounts. Make sure that you understand the effects of excluding this data from Einstein Activity Capture.
products:
  - Sales Cloud
  - Cross Cloud
  - Service Cloud Voice
release: "264"
---
# Considerations for Excluding Data from Einstein Activity Capture

Admins and users can prevent emails and events connected with a particular email address, domain, keywords, or sensitive content from association with Salesforce records. You can also prevent events from syncing between Salesforce and connected accounts. Make sure that you understand the effects of excluding this data from Einstein Activity Capture.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available with Einstein Activity Capture Standard in Sales in <strong>Starter</strong>, <strong>Pro Suite</strong>, <strong>Professional</strong>, and <strong>Enterprise</strong> Editions</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available with <strong>Unlimited </strong>Edition, <strong>Einstein 1 Sales Edition</strong>, and <strong>Agentforce 1 Edition</strong></td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available with Einstein for Sales, which is included in <strong>Einstein 1 Sales Edition</strong> and available for an extra cost in <strong>Enterprise</strong> and <strong>Unlimited</strong> Editions</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available with Sales Engagement, which is included with Sales in <strong>Performance</strong> and <strong>Unlimited</strong> Editions, and available for an extra cost in <strong>Professional</strong> and <strong>Enterprise</strong> Editions</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available with Revenue Intelligence, which is available for an extra cost in <strong>Enterprise</strong> and <strong>Unlimited</strong> Editions</td></tr></tbody></table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_productivity-264-0-0-production-enus/b2f6c36a-fa61-4a3c-9752-032ce1818a69/images/icon_note.png)

Note We’re reorganizing the Einstein Activity Capture documentation. We’re moving some information around, but we aren’t deleting anything.

- The admin’s org-wide Excluded Addresses list applies to all Einstein Activity Capture users in the org and is the baseline that always takes effect. Users can add more email addresses to their own Excluded Addresses list to extend (but not override) the org-wide list.
- Salesforce adds the default internal domain to the excluded list so that emails and events between users in your company aren’t added or synced to Salesforce records. Your company’s default internal domain is the domain used in the admin’s email address. If your company uses other internal domains, the admin must add them to the excluded list.
- Emails where all email addresses are part of the internal domain (internal emails) are always excluded. If the sender, recipient, and cc address contain an internal domain you specified in the excluded list, the email is considered internal. If the sender, recipient, and cc address contain the same domain of a connected data source, the email is considered internal.
- Events where all attendees, including the organizer, are part of the internal domain (internal events) can be included or excluded. Events that have the meeting organizer as the sole attendee are also considered. Go to Einstein Activity Capture settings and turn **Sync Internal Events** on or off.
- Internal event filtering is based on attendee email addresses on the event, regardless of whether they match Salesforce user, contact, or lead records.
- Internal domains can’t be deleted from the excluded addresses list when the domain matches the primary email address (the email on the user record) of any:
    - Salesforce admin
    - Salesforce user with the Customize Application or Modify All Data permissions
- If the email addresses on a Salesforce record all belong to an internal domain, then emails and events aren’t added to the record’s timeline. For example, the internal domain used to set up Einstein Activity Capture is acme.com. John Smith is a contact record in Salesforce with the email john@acme.com. The John Smith contact record doesn’t show any emails or events because the email address john@acme.com is part of the acme.com internal domain.
- When Sync Email as Salesforce Activity is turned on, email messages and events that match any exclusion, such as keyword, email address or domain, and sensitive content, aren’t captured, synced, or stored. This data is unavailable in Salesforce. Without Sync Email as Salesforce Activity, sensitive emails are handled differently. The emails are set to the Don’t Share sharing setting, regardless of the user’s individual sharing setting. The emails are marked as sensitive so that users know why the sharing setting was changed. For example, emails that include a credit card number from a customer are kept private. Automated responses about a password reset are also kept private. The email owner can later change the sharing setting to something less restrictive. The settings that prevent these emails from being shared are on by default, but [you can turn them off](https://help.salesforce.com/s/articleView?id=sales.aac_set_default_activity_sharing.htm&release=264.0.0&type=5 "Use activity sharing rules to manage how users see and share captured event data. If Sync Email as Salesforce Activity is turned on, activity sharing rules also control the visibility of captured email data. If captured email isn’t synced as activity data, use Einstein Activity Capture settings to manage data sharing.").
    
    Some automated email replies are useful to your colleagues and aren’t set to private. Examples include out-of-office replies and email bounce notifications.
    
    To add extra protections, admins can update the Excluded Addresses list with customer domains and email addresses from the services their company uses. Services that offer payroll, financial support, or human resources for your company are good candidates to add to the Excluded List. Then, if someone creates a Salesforce contact record with the email address no-reply@confidential.tax.details.com, emails from that sender aren’t added to the contact’s activity timeline.
- All internal domains that are included in the excluded list apply to Einstein Activity Capture.
- Add keywords, addresses, and domains to the excluded data capture and turning on a sensitive data detection setting filters newly captured data and hides matching past data from the activity timeline. It doesn’t delete any previously captured data. When you add excludes this is what happens:
    - New emails and events aren’t added to the activity timeline, and past matching ones are removed from the activity timeline.
    - New events are still added to the user’s Salesforce calendar, and past ones remain.
    - Email that doesn’t match to a user, contact, lead, or other record is stored on Hyperforce and Amazon Web Services (AWS) for up to 30 days.
    - Manually added email and events remain on the activity timeline and calendar.
- When you exclude an email address or customer domain, here’s what happens regarding synced events.
    - New events don’t sync between Salesforce and the connected accounts.
    - New events aren’t stored in Salesforce.
    - Previously synced events no longer sync, but they remain in Salesforce or the connected accounts.
- If you remove an email address or customer domain from the excluded list, new email and events are captured and synced. Past emails and events remain excluded.
- In an event series, only the events that meet the excluded email address or domain criteria don’t sync.
- Admins can prevent all email data for specific Einstein Activity Capture users from being added to the activity timeline and stored by Salesforce. When creating or editing an Einstein Activity Capture configuration, an admin can disable emails.
- When you exclude an email address or customer domain, several rules determine whether the related emails and events are captured and synced.
    - If any participant on an email thread or event isn’t on the applicable Excluded Addresses list, the email or event can still be captured and added to related Salesforce records, even when other participants are excluded.
    - The admin’s list applies to the entire org, and has priority over users’ lists.
    - When email or event recipients include multiple Einstein Activity Capture users and a customer, Einstein Activity Capture users must add the customer’s email to the Excluded Addresses list.
    - When email or event recipients include Einstein Activity Capture users and multiple customers, Einstein Activity Capture users must add at least one customer email or domain to the Excluded Addresses.

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_productivity-264-0-0-production-enus/b2f6c36a-fa61-4a3c-9752-032ce1818a69/images/icon_example.png)

Example

Albert and Barry are Einstein Activity Capture users. Cindy is a contact on the Acme account. Review how different scenarios affect what’s captured and synced.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
            <colgroup>
              <col style="width:29.7029702970297%">
              <col style="width:24.893917963224894%">
              <col style="width:14.144271570014144%">
              <col style="width:15.700141442715701%">
              <col style="width:15.55869872701556%">
            </colgroup>
            <thead class="slds-text-title_caps ">
              <tr class="">
                <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d93568e277">Scenario</th>
                <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d93568e280">Excluded Addresses List</th>
                <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d93568e283">Event Added to Activity Timeline?</th>
                <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d93568e286">Event Added to User’s Salesforce Calendar?</th>
                <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d93568e289">Event Synced Between Salesforce and Connected Accounts?</th>
              </tr>
            </thead>
            <tbody>
              <tr class="">
                <td data-label="Scenario" class="slds-cell-wrap" rowspan="3" style="vertical-align:top;" headers="d93568e277 ">Albert sends a meeting invite to Cindy and includes Barry in the
                  invite.</td>

                <td data-label="Excluded Addresses List" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e280 ">Albert and Barry add Cindy to their lists.</td>

                <td data-label="Event Added to Activity Timeline?" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e283 ">No</td>

                <td data-label="Event Added to User’s Salesforce Calendar?" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e286 ">Yes</td>

                <td data-label="Event Synced Between Salesforce and Connected Accounts?" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e289 ">No</td>

              </tr>
              <tr class="">
                <td data-label="Excluded Addresses List" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e280 ">Albert adds Cindy to their list. Barry doesn’t.</td>

                <td data-label="Event Added to Activity Timeline?" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e283 ">Yes</td>

                <td data-label="Event Added to User’s Salesforce Calendar?" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e286 ">Yes</td>

                <td data-label="Event Synced Between Salesforce and Connected Accounts?" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e289 ">Yes</td>

              </tr>
              <tr class="">
                <td data-label="Excluded Addresses List" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e280 ">Albert adds Cindy to their list. Barry doesn’t. The admin adds Cindy’s email
                  domain to the org-wide list.</td>

                <td data-label="Event Added to Activity Timeline?" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e283 ">No</td>

                <td data-label="Event Added to User’s Salesforce Calendar?" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e286 ">Yes</td>

                <td data-label="Event Synced Between Salesforce and Connected Accounts?" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e289 ">No</td>

              </tr>
              <tr class="">
                <td data-label="Scenario" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e277 ">Albert sends a meeting invite to Cindy and the team. Some of the recipients use
                  the @acme.com domain and others use the @acme_jr.com domain.</td>

                <td data-label="Excluded Addresses List" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e280 ">Albert adds only Cindy’s email to their list.</td>

                <td data-label="Event Added to Activity Timeline?" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e283 ">No</td>

                <td data-label="Event Added to User’s Salesforce Calendar?" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e286 ">Yes</td>

                <td data-label="Event Synced Between Salesforce and Connected Accounts?" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e289 ">No</td>

              </tr>
              <tr class="">
                <td data-label="Scenario" class="slds-cell-wrap" rowspan="2" style="vertical-align:top;" headers="d93568e277 ">Albert sends a meeting invite to Cindy and the team. Some of the
                  recipients use the @acme.com domain and others use the @acme_jr.com domain. Albert
                  includes Barry in the invite.</td>

                <td data-label="Excluded Addresses List" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e280 ">Albert adds only Cindy to their list. Barry doesn’t.</td>

                <td data-label="Event Added to Activity Timeline?" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e283 ">Yes</td>

                <td data-label="Event Added to User’s Salesforce Calendar?" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e286 ">Yes</td>

                <td data-label="Event Synced Between Salesforce and Connected Accounts?" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e289 ">Yes</td>

              </tr>
              <tr class="">
                <td data-label="Excluded Addresses List" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e280 ">The admin adds the @acme_jr domain to the org-wide list.</td>

                <td data-label="Event Added to Activity Timeline?" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e283 ">No</td>

                <td data-label="Event Added to User’s Salesforce Calendar?" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e286 ">Yes</td>

                <td data-label="Event Synced Between Salesforce and Connected Accounts?" class="slds-cell-wrap" style="vertical-align:top;" headers="d93568e289 ">No</td>

              </tr>
            </tbody>
          </table>

#### See Also

- [Exclude Emails and Events from Einstein Activity Capture](https://help.salesforce.com/s/articleView?id=sales.eac_exclude_emails_and_events_for_org.htm&release=264.0.0&type=5 "Set up org-wide exclusions to control which emails and calendar events are captured and stored. Exclude emails and events from specific addresses and domains, and filter emails based on keywords and sensitive content. Adding exclusions doesn’t remove previously captured emails or synced events. Exclusions only filter incoming data after the value is saved.")
- [Exclude Emails and Events from Your Salesforce Activities](https://help.salesforce.com/s/articleView?id=sales.aac_add_excluded_addresses.htm&release=264.0.0&type=5 "When you add email addresses to your Excluded Addresses list, emails and events with those addresses aren’t added to the activity timeline of related Salesforce records. Events aren’t added to the Salesforce calendar. And events aren’t synced between Salesforce and the connected accounts.")
- [Einstein Activity Capture](https://help.salesforce.com/s/articleView?id=sales.einstein_sales_aac.htm&release=264.0.0&type=5 "Eliminate manual data entry and transform a list of engagements into action. Einstein Activity Capture syncs your Microsoft or Google account with Salesforce, linking email and calendar activities to the relevant contacts, leads, and opportunities. Einstein Activity Capture gives your team and AI agents the critical context needed to make their next move.")