Filter Email Tracking
Filter Email Tracking is the Salesforce Setup setting that excludes specific email addresses or domains from being tracked when users open or click links in emails sent through Sales Cloud features like Email Templates, List Email, and the Sales Inbox.
Definition
Filter Email Tracking is the Salesforce Setup setting that excludes specific email addresses or domains from being tracked when users open or click links in emails sent through Sales Cloud features like Email Templates, List Email, and the Sales Inbox. When email tracking is enabled, the platform embeds a pixel and link-rewriting in outbound mail to record opens and clicks. The filter list lets administrators exclude internal domains, partner addresses, or test recipients from this tracking, both for privacy reasons and to keep tracking data clean.
The page is small but matters disproportionately because uncorrected tracking data produces misleading sales metrics. A sales rep forwarding a tracked email to a colleague generates spurious open events. Marketing dashboards counting opens against the recipient inflate engagement metrics. The filter list is the mechanism for excluding these known-noisy addresses so the tracking data reflects actual customer engagement rather than internal traffic.
How the email tracking filter works
Why filter at all
Tracked emails carry an invisible pixel. When the recipient opens the email, the pixel loads and the platform records an open event. The mechanism is accurate enough for marketing analytics, but it generates noise from internal forwards, mail security scanners that fetch pixels for malware analysis, and corporate gateways that pre-fetch links. Filtering known noisy sources at the configuration layer produces cleaner metrics than trying to clean the data downstream.
Address versus domain filtering
Filters can target individual email addresses or entire domains. Adding your own corporate domain (@yourcompany.com) excludes all internal recipients with one entry. Adding specific external addresses is useful when a partner uses a known address that always pre-fetches. The domain match is suffix-based; @example.com matches user@example.com and user@sub.example.com.
What the filter affects
The filter only affects email-tracking events: opens and clicks. Other event types (bounces, deliverability failures, replies) are unaffected. The filter applies to email sent through Salesforce-native channels (Sales Email, List Email, Email Templates fired from Workflow). It does not affect Marketing Cloud or Pardot tracking; those tools have their own exclusion lists.
Internal traffic noise
Forwarded internal email is the most common source of spurious tracking events. A rep emails a customer and BCCs their manager; the manager opens the email and generates an open event. Without filtering the corporate domain, that event credits the customer for an open they never made. Add your corporate domain to the filter list on day one; this single entry typically removes 30-50% of noise in raw tracking data.
Mail security scanners
Corporate mail security tools (Mimecast, Proofpoint, Microsoft ATP) often scan inbound mail by fetching all embedded resources, including tracking pixels. This produces a flood of false opens before the human even sees the email. The known scanner addresses can be filtered, though the list varies by tool and region. For organizations sending into corporate inboxes, the filter list deserves a periodic update as security tools change behavior.
Privacy and consent considerations
Some jurisdictions (GDPR in the EU, CCPA in California) treat email tracking as personal data processing requiring consent. Adding addresses to the exclusion list is one mechanism for respecting opt-outs at the platform level rather than relying on each user's mail client. For organizations subject to these regulations, the filter list should integrate with the consent management process.
Auditing the filter list
The filter list is org-wide and persistent. Without periodic review, it accumulates entries from departed administrators, retired test domains, and obsolete partner integrations. Audit at least annually: review each entry, confirm it still applies, remove stale ones. A bloated filter list does no harm but is a sign of org configuration drift that deserves attention.
Configure Filter Email Tracking
Configuring the email tracking filter is a small Setup page but the entry strategy matters. The steps below cover what to add on day one and what to audit periodically.
- Confirm email tracking is enabled
Setup > Email > Sales Email > Activity Settings. Confirm Email Tracking is on. Filtering only matters if tracking is active.
- Navigate to Filter Email Tracking
Setup > Email > Filter Email Tracking. The page shows a list of currently filtered addresses and domains.
- Add your corporate domain
Enter your primary domain (yourcompany.com) without the @ symbol. Save. Internal forwards are now excluded.
- Add known noisy addresses
Add any partner addresses, test inboxes, or compliance archives known to pre-fetch tracked emails. Document the reason for each entry.
- Add mail security scanner addresses
Identify scanner addresses from corporate IT. Common ones: ATP, Proofpoint, Mimecast scan endpoints. Add the specific addresses they advertise.
- Validate with a test send
Send a tracked email to an internal address. Confirm no open event is recorded after the recipient opens it. Repeat for an external address to confirm tracking still works.
- Schedule annual audit
Add a calendar reminder to review the filter list annually. Remove stale entries; confirm corporate domain changes are reflected.
Specific email address to filter. Exact match (user@example.com).
Entire domain to filter. Suffix match (example.com catches sub.example.com).
Optional note per entry explaining why it was added. Critical for future audits.
Some entries support temporary disabling rather than deletion. Useful when troubleshooting whether an exclusion is causing missing data.
Some org versions support bulk import of filter entries. Useful for migrating from a separate exclusion-list tool.
- The filter only affects email tracking, not other email events. Bounces and deliverability data still flow normally.
- Marketing Cloud and Pardot tracking have their own exclusion lists. Filtering here does not affect those platforms.
- Domain match is suffix-based and catches subdomains. Adding a domain may exclude more than intended; review subdomains before adding.
- Mail security scanner addresses change. Stale scanner entries in the filter list do no harm, but new scanner endpoints need to be added when corporate IT changes tools.
- Removing an entry does not retroactively re-tracking past emails. Removing a domain only affects future sends, not historical tracking data.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is the primary benefit of Filter Email Tracking for Salesforce administrators?
Q2. Can a Salesforce admin configure Filter Email Tracking without writing code?
Q3. Why is understanding Filter Email Tracking important for Salesforce admins?
Discussion
Loading discussion…