You know the little checkbox in Outlook and Gmail labeled "request a read receipt." You tick it, you send the email, and then… nothing. No confirmation. The recipient opened your message four days ago and you never heard a thing. That's not a bug. It's the design working exactly as intended — against you.

A read receipt is a polite request. When the recipient's email client receives it, the client is supposed to pop up a dialog asking, "The sender would like to know you read this — send a receipt?" Most people click "No." Many clients don't honor the request at all, and plenty strip it silently before the user ever sees it. The entire mechanism depends on the person you're tracking agreeing to be tracked. You can guess how often that goes your way.

There is a mechanism that doesn't ask: a tracking pixel — an invisible 1×1 image dropped into the body of the email. When the message is opened and the client loads that image, your server records the open. No dialog. No opt-in. It's the same technique behind every "open rate" number your marketing team has ever quoted. This guide shows you how it works, how to make one on InfoSniper's IP Logger and read the map of who opened your message — and, because we're not going to oversell it, exactly where Apple Mail and Gmail quietly break it.

Why the Read Receipt Almost Never Works

It's worth being precise about why the built-in feature fails, because it explains why the pixel exists at all. The MDN (Message Disposition Notification) standard that powers read receipts is opt-in by the reader at three separate points:

• The client may ignore it. There is no rule forcing a mail app to honor a receipt request. Apple Mail, many mobile clients, and privacy-focused providers simply drop it.
• The reader is usually asked. Where receipts are supported, the default is a prompt. Confronted with "let the sender know you read this?", most people decline.
• It only reports the open, nothing else. Even in the rare case a receipt comes back, it tells you a message was displayed — not from what city, on what device, or through which network.

So the read receipt is both unreliable and thin. A pixel is the opposite: it doesn't ask, and it carries a payload of context — a timestamp, an IP address, and everything a geolocation lookup can derive from it.

The Tracking Pixel: A Question Nobody Gets Asked

A tracking pixel — the older, more technical name is a web beacon — is a 1×1 pixel transparent image referenced in the HTML of your email.^[1] It looks like this in the message source:

Here's the clever part, and the reason this works when read receipts don't: displaying an image requires downloading it. An email client can't show you a picture without first fetching it from the server it lives on. That fetch is an ordinary HTTP request, and every HTTP request carries the requester's public IP address and arrives at a specific moment in time. The image is transparent and one pixel wide, so the reader sees nothing. But the server sees a knock on the door — and it knows who knocked and when.

This is not a fringe hack. Most email marketing platforms embed exactly this kind of pixel to compute the "open rate" on every campaign. The difference with InfoSniper's pixel is that you own it, and instead of a rolled-up percentage in a dashboard you get each open plotted on a map with the city, ISP, and device attached.

How an Invisible Pixel Logs an Open

Four steps sit between "recipient opens the email" and "pin on your map." Knowing the chain is what lets you judge how much to trust any single open.

Step 1 is the only one that involves a human. Everything after it is automatic — which is both the strength (nobody has to agree to anything) and the weakness (a machine, not the reader, sometimes triggers step 2). The IP captured in step 2 is a hard fact about where the request came from. Turning it into a place in step 3 is an estimate from a commercial-grade geolocation database, excellent for a fixed home connection and much weaker for anything that pools or relays traffic. We break the accuracy down region by region in How Accurate Is IP Geolocation?

Create a Pixel on InfoSniper in Two Minutes

The pixel flow is deliberately short. There's nothing to install and no account required for your first tracker.

1. Open the IP Logger and switch the tracker type to "Pixel." Unlike a link tracker, a pixel needs no destination URL — there's nothing to redirect to. Just give it a name you'll recognize later, like "Q3 proposal to Acme."
2. Copy the embed code. InfoSniper hands you a ready-made HTML <img> tag, plus a plain URL and a BBCode version. The HTML tag is the one you want for email.
3. Paste it into your email's HTML. In Gmail or Outlook you'll need to compose in HTML mode, or use the "insert image by URL" option and point it at the pixel URL. In a proper email tool, drop the tag anywhere in the body — the bottom is fine and least conspicuous.
4. Send the email. Nothing looks different to the recipient; the image is one transparent pixel.
5. Open your analytics link. Each open appears with a timestamp and lands on the map with the city, ISP, and device.

Reading the Open: When, Where, and on What

Every logged open gives you three layers of information. They are not equally trustworthy, and knowing the order of confidence keeps you from over-reading a single ping.

The habit that separates careful users from credulous ones: read the ISP field before you trust the city marker. If the network name is a hosting or cloud provider — "Google LLC," "Apple Inc.," "Cloudflare," "Amazon" — you are almost certainly looking at a proxy, not the reader's home. That's your cue to distrust the pin. A residential ISP like Comcast or BT is your best-case open; the marker is probably in the right metro. Mobile carriers sit in between — often routed through a regional hub tens of kilometers from the reader.

One genuinely useful pattern: across multiple opens, a stable device-and-client fingerprint tells you whether the same person keeps returning to your message, even when the city jumps around. Three opens all reading "iPhone / Apple Mail" over two days is a recognizable reader re-checking your proposal — useful timing intelligence for a follow-up, even if two of those pings geolocate to an Apple data center.

The Big Caveat: Apple Mail and Gmail

This is the section that dishonest "email spy" tools leave out, and it's the one that will save you from an embarrassingly wrong conclusion. Two of the biggest email clients on the planet deliberately interfere with pixel tracking — in opposite ways, both of which distort what you see.

Apple Mail Privacy Protection: false opens

Since 2021, Apple Mail has shipped with Mail Privacy Protection, and it is on for a huge share of Apple users. When enabled, Apple pre-loads and caches all remote images through its own proxy servers the moment a message arrives — before the reader has opened anything.^[2] Two consequences follow:

• False opens. Your pixel fires when Apple's server fetches it, not when the human reads the email. An "open" can register at 3 a.m. while the recipient is asleep. You cannot tell a real open from a pre-fetch.
• Masked location. The IP you capture is Apple's proxy, which strips the reader's real IP and reports only a broad region. The marker lands on an Apple data center, not the reader's city.

This matters because Apple Mail's slice of tracked email opens is enormous — measurements from email analytics firms have put Apple's share of opens above 50% in many datasets.^[3] A large fraction of the opens you log on an email pixel will therefore be Apple pre-fetches, not people.

Gmail: the image proxy

Gmail plays a different game. Since 2013 it has served every remote image in an email through Google's own image proxy servers.^[4] The pixel still loads — so you do usually learn the message was opened — but the IP that reaches you belongs to Google, not the reader. The device is often masked too. So Gmail opens tend to confirm the when reasonably well while erasing the where.

So does email open tracking still work? Yes — for the substantial share of recipients not reading in Apple Mail or Gmail, and, even for those two, as a "when" signal more than a "where" signal. Outlook desktop, Yahoo, Thunderbird, many corporate clients, and anyone who hasn't turned on Apple's protection will hand you a clean open with a real location. The mistake is treating every logged open as gospel. Read the ISP field, discount the data-center pings, and you'll get honest value out of it.

Where This Is Genuinely Useful

Stripped of the spy-movie framing, email open tracking is a mundane and widely used business tool. The legitimate uses are the ones worth building a habit around:

• Sales follow-up timing. You sent a proposal Tuesday. It opens Thursday at 4 p.m. That's your cue to call — not a cold "just checking in" a week later, but a warm follow-up minutes after it's on their screen. Sales teams have used pixel timing for exactly this for years.
• Confirming a document was seen. You emailed a contract, an invoice, or a deadline. A logged open is a soft confirmation that it landed and was viewed — useful when someone later claims they "never got it."
• Catching the "never received it" excuse. An open at 9:14 a.m. is a quiet, factual counter to a claim that a message vanished.
• Newsletter and content engagement. Which of your sends actually get opened, and roughly where your readers are, without wiring up a full marketing platform.

And the boundaries, because the tool is powerful and the failure mode is a confident wrong accusation:

Pixel vs. Link Tracker

InfoSniper's logger works two ways, and choosing the right one is the difference between a clean signal and no signal.

Rule of thumb: if you want to know a message was opened without asking anyone to click, use a pixel. If you want a shareable URL and to know someone clicked, use a link tracker — which we cover end to end, including reading the click map, in IP Logger With a Map. Both plot their hits on the same interactive map.