Your dashboard says 47 opens on that proposal. How many were actually the prospect?
For most email-tracking tools, the answer is: nobody knows, including the tool. Every time you re-read your own sent email — to remind yourself of the wording before a call, to forward it to a champion, to copy-paste a line into a follow-up — the pixel loads. That counts. Same domain, same image, same request shape as the recipient's open. The server cannot tell you and the buyer apart.
For an AE running a 90-day deal cycle this is not a small problem. You re-read proposals constantly. You scan your sent folder before discovery calls. The opens you trust least pile up most on the deals you care most about.
The fix, in one sentence
We silently drop opens when it is you re-reading your own sent email.
The Outsolvi add-in is already running in your inbox — Outlook desktop, Outlook web, Gmail, Outlook for Mac. The moment you open one of your own sent emails, the add-in fires a one-line heads-up to our server: "this open is the sender, not the recipient." A second later the pixel loads. The server checks for a matching heads-up in the last 5 seconds and, if it finds one, flags the open as `is_self` and excludes it from every stat. The pixel still loads so nothing breaks. The record stays in the database with a flag, so you can inspect self-opens if you want — every default view hides them.
Why a cookie does not solve this
The obvious instinct is "set a cookie when the sender logs into Outsolvi, then check for it when the pixel fires." It fails on two of the three surfaces AEs actually use.
Outlook desktop's internal viewer is not a browser. When you open a sent email in Outlook desktop, the pixel request comes from Outlook's own HTTP stack, not Chrome or Edge. Your browser cookies live in your browser; the desktop client has never seen them. The server gets a plain image fetch with no identity attached. Outlook desktop is also where AEs spend the most time re-reading sent items — proposals, contracts, long threads — so losing self-open detection there is losing it where it matters most.
Gmail proxies every image through Google's servers. When a Gmail tab loads, your browser does not fetch the tracking pixel directly. Google fetches it, caches it, and serves the cached copy. The request hitting my.outsolvi.com comes from a Google data center, not your machine. No cookies from your browser, no IP that ties to you — every Gmail open looks anonymous and identical to every other Gmail open from the server's point of view.
That is why the add-in does the heads-up. It is the only thing already present in both surfaces that knows, from inside the client, that the user opening the email is the same user who sent it.
What counts and what does not
| Scenario | Counts as a real open? |
| Recipient opens the email | Yes |
| You re-read it in Outlook desktop with Outsolvi installed | No |
| You re-read it in Gmail with the Outsolvi extension | No |
| You re-read it in Outlook web with Outsolvi installed | No |
| You re-read it on a colleague's laptop without Outsolvi | Yes — we cannot tell |
| You forward your own sent email back to yourself | Yes — treated as a genuine re-load |
| Apple Mail Privacy Protection pre-fetch on the recipient side | Counted, but tagged Tier 4–5 confidence |
| Corporate scanner or link-checker on the recipient side | Counted, but tagged Tier 5 confidence |
The trade-off on the "colleague's laptop" row is deliberate. Detecting it would need IP fingerprinting that breaks on mobile networks, VPNs, and hotel WiFi. False negatives there cost less than fragile detection logic.
Across most accounts we have looked at, 15–40 percent of historical opens are self-opens. After the backfill runs, your count drops — and the number that remains is one you can act on.