Gmail Adds Image Caching + Stops Image Blocking: What You Need to Know

[ 24 By
NOTE: New information on changes to Gmail have been made public since this article was first published. The article has been updated to reflect that new information.

Google has introduced a number of features to Gmail lately. Along with tabs in the new inbox and an updated mobile client, you can add image caching and automatic enabling of images to the list of changes that affect email marketers.

On December 5th, Laura Atkins reported on the Word to the Wise blog that Gmail was now caching images and serving them via their own proxy servers—a potentially game-changing update that could affect marketers who rely on images to track email opens or geolocation for dynamic content.

So what is really going on and how does it affect you?

How Images Are Used in Email

Beyond their visual appeal, images serve a very important function in email marketing. Images are used to track email opens and engagement while providing marketers with valuable data about when, where, and how their campaigns are being read.

Email tracking relies on a unique image being included in a campaign and that image being downloaded and displayed within the email. Every time the image is downloaded from the server, the tracking software marks that as an email open. Combined with things like click tracking and site analytics, open tracking via images helps give marketers a comprehensive view of how people are interacting with their campaigns.

To count opens reliably, software tools need those images to be downloaded every time someone opens an email.

Enter: Image Caching

When an image is cached, it is downloaded from the original server and stored on a proxy server. Subsequent views of the cached image will always display from the proxy server rather than the original server, effectively re-routing all the image downloads along with the associated tracking data that comes with the image download. Gmail has started caching images for users accessing Gmail via the webmail interface: images are viewed only once on the original server while successive views will originate from the cached image on Google’s proxy servers.

The Gmail team explained some of the reasoning behind the change in a recent blog post. Product Manager John Rae-Grant sums it up by saying:

Your messages are more safe and secure, your images are checked for known viruses or malware, and you’ll never have to press that pesky “display images below” link again.

Email designers will be delighted to know that Gmail displays images by default. While we still suggest using alt text for images, it’s nice to know that messages will display as intended, and that image blocking is no longer an issue for Gmail users.

Safer emails with images enabled are wonderful for Gmail users, but Google’s new image caching still poses a number of problems for email analytics tools. The unique image downloads that tracking software looks for will no longer occur. Some analytics tools will only see the initial download by Google and won’t record subsequent opens regardless of how many times a reader opens that email.

Some marketers also use geolocation to personalize email messages. They look at where the image is downloaded and feed users dynamic content based on their location. With Gmail’s new image caching behavior, geolocation could effectively break. Instead of being able to see where a reader is located, these services will see where Google’s proxy server is located—resulting in dynamic content tailored to the proxy server’s location.

When did these changes go into effect?

While it looks like Gmail’s image caching changes were released around December 4th, we have evidence of Google caching email images as far back as October. It’s possible that Google was testing the caching system on a small segment of Gmail users, or with employee email accounts before rolling it out to all users. Automatic image downloads were enabled in a waved roll-out starting December 12th, affecting some users sooner than others.

Does this affect all Gmail users?

Google’s image caching only affects users accessing their email through the web interface and the mobile Gmail app. People that use desktop and non-Gmail mobile apps to access their Gmail accounts will still download images from the original server, not Google’s proxy servers. The same goes for image blocking: Gmail users reading mail on an iPhone or iPad likely didn’t have images disabled to begin with, although folks logging into gmail.com will now see images automatically unless they take action to re-enable image blocking.

Fortunately, the number of people that use the Gmail web interface is declining. Only 20% of Gmail users access their email in a browser via gmail.com. Mobile access accounts for 68% of Gmail opens, with desktop accounting for the remaining 12%.

While these changes initially only rolled out to gmail.com addresses, they have extended to include custom domains using Gmail as well.

Does device detection still work?

Yes and no. Device tracking will still work when an email is opened in a non-native Gmail client. For instance, device tracking will work for an email sent to a @gmail.com address that is opened in Apple Mail, Outlook, the mail client on iOS, etc. Device tracking will not work for emails opened in the gmail.com interface in a web browser, or using an official Gmail mobile app. In other words, device tracking still works in the places where Gmail is not caching images.

What Does This Mean for Email Analytics?

If you’re not already using Email Analytics for learning about your audience, you should start. Email Analytics (EA) provides valuable insights into your audience and how they are engaging and interacting with your email campaigns.

Like all other email analytics services, EA relies on readers downloading a unique image to start tracking an email. With these changes to the way Gmail handles and displays images, EA users will see a few changes to their reports. To be clear, these changes only apply to emails opened in native Gmail clients. Reporting remains unaffected for emails sent to Gmail accounts that are opened in non-Gmail email clients.

  • There is now a “Using Google Cache” metric in Email Clients reports, showing initial opens from Google’s caching service.
  • Forward and print tracking won’t work via Gmail due to image caching.
  • EA users will see the IP address or location of Gmail proxy servers.
  • Users may see a higher occurrence of “Other” opens from the time period that Google started testing image caching until we updated our reporting logic on December 6th.

With these updates to Gmail, it is crucial to use individual tracking with Email Analytics in order to properly record analytics. Without individual tracking, Gmail will see the image in your tracking code as the same image for all recipients—and that tracking image will be cached along with the other images in your email. This means that only the first open using that tracking code will be recorded and you’ll see very few opens for Gmail. Using a unique identifier allows us to properly track email opens, even when Gmail is caching images.

Will I see more opens? Less?

It’s hard to say just yet. Due to image caching, Email Analytics will track the first open from each user, in that browser/device. Subsequent opens in the exact same browser/device will not be tracked, because the pixel will be cached for that individual user at that point in time. You’ll continue to see unique opens from each subscriber, however total opens may be impacted. For example: if hello@litmus.com opens in Gmail in Chrome, then using the Gmail app on iOS, then Gmail in Chrome again, EA will track one open in Gmail in Chrome and one open in the Gmail app on iOS.

There has been a lot of misinformed mainstream press and concern over Gmail opens decreasing. Since tracking relies on an image being downloaded and displayed, and Google is now displaying all images by default, it is possible that Gmail opens will actually increase. Once those images are cached, however, repeat opens and total opens will likely decrease, since the tracking image will only be downloaded once.

So while we may see fewer total opens as compared to before Gmail rolled out image caching, the automatic display of images will mean that more of those initial or unique opens will be tracked. The number of Gmail users on your list, combined with their preferred email client, will definitely play a factor.

Some of my images look funny since the roll-out. What’s up with that?

There have been a few reports of degraded images for Gmail users. While we haven’t witnessed the problem first hand, a few of our Community members have seen already compressed images further compressed by Google, leading to compression artifacts and images of low quality.

The final word

Google’s new image caching and image blocking rules came as a big surprise to most marketers. As with any new development in the world of email, we will be keeping an eye on how it develops and will update this post and our monthly Email Client Market Share stats accordingly.

Additional Resources

  • skeenery

    Has anyone else seen issues with these cached images horribly mangling the original image?

    Here’s a quick side-by-side comparison of what Gmail did to a gif in a recent campaign:
    https://i.imgur.com/eCwQifF.png

    The image on the left is referencing the asset intended, the second is an “unnamed.gif” Gmail generated.

  • orliesaurus

    I don’t see how individual tracking will bypass the caching mechanism set by Google; you still won’t know if the email has really been opened if Google caches the 1 by 1 pix image on their servers regardless whether I have “really” opened it or not

    • http://www.litmus.com Justine, Litmus

      Individual tracking inserts a unique ID into the tracking pixel, making the tracking pixel unique to each user. Therefore Google won’t cache one image across all the subscribers in your campaign. You will still just see one unique open for each user, but the alternative (if not using individual tracking) would be seeing one open across ALL gmail users on the campaign.

      • orliesaurus

        Okay, is this confirmed working? That’s what I m using right now: Each user has its own uniquely generated pixel… so I should be safe right?

        • http://www.litmus.com Justine, Litmus

          Yes, this is confirmed to be working. Each user will not have their own *pixel* but rather, the unique ID being appended to the pixel will make it appear unique to Gmail. Email Analytics will track the first open from that user, in that browser/device. Subsequent opens in the exact same browser/device will not be tracked, because the pixel will be cached for that individual user at that point in time. You’ll continue to see unique opens from each subscriber, however total opens may be impacted. For example: if hello@litmus.com opens in Gmail in Chrome, then using the Gmail app on iOS, then Gmail in Chrome again, we will track 1 open in Gmail in Chrome and 1 open in the Gmail app on iOS.

          • orliesaurus

            Gotcha, I read about different implementations with “pixels” etc but I get your point, super cool, thanks!

  • Sahil

    Hi Justine,

    As per my knowledge, appending the useragent by google is against the rule of HTTP RFC 2616. Cant you guys contact google about this.

    • http://www.litmus.com Justine, Litmus

      If you know someone at Google we can contact, let us know!

  • http://www.dennisoneil.com Dennis O’Neil

    Litmus has been reporting a steady decline in Gmail opens for a while now. Android gets beat by the iPhone and iPad (two devices that display images by default).

    Does anyone else think this move is partially motivated by a desire to improve the appearance of Google products in these email client reports?

    Yeah, we may not be able to track re-opens, but I’m happy to trade that in order to know every single recipient who opens the email gets to see all the graphic goodness – increasing the likelihood for a click conversion, and allowing me to track that view.

  • lucanos

    I just read the Google Blog post referred to in this article ( http://gmailblog.blogspot.com.au/2013/12/images-now-showing.html ). It does not mention anywhere that the images will be cached.

    It does say that they will be served through a Google proxy, but a search for “cach” shows no matches on the page.

    Where did you get the information that the images are cached? Are they supposedly being cached server-side or client-side? Or is this an assumption on your part?

    • http://www.litmus.com Justine, Litmus

      We’ve seen the caching behavior through testing—the images are only pulled from the proxy once, and not on subsequent views/opens.

  • http://www.andykuiper.com/ Andy Kuiper – SEO Analyst

    lots of intrigue here… I hope G is very transparent in the reasoning on this one

  • http://www.artshighway.com/ Artist3d

    If you own your domain, use your @mydomain.com email — gmail/hotmail/yahoo email addresses are ‘free’ services used to track and profile consumers and their use of keywords in their communications. Avoid using them if you can, the content you create with them is not confidential. Cloud services are also suspect, if you own your own domain and a hosting account that is probably the best place to ‘cloud store’ your content. Most web hosting accounts now come with infinite storage and bandwidth included with the website space. Most Internet providers also provide at least one private email address anyway.

  • andrew

    “Your messages are more safe and secure,” Um, since when do we *not* say “safer and more secure”? Amazing.

    • http://www.litmus.com Justine, Litmus

      Sounds like Gmail is confident that malicious messages are no longer an issue for their users—I’ll take that as a good sign for email in general!

  • Rajinder kumar Aggarwal

    After this update, I get the same URL that is mentioned in the post, however my image is not displayed in my email. What should be done to get my image display back

    • http://www.litmus.com Justine, Litmus

      We’ve heard a few other scattered reports of this happening, but nothing consistent enough to tie down a solution. It could be that Gmail’s image proxy servers were experiencing a momentary uptick in traffic—it seems to resolve itself if the image/email is reloaded.

  • Pingback: Gmail Continues to Shift the Market Share Landscape | Litmus | SoShake