My knowledge might be outdated but back in 2014? Gmail decided to download and cache images embedded in an email. This meant that a tracking pixel was only downloaded once (before a user even opened an email) and every subsequent time the email was opened, the cached image was served from Gmail's servers, not the image origin server. This meant that tracking pixels became useless for Gmail (web based) users. I'm still under this impression today but maybe something has changed?
Edit: I said the pixel loads before the email is even opened. This is incorrect. The pixel loads the first time an email is read. Subsequent loads come from Gmail's servers.
I get why people do this. I used to use Freshbooks for my billing. They include tracking pixels in their emails, so I could see if a client had opened their invoice or not. If a client was late, I could adjust my behavior based on that tracking pixel (if they hadn't seen it, I would just send the invoice again vs. calling and trying to hound down a payment).
That said, I don't like the idea of tracking pixels either. I turn off images in gmail/thunderbird so that people can't track my reading. Would love it if the move to get rid of these became mainstream.
The Gmail image setting is all wrong, though — it also blocks inline images.
The correct solution is trivial if Google cared to implement it: never load remote content in emails. If Google did this, then people would stop including remote content. Problem solved.
This is a valid use case, and it's a service you can get with snail mail, by sending it as "certified". Except for the fact that emails aren't particularly private, it seems reasonable that the same thing could exist for important emails. But if so, the fact that it's tracked should be as clearly exposed to the recipient as the certified snail mail envelope. Although that might not be possible to implement on top of email.
Standard email marketing best practice is to use this to see if the recipient is opening emails. If the recipient doesn’t, the sender should auto unsubscribe the recipient. Blocking tracking pixels means that the “good” email marketers will keep emailing until a manual unsubscribe event happen.
Surely blocking tracking pixels looks just like not opening the email, triggering the autounsubscribe. I don't see the problem here. The recipient and mailer both get what they want.
Ideally what I want is for all of my e-mail clients to programmatically identify spy images and auto send a form letter on my behalf. Unfortunately, I don’t always have a choice what email client I use. My work forces me to use Outlook for work emails (I have to be on my company VPN and I have to authenticate through OKTA before viewing them).
In my opinion, Hey never actually took off because unlike Basecamp which is great, feels like it was used by the team that made it before they actually launched it. Hey feels clunky and incoherent IMHO.
What if they are used directly by the business owner purely to make your experience better and improve their business and not fed into some big ML data-eating machine?
This looks like an advertisement for hey.com. It's a good service that I used for about a year. But what I really wanted was a better email client and not a new email address.
I'm not seeing a connection between Dave Smyth (https://davesmyth.com/) and Hey. I think he just mentions it because of it supports surfacing "spy pixel" use.
[+] [-] tppiotrowski|3 years ago|reply
Edit: I said the pixel loads before the email is even opened. This is incorrect. The pixel loads the first time an email is read. Subsequent loads come from Gmail's servers.
[+] [-] xiaomai|3 years ago|reply
[+] [-] cdot2|3 years ago|reply
[+] [-] xiaomai|3 years ago|reply
That said, I don't like the idea of tracking pixels either. I turn off images in gmail/thunderbird so that people can't track my reading. Would love it if the move to get rid of these became mainstream.
[+] [-] amluto|3 years ago|reply
The correct solution is trivial if Google cared to implement it: never load remote content in emails. If Google did this, then people would stop including remote content. Problem solved.
[+] [-] b3morales|3 years ago|reply
[+] [-] lzooz|3 years ago|reply
[+] [-] fuegoio|3 years ago|reply
On one side, I prefer consent, limiting the amount of analytics made on me and I don't like giving my behavior for free.
On the other side, I work in a Tech startup and we need to know what users are doing / thinking. It is so important to iterate and grow quickly.
So it is the kind of stuff where I would like it to disappear, but at the same time I am a bit digging my grave.
[+] [-] andrei_says_|3 years ago|reply
I use pihole and nextdns and hey.com email, all aggressively resisting advertising and targeting.
At the same time my coworkers need to report on opens and click through in their email campaigns.
[+] [-] svnpenn|3 years ago|reply
[+] [-] bberenberg|3 years ago|reply
[+] [-] vageli|3 years ago|reply
[+] [-] JohnFen|3 years ago|reply
[+] [-] teaearlgraycold|3 years ago|reply
[+] [-] cf100clunk|3 years ago|reply
https://tutanota.com/faq#load-images
[+] [-] beebeepka|3 years ago|reply
[+] [-] kobalsky|3 years ago|reply
if it matters they can embed the content and the images will display even if you have remote images disabled.
[+] [-] irrational|3 years ago|reply
[+] [-] dang|3 years ago|reply
We Built a Meta Pixel Inspector - https://news.ycombinator.com/item?id=33753498 - Nov 2022 (1 comment)
[+] [-] dikaio|3 years ago|reply
[+] [-] XCSme|3 years ago|reply
[+] [-] pastyboy|3 years ago|reply
[+] [-] cf100clunk|3 years ago|reply
[+] [-] nicolaslem|3 years ago|reply
[+] [-] jdlyga|3 years ago|reply
[+] [-] MarcoZavala|3 years ago|reply
[deleted]
[+] [-] photoGrant|3 years ago|reply
"If you use Hey"... And close tab.
What's more nefareous? Being advertised to through the regular channels, or this covert, hidden as help type of swindle? I hate both.
[+] [-] CharlesW|3 years ago|reply