11–20 of 341 posts
I can't think of any email clients that automatically download external images by default. The article seems to be over-blowing the issue a bit.
Gmail does. This is great for privacy because it destroys the usefulness of the tracking pixel to the marketer.
I can't think of any email clients that automatically download external images by default. The article seems to be over-blowing the issue a bit.
I just found it turned on. I forgot to disable it again after my annual OPSEC-cosplay device-wipe.
I can't think of any email clients that automatically download external images by default. The article seems to be over-blowing the issue a bit.
GMail displays them. It uses a proxy for downloading, but I don't think that matters unless they're preloading all images unconditionally upon server-side receipt of the message. Apple's macOS Mail.app client displays external images by default, as does their iOS app.
I can't think of any email clients that automatically download external images by default. The article seems to be over-blowing the issue a bit.
Gmail does. This is great for privacy because it destroys the usefulness of the tracking pixel to the marketer.
https://jioegijogeijesgioegeg.tracking.example.com/niowefioe.png?sdgsdbuegiu=rojpopwmrmwk
Does Gooogle's proxy remove all of them?
Earlier quoted context omitted.
Gmail does. This is great for privacy because it destroys the usefulness of the tracking pixel to the marketer.
Eh... Not really... It's pretty easy to generate a unique image url per customer and use that to determine whether a customer opened the mail or not and it's about the same cost as a traditional tracking pixel, complexity-wise.
I can't think of any email clients that automatically download external images by default. The article seems to be over-blowing the issue a bit.
Earlier quoted context omitted.
Eh... Not really... It's pretty easy to generate a unique image url per customer and use that to determine whether a customer opened the mail or not and it's about the same cost as a traditional tracking pixel, complexity-wise.
Indeed, the three email tracking services I'm familiar with (HubSpot, Yesware, and Outreach) all generate unique URLs per recipient. The only information you don't get for Gmail clients is location, but you get the most valuable info which is if/when/how many times the email is opened.
Earlier quoted context omitted.
Gmail does. This is great for privacy because it destroys the usefulness of the tracking pixel to the marketer.
Eh... Not really... It's pretty easy to generate a unique image url per customer and use that to determine whether a customer opened the mail or not and it's about the same cost as a traditional tracking pixel, complexity-wise.
I can't think of any email clients that automatically download external images by default. The article seems to be over-blowing the issue a bit.
Earlier quoted context omitted.
Indeed, the three email tracking services I'm familiar with (HubSpot, Yesware, and Outreach) all generate unique URLs per recipient. The only information you don't get for Gmail clients is location, but you get the most valuable info which is if/when/how many times the email is opened.
I remember reading that gmail caches these images, rendering the how-many-times useless.
While their cache is large, it's not infinite. If what you're interested in is whether a customer engages with an email multiple times over a few days, you'll likely get the pixel hits to confirm it over that time period. Of course, as you imply, you wouldn't be able to collect how many times an hour a single customer has viewed an email sent to them.