GMail will now always show images by default
gmailblog.blogspot.com
gmailblog.blogspot.com
Looks like submitter missed this in the post:
Of course, those who prefer to authorize image display on a per message basis can choose the option “Ask before displaying external images” under the General tab in Settings. That option will also be the default for users who previously selected “Ask before displaying external content”.
Probably worth updating the HN title to reflect this.
Here's MailChimp's analysis: http://blog.mailchimp.com/how-gmails-image-caching-affects-o...
Pretty effectively spoils Litmus and others though.
If the latter, sender image tracking will be alive and well.
<img src="image.jpg?userid=123456"/>
and I can tell whether you opened it or not. Google could strip out query strings in their proxy, but I'm not sure that's a good idea.By loading images automatically, this tracking will again be possible. However, Google may be getting around this by loading all images on receipt by the Gmail servers and then caching them as the blog mentions. That way a sender will only be able to track that the email made it to Google, not whether the end user actually viewed it or not.
When you actually want to be marketed to, it makes it easier for the sender to tailor their content -- and I do for some markets want to get the tailored stream.
Why not leave comments to comment section and use original post titles instead.
I've now modified the title to not include the (Tracking always!?) text at the end.
Simple: your messages are more safe and secure, your images are checked for known viruses or malware...
Unless I missed something. I read it twice. Can anyone point to text that says otherwise.Is all email open tracking broken now? Good thing for users, not so good for email marketing campaigns/tools.
Was hoping some gmail devs would comment here. The blog entry didn't have comments enabled.
I'm assuming at this point that that would still work. But as mentioned in the Movable Ink article all sorts of other tracking and image request headers are lost.
If it is the latter, users can still be tracked. If the former, legitimate uses that help users will now be blocked. Github, for example, uses a tracking dot to mark a notification as read if you read it via email, which means you don't get double notified on the Github UI and via email.
It's unclear if this technique will work against the new GMail approach; maybe Google will always fetch all images as soon as the mail arrives, which would immediately ruin any signal.