Is Nutshell Tracking Your Email? How to Block It

A follow up lands from a salesperson you spoke to last week. It reads like a normal note. Yes, Nutshell tracking your email is running on it whenever that rep has ticked one setting labeled "Track when messages sent from Nutshell are opened or clicked." From then on an invisible image rides along in everything they send. You open the message, the image loads, and an eye icon appears under the timestamp on their screen with a number beside it. No banner, no prompt.

Key Takeaways

• Nutshell's help center states plainly that "Nutshell uses a small embedded pixel in your outbound emails for tracking views," activated by one checkbox on the sender's settings page rather than per message.
• The sender sees an eye icon under the email timestamp with a running count of opens, and can scan those counts across a whole Sent folder at once.
• Nutshell's own tracking pixel explainer rates pixel accuracy at "70-85%" and blames Apple Mail Privacy Protection, launched September 2021 with iOS 15, for firing opens before anyone reads a word.
• Nutshell's link report FAQ concedes that "tech-savvy users can detect it by hovering over links to see redirect URLs," confirming that tracked links are rewritten.
• Nutshell suppresses opens generated by other Nutshell users so reps do not skew each other's numbers, an exemption its customers get and you do not.

Does Nutshell Track Email Opens?

Yes, whenever the sender has email tracking switched on in their Nutshell account. It is a setting, not a per message decision, so once it is on it applies to everything that leaves through Nutshell.

Nutshell's help article on how to track emails sent from Nutshell tells reps to check the box labeled "Track when messages sent from Nutshell are opened or clicked" on the Email send settings page. Templates sent in bulk from a list view are tracked automatically. There is no unsubscribe footer, because these are not campaigns. They are one to one messages from a person.

It reaches Gmail too. Nutshell's Chrome extension documentation says "you can keep an eye on how your emails sent from Gmail are doing by tracking when they are opened and clicked," switched on through a "Track and show emails in Nutshell" option during setup. The message can originate in an ordinary Gmail compose window and still carry the beacon, the same architecture used by Pipedrive and Copper.

What Does Nutshell's Tracking Actually Record?

An open event, when it happened, how many times you came back to the message, which links you clicked, and whether you replied. Not the words you write.

Nutshell describes the mechanism without dressing it up. Its product page for CRM email puts it this way: "Nutshell tracks opens, link clicks, and replies and shows you when emails are read, so reps can focus first on the people who are already paying attention."

Nutshell's own explainer on tracking pixels lists what the category collects: device type, the timestamp of the first open and how often it was reopened, your email client, and approximate geographic region derived from IP address. Gmail changes part of that picture. Google proxies remote images through its own servers, so the location guess degrades and your device details stay hidden. The request still goes out. The open still lands. The timestamp is still yours.

One thing we could not confirm from primary sources: the exact hostname Nutshell serves the pixel from. The documentation says a pixel exists but never names the tracking domain, so treat the shape of the image tag as your fingerprint rather than a host you can look up.

How Does Nutshell Track Link Clicks?

By rewriting the links so your click passes through a redirect before it reaches the page you actually wanted.

Nutshell confirms it in the FAQ of its link report announcement: "Most recipients won't notice tracking, but tech-savvy users can detect it by hovering over links to see redirect URLs or inspecting email source code." That sentence does a lot of work. It concedes the redirect, and it concedes that the design depends on you not looking.

The reporting is granular. Nutshell separates unique clicks, one person counted once regardless of frequency, from total clicks, which count every single one. The specific links you clicked land on your timeline with counts and times attached. Clicks fail differently from opens, which is why one defense rarely covers both, and we break the split down in our comparison of email open tracking versus click tracking. Turn off remote images and the pixel goes quiet, yet every rewritten link keeps working perfectly and still reports the moment you touch it.

How Do You Tell If a Nutshell Email Is Tracking You?

Read the raw message source and look for an image with no picture in it, then check whether the links point somewhere other than where they claim.

In Gmail, open the message, click the three dots at the top right, and choose "Show original." The full source loads in a new tab. Two things are worth finding:

• An image sized to be invisible. Search for <img and read the width and height. Values of 1, or CSS that hides the element, mark a beacon. The path usually carries a long unique string, and that string ties the fetch back to your address.
• A link whose destination does not match its text. Hover before clicking, or read the href. An unfamiliar redirect host wrapped around a familiar destination is click tracking, exactly as Nutshell's FAQ describes.

Our walkthrough on detecting email tracking pixels in Gmail covers the full inspection. The honest caveat: this is forensics, not defense. If you are reading headers, the pixel already fired and a row already sits on somebody's timeline.

Why Email Users Should Care

Nutshell is unusually candid about how weak this data is. Its help center admits "this technology does not allow us to identify who actually opened an email." Its pixel explainer rates the technique at "70-85%" accurate and names the culprit: "Apple Mail Privacy Protection (launched September 2021 with iOS 15) pre-loads all email images through proxy servers, triggering tracking pixels before recipients actually open emails." On the low end, roughly one in three logged opens is wrong.

Unreliable for the sender is not the same as harmless for you. A noisy signal still gets acted on. A phantom open triggers the follow up call, and a real open at 11pm on a Sunday tells the other side of a negotiation how badly you want the thing. Neither reading asked your permission. Nutshell's own guidance even tells customers to "always get consent before adding your tracking pixels" under GDPR. That duty sits with the sender, and almost nobody performs it.

Then there is the detail that reframes everything. Nutshell filters out views generated by other Nutshell users so reps do not pollute each other's counts. A working opt out exists inside the product, reserved for the people who pay for it. Everyone else gets measured, and if that pattern holds across CRMs the way our broader Gmail tracking guide suggests, most of the sales mail in your inbox carries a beacon you were never offered a way to decline.

How Do You Block Nutshell Tracking in Gmail?

Three approaches work, and each one reaches a different part of the problem.

1. Make Gmail ask before loading images. Gear icon, "See all settings," General tab, scroll to Images, select "Ask before displaying external images," then save. Nothing remote renders until you approve it, so the pixel never fires. Per Google's documentation on displaying images, the cost is indiscriminate: every logo, receipt, and boarding pass hides behind a prompt too. It also does nothing about rewritten links.

2. Do not mistake Gmail's proxy for a blocker. Routing images through Google hides your IP address and user agent, which blunts the location estimate. It does not cancel the fetch. Google requests the image, Nutshell logs the view, the eye icon appears. The open counts either way.

3. Strip the beacon before the message renders. An extension running inside Gmail can drop tracking pixel requests and neutralize redirect links while leaving the images you actually want intact. Gblock takes that route: it blocks known tracking pixel requests, strips tracking parameters and redirect hops out of links, and runs on a blocklist that updates itself instead of one frozen at install. It is not an anti phishing tool, and any blocklist is an ongoing race against new tracking hosts.

Which Blocking Method Covers What?

Nothing covers everything, and the useful question is which half of the tracking each option reaches. We rank the wider field in our roundup of the best email tracker blocker extensions.

Note who recommended one of these first: Nutshell's own pixel explainer tells readers "you will know if your email has a tracking pixel if you use a tool such as Boxy Suite or Ugly Email." We put the free options head to head in our Ugly Email vs PixelBlock vs Trocker comparison.

The Bottom Line

None of this is buried. Nutshell's help center names the pixel, its product pages sell opens and clicks and replies as a feature, and its blog explains the mechanism better than most privacy writing does. The asymmetry is not secrecy. It is that the person emailing you read all of it and you had no reason to. Blocking the beacon settles that quietly: the message still arrives, the images you want still load, the links still go where they say, and the counter beside the eye icon never moves.

Sources: Nutshell Help Center, Email: How to track emails sent from Nutshell, Nutshell Help Center, How to install the Chrome extension for Gmail, Nutshell, CRM email, Nutshell, Email tracking pixels 101, Nutshell, Dive into email engagement with the link report, Nutshell pricing, and Google, Display images in Gmail.