Filter Email Tracking
Filter Email Tracking is the Salesforce Setup page where an administrator enters IP address ranges that should be excluded when the platform records email opens and clicks.
Definition
Filter Email Tracking is the Salesforce Setup page where an administrator enters IP address ranges that should be excluded when the platform records email opens and clicks. When email tracking is turned on, Salesforce embeds a tiny invisible image (a tracking pixel) in HTML emails sent through Sales Cloud channels. If a request for that pixel comes from one of the filtered IP ranges, the open is not counted. The same idea covers tracked links.
The setting exists because raw open data is noisy. Internal staff, corporate mail gateways, and security scanners all load images and fetch links, which inflates engagement numbers against the wrong people. By listing the IP ranges those requests come from, an admin keeps the tracking data closer to real customer behavior. The page is small, but it has an outsized effect on how trustworthy your email metrics are.
How IP-range filtering cleans your open data
What the page actually filters
The key thing to get right is that this page filters by IP address, not by email address or domain. Many admins assume they can type in a recipient address or a company domain to suppress its opens. That is a different feature set. On the Filter Email Tracking page you enter ranges of IP addresses using a start value and an end value. When Salesforce receives the pixel request or a tracked-link click, it checks the source IP against your ranges. A match means the event is dropped before it ever lands on the record or in a report. This design targets the network the request comes from, which is exactly where the noise lives. Your own office network, a VPN exit, or a mail-security appliance all have known, stable IP ranges. Email addresses are harder to pin down because forwarded mail and shared mailboxes move around. Filtering at the IP layer catches a whole building or a whole gateway with one entry. When the configuration is deployed between orgs, it travels as the IpAddressRange metadata type, the same shape used elsewhere in Setup for trusted ranges.
Turn tracking on before you filter
Filtering only does something once email tracking is enabled, and that switch lives in a different place. Go to Setup, open Activity Settings, and select the option to enable email tracking. With Enhanced Email active, Salesforce can insert the tracking pixel into outbound HTML messages and rewrite links so clicks can be counted. The open status then shows on the email activity, and you can build reports on opens and clicks across leads, contacts, and other records. Once tracking is producing events, the Filter Email Tracking page becomes useful. Without tracking on, there is nothing to filter and the page does nothing visible. The right order is enable tracking, watch the raw numbers for a short while, identify which IP ranges are generating obvious false opens, then add those ranges to the filter. Treat the two settings as a pair. One produces the signal, the other removes the parts of the signal you know to be noise. Skipping the filter step is a common reason early adopters distrust their own open rates.
Why a tracked open is not always a human
The tracking pixel is a one-by-one transparent image hosted by Salesforce. The theory is simple: a person opens the email, their mail client loads images, the pixel request hits Salesforce, and an open is logged. In practice, several non-human actors load that same image. Corporate spam filters and mail gateways often fetch every embedded resource to scan it for threats, which fires the pixel before the recipient sees anything. Some clients pre-fetch or proxy images through their own servers, which both inflates and anonymizes the request. This is the gap the filter closes. If you know your inbound mail to a partner passes through a scanning appliance at a fixed IP range, every message you send them may register a false open from that range. Adding the range stops those phantom opens. The same logic applies to your internal users who receive copies of campaign sends. Image blocking works the other way too: a recipient who blocks images never loads the pixel, so a genuine open can go uncounted. No pixel system is perfect, which is why click data is usually treated as the stronger signal.
Internal traffic is the biggest source of noise
The most common reason opens look inflated is your own team. When a company sends a newsletter, a release update, or a product announcement, internal staff are frequently on the list for visibility. If they open or click, those events count exactly like a prospect would, and the engagement rate drifts upward. The same happens when a rep BCCs a manager on a tracked message and the manager opens it. The record gets credited for an open the customer never made. Filtering your corporate office and VPN IP ranges removes this in one move. Instead of trying to clean each spurious event after the fact, you stop them at the source. For an org that routinely includes employees on big sends, this single category of filtering can be the difference between an open rate that reflects customers and one that reflects the marketing team checking its own work. Identify the public-facing IP ranges your staff browse and open mail from, confirm them with your network team, and enter those as your first filter entries. It is the highest-value change you can make on this page.
Where this filter does not reach
The Filter Email Tracking page governs native Salesforce email tracking only. It applies to messages sent through Sales Cloud channels such as the email composer on a record, List Email, and templates fired from automation. It does not control tracking in Marketing Cloud Account Engagement (formerly Pardot) or Marketing Cloud Engagement. Those products run their own tracking infrastructure and their own exclusion settings, so an IP range you add in Setup has no effect on a Pardot list email. It also only touches open and click events. Bounces, delivery failures, and replies are recorded through other mechanisms and are unaffected by these ranges. Knowing the boundary saves confusion when numbers disagree across tools. If your Pardot dashboard and your Salesforce activity report show different open counts, the filter is one likely reason: it suppresses internal opens on the Sales Cloud side while Pardot may still count them. Decide where each audience should be measured, then apply the matching exclusion in the matching product rather than expecting one page to cover everything.
Privacy, deployment, and ongoing upkeep
There is a privacy angle worth noting. Some regions treat email open tracking as processing of personal data. Salesforce also offers a per-record Don't Track preference under Data Protection and Privacy, which suppresses pixel insertion for a specific contact or lead who has opted out. IP-range filtering is a blunter, network-level tool and is not a substitute for honoring individual opt-outs, but the two can work alongside each other in a wider consent process. On the operational side, the page is org-wide and persistent. Ranges deploy cleanly between sandboxes and production because they carry as standard metadata, which makes them easy to keep consistent across environments. Over time, though, the list drifts. Office ranges change, VPN providers rotate, old test networks get decommissioned, and entries linger after the admin who added them has left. Schedule a review at least once a year. Walk each range, confirm it still belongs, and remove anything stale. A bloated list does no direct harm, but it is a reliable sign of configuration that nobody owns anymore.
Set up IP-range filtering for email tracking
Set up IP-range filtering in two stages: confirm email tracking is on, then add the ranges you want excluded. You need the Customize Application permission. Both settings live in Setup.
- Confirm tracking is enabled
In Setup, use Quick Find to open Activity Settings. Make sure the option to enable email tracking is selected and Enhanced Email is active, so opens and clicks are being recorded in the first place.
- Open Filter Email Tracking
In Setup, type Filter Email Tracking in Quick Find and open the page. This is where you manage the list of IP address ranges that should be excluded from open and click tracking.
- Gather the IP ranges to exclude
Work with your network team to list the public IP ranges for your offices, VPN exits, and any mail-scanning gateways. These are the sources that generate false opens and are the right things to filter.
- Add each range
Enter a start IP address and an end IP address for each range, then save. Use a single address in each field and keep the end value higher than the start. Repeat for every range you identified.
- Verify and document
Send a test campaign that includes an internal recipient inside a filtered range, then check that their open does not appear on the record. Note who owns each entry so future audits are easy.
The lowest IP address in the range you want excluded from email tracking. For a single machine, this is the same as the end of a one-address range.
The highest IP address in the range. Keep this value greater than the start so the range is valid and covers the addresses in between.
The ranges apply org-wide to native Salesforce email tracking only. They do not affect Marketing Cloud or Account Engagement, which have separate exclusion settings.
- This page filters by IP address, not by email address or domain. To suppress tracking for a person, use the per-record Don't Track preference instead.
- Filtering does nothing until email tracking is enabled in Activity Settings. Enable tracking first, then add ranges.
- Ranges deploy as the IpAddressRange metadata type, so they move between sandboxes and production with your other config.
- The filter only affects opens and clicks. Bounces, delivery failures, and replies are recorded separately and are not excluded.
Prefer this walkthrough as its own page? How to Filter Email Tracking in Salesforce, step by step
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Filter Email Tracking.
Hands-on resources to go deeper on Filter Email Tracking.
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 does the Filter Email Tracking setting do in Salesforce?
Q2. Why is adding your own corporate domain to the Filter Email Tracking list usually the first step?
Q3. Which email event types does Filter Email Tracking actually affect?
Discussion
Loading discussion…