Live data from Hacker News

Email tracking pixel support

rant.gulbrandsen.priv.no

1–10 of 15 posts

Re: Email tracking pixel support

#2
Why are tracking pixels still even a thing. Wouldn't this all be solved is the top 3 mail providers would just decide to hit all embedded resources at the moment a message is received and proxy or even cache it after? This would render this method ineffective for the vast majority of receivers

Re: Email tracking pixel support

#3
post #2

Why are tracking pixels still even a thing. Wouldn't this all be solved is the top 3 mail providers would just decide to hit all embedded resources at the moment a message is received and proxy or even cache it after? This would render this method ineffective for the vast majority of receivers

In order to proxy/cache it they would have to rewrite https resources in user mail to point at their servers. Technically possible but a PR nightmare for little gain to them.

Re: Email tracking pixel support

#5
post #2

Why are tracking pixels still even a thing. Wouldn't this all be solved is the top 3 mail providers would just decide to hit all embedded resources at the moment a message is received and proxy or even cache it after? This would render this method ineffective for the vast majority of receivers

I thought google started doing this years ago https://gmail.googleblog.com/2013/12/images-now-showing.html

Re: Email tracking pixel support

#6
post #5
post #2

Why are tracking pixels still even a thing. Wouldn't this all be solved is the top 3 mail providers would just decide to hit all embedded resources at the moment a message is received and proxy or even cache it after? This would render this method ineffective for the vast majority of receivers

I thought google started doing this years ago https://gmail.googleblog.com/2013/12/images-now-showing.html

They might be proxying it, but it still only gets hit once you open the mail as I can remember after sending myself a testmail a while back, embedding an image and watching the webserver logs.

Re: Email tracking pixel support

#7
post #2

Why are tracking pixels still even a thing. Wouldn't this all be solved is the top 3 mail providers would just decide to hit all embedded resources at the moment a message is received and proxy or even cache it after? This would render this method ineffective for the vast majority of receivers

In order to proxy/cache it they would have to rewrite https resources in user mail to point at their servers. Technically possible but a PR nightmare for little gain to them.

They do this already. Similar to Github’s Cameo service for proxying readme images.

Re: Email tracking pixel support

#8
post #7

Earlier quoted context omitted.

In order to proxy/cache it they would have to rewrite https resources in user mail to point at their servers. Technically possible but a PR nightmare for little gain to them.

They do this already. Similar to Github’s Cameo service for proxying readme images.

Wow, I just checked and yep there it is - google URL! I wonder if it caches automatically or only when read. If the latter I bet you could game the system by sending a tracking pixel with a unique source URL. Will have to stand up a test server and see what resource gets requested when.

Re: Email tracking pixel support

#9
post #7

Earlier quoted context omitted.

They do this already. Similar to Github’s Cameo service for proxying readme images.

Wow, I just checked and yep there it is - google URL! I wonder if it caches automatically or only when read. If the latter I bet you could game the system by sending a tracking pixel with a unique source URL. Will have to stand up a test server and see what resource gets requested when.

It varies by the reputation of the domain. Most images get hit once when the email is initially opened, and cached basically forever. If you send tons of tracking pixels to multiple users you'll eventually see the images being loaded and cached as soon as you deliver the message.

Re: Email tracking pixel support

#10
post #6
post #5

Earlier quoted context omitted.

I thought google started doing this years ago https://gmail.googleblog.com/2013/12/images-now-showing.html

They might be proxying it, but it still only gets hit once you open the mail as I can remember after sending myself a testmail a while back, embedding an image and watching the webserver logs.

Only if you enable images for the email.

If you don't enable images, the tracking pixel is never retrieved.

Post reply on HN