What We Know About Google AMP for Email (And How It May Affect Your Campaigns)

Last Updated on September 26, 2022 by 14 Comments

What We Know About Google AMP for Email (And How It May Affect Your Campaigns)
Blog / General News / What We Know About Google AMP for Email (And How It May Affect Your Campaigns)

It’s been almost two years since the launch of the Google AMP Project. Its aim from the start was to help foster better web standards, which could result in an improved mobile experience for users. Now, the project is turning a new leaf and expanding towards email, which brings us to how this shift might affect you.

AMP for email is still in development and we don’t know what the finished product will look like yet. However, what we do know enables us to paint a decent picture of how the project could affect email marketing. In this article, we’ll discuss how the AMP Project has evolved since its creation and what it means for email. We’ll then talk about how you can prepare for the launch of AMP for email. We’ve got a lot of ground to cover, so let’s get to it!

An Update on the Google AMP Project

The AMP Project homepage.

Google AMP launched in 2016 to some controversy, but the project is still moving along.

We talked about the AMP Project shortly after it launched in 2016, including some instructions on how to integrate it with WordPress. In case you need a refresher, the project is an initiative meant to improve the overall performance of the mobile web. To do that, it aimed to foster a lightweight framework that would result in faster-loading websites.

Since those early days, over 25 million domains have launched AMP content. Furthermore, Google wants to convince the group in charge of web standards to adopt technologies similar to AMP. In the meantime, they’ve also been busy with the launch of Web stories and the development of AMP for email. If you are interested in integrating stories into your website, check out our overview and review of the Google Web Stories plugin.

However, while AMP development forges ahead, there are a lot of people worried about what it means for the future of the web. Some are concerned that Google wants to favor AMP articles. Since this content is only accessible through Google’s applications, it mostly benefits the people that choose to adapt to the company’s guidelines.

Additionally, some people argue it stands in contrasts with the ideals of an open web. Others have gone on to suggest some changes AMP could adopt, so it doesn’t favor Google’s ecosystem. For now, the discussion continues, and Google’s AMP for email project only gives us more food for thought.

What AMP for Email Is

The AMP for email announcement page.

Just as its parent project, AMP for email has also stirred passions since its announcement.

AMP is nothing if not ambitious, and now the project wants to tackle another critical aspect of the web – email. The goal of AMP for email is to provide you with the tools to create more engaging and actionable messages. For example, when you open an AMP-enabled email, you’ll be able to complete specific tasks without opening a website. Those include RSVPs, scheduling appointments, or even running simple applications.

Another feature that AMP for email promises is the ability to include self-updating information within messages. For example, you could book a flight and your confirmation email would always include relevant up-to-date information, such as warnings about delays. This would also enable you to send promotional emails that update to reflect when the sale is over, to avoid confusion.

So far, AMP for email is still in its beta phase. You can gain access to it through the Gmail Developer Preview of AMP for Email program if you want to test it in advance. Some companies, such as Pinterest and Booking.com, are already working on how to use AMP for email to their advantage. However, as great as the project’s new features sound, not all people are as excited about it.

A recent Techcrunch article argues that email’s main selling point is its simplicity. If you take email and add new features to it, you’re going to run into interoperability issues. This is a valid point since AMP for email is set to launch later this year, only for Gmail users. It’ll be up to other clients and providers to decide if they want to support AMP emails, which is bound to complicate things somewhat.

Another potential downside of the AMP for email project is it extends Google’s control over the content you see even further. For example, without AMP emails, you’d be forced to open a new page if you wanted to RSVP to an event or schedule an appointment. Now, a lot of people won’t need to leave Google’s email ecosystem to do that, just like with AMP pages. Couple that with the fact that Gmail is one of the leading email platforms and these drastic changes become even more troublesome.

Finally, there’s also the glaring issue that performance isn’t such a big deal when it comes to email versus websites. In most cases, the emails we get don’t take that long to load by design, as most providers have a maximum size limit. That means AMP for email’s primary goal is not performance oriented but adding new features to a medium that already works. In fact, adding all that new functionality to emails may end up slowing their performance. However since the project is still in development, it may not be time to panic just yet. Instead, what you can do is consider how it’ll affect you.

How to Prepare Your Campaigns for AMP for Email

There are two ways you can go about testing AMP for email in its current version. If you’re a developer, you can apply to Gmail Developer Preview of AMP for Email program. You will need to sign a Non-Disclosure Agreement (NDA) if you get in, so keep that in mind:

The AMP for email project.

However, since AMP is an open source, you can also review its specs by checking out the project’s repository. The difference, in this case, is you won’t be able to test the code using a beta version of Gmail, as you would signing up for Google’s developer preview. So far, you can check out AMP for email’s proposed design:

<!doctype html>
<html amp4email> <!-- `amp4email` also accepted. -->
 <meta charset="utf-8">
 <style amp4email-boilerplate>body{visibility:hidden}</style>
 <script async src="https://cdn.ampproject.org/v0.js"></script>
Hello, world.

Technically, this template will support AMP for email elements that only compatible clients will display. Other clients will still be able to render emails using regular HTML. In other words, you’d be creating two versions of each email you send out to your users. One email displaying AMP and the other using standard HTML. That is, of course, if you want to jump on the AMP bandwagon.

So far, Google has only confirmed support for a few AMP elements. Those include forms, selectors, lists, accordions, carousels, sidebars, light-boxes, images, and animations. Regular AMP supports more elements. However, these are some of the ones that Google has deemed secure for email environments. If you want to check out how your campaigns would translate to AMP, you can try out the AMP Playground using the project’s email template:

The AMP Playground.

There, you’ll be able to test all the elements you want. This will give you a practical idea of what your campaigns could look like using AMP.


The AMP Project caused a stir when it launched in 2017. It’s still a controversial project, but it’s made some decent headway since its inception. More than 25 million domains have already started publishing AMP content, and Google are still increasing the project’s scope.

With AMP for email, Google managed to stir up even more feelings. Adding complex elements to email using a new framework may lead to compatibility issues, and AMP emails may even end up being less lightweight than their standard counterparts. Even so, you should take the time to prepare for what AMP for email may bring, as it’s sure to have an effect on your campaigns in the future.

What do you think about the Google AMP project and its expansion into email? Share your thoughts with us in the comments section below!

Article thumbnail image by Sammby / shutterstock.com


Want To Build Better WordPress Websites? Start Here! 👇

Take the first step towards a better website.

Get Started
Premade Layouts

Check Out These Related Posts

Divi 5 And The Move Away From Shortcodes

Divi 5 And The Move Away From Shortcodes

Updated on September 29, 2023 in General News

I’m back with another Divi 5 update! As you may know, we are in the midst of a massive project recreating the Divi Builder, focusing on foundational improvements such as performance and extendability. I give a quick update every month to keep the community informed about our progress. Last month,...

View Full Post
Announcing Divi 5 Dev Beta

Announcing Divi 5 Dev Beta

Posted on August 22, 2023 in General News

I’m back with another Divi 5 update, and this time I am pleased to announce the release of Divi 5 Dev Beta, the next phase in the Divi 5 beta program. The Divi 5 foundation is complete, our development documentation is filling out nicely, and we have used the Dev Alpha phase to collect...

View Full Post


  1. Wow really interesting post John! It’s true that the compatibility across multiple clients will definitely be the crux of the issue here. This is great for people who use gmail but Microsoft and Outlook … well that’s just another question all together isn’t it!

  2. I’ve experimented with AMP in the past. It essentially requires you to set up two sets of website code, one for AMP and one for everything else. The AMP pages are dumbed down (no JS, no comments, etc.). It’s a major burden to setup and to maintain.

    But the biggest disappointment is that visitors never visit your website. Instead they see a copy of your AMP page served from a Google server.

    In my opinion, AMP is a bad user experience since the user sees a page without features we work hard to add. It’s also bad for website owners, since the whole objective is to drive engagement, but the visitor seldom arrives on the real website. It’s also bad for website owners in that the cost to build and maintain is significantly increased.

    Google claims the benefit of AMP is decreased load times. Our websites typically load in a second or less. For my clients in the USA, who are all on 4G or better, this is plenty fast enough.

    I pray AMP does not get accepted as a standard. The only beneficiary is Google.

  3. So what’s the actual benefit ?

  4. Instead of Amp for Email, how about moving HTML emails away from tables and over to CSS and create standards? As someone who’s spend a great deal of time as part of my career in Email Marketing that to me is more important than this.

    • I couldn’t agree more. I had to stop offering email marketing services because every time I would build a custom newsletter and run it against litmus, it displayed as correct. Once it would hit the inbox it would be fried depending on the service it was sent from even though it passed the litmus test for the same exact service provider. I have gotten so fed up with it that I won’t build them anymore and outsource the work.

  5. I’ve been in email marketing for 10 years, hand coding emails in HTML and dealing with all the variables; Outlook sucks because it uses Word as its backend, Google waited until recently to NOT strip out your header CSS and now Google wants us to just fall in line and start using their script?

    Until emails, like the web world has already done, gets a standardization there’s no way I’m going to bend to the whims of one to the possible detriment of all the others.

  6. Google is an ingenious company who has shaped the way we use the web. On the other hand they have been well compensated for their creativity. They are also being well compensated for buying up other people’s patents, (creativity), such as YouTube.

    I have been affiliated with several companies which were put out of business. A. because Google either had a better idea, or B. Bought out someone who did. Let’s list a few; 1. Kooday, (2011, a competitive search engine where you could “Own” a keyword/phrase. 2. Photomax, (2005, a competitor to Snapfish), and YouTube before the Google acquisition.

    Sometimes this is just sour grapes over a big company buying out a smaller one to acquire their patents. Other times a great idea was thrown under the bus because the 52, billion company could easily pay $300,000,000.oo ,or even a billion to eliminate a competitor that could move them from #1 to #2 in the market. In Google’s case, Kooday represented a 30 to 40 billion shift in how we create small businesses. Would you pay 2% of Your net to stifle that? (If YOU were #1 ?)

    The question is; . . . does stifling proven, good ideas benefit You, Your nation, or mankind in general ? (That’s a rhetorical question Dummy.)

    Or does it benefit the Giant corporation? Need help deciding? Try buying an ‘Adword’ for your next campaign.

    Next try to compete without cheap/effective email marketing. Mr. Hughes article is more important than it may appear to someone who is more techy than Business. Think About It!

    Do You Jet?

  7. When Windows desktops were the only game in town — and app developers had to deploy on Windows, Microsoft employed a strategy (and tactic) that was referred to as “Embrace and extend”. In other words, embrace a standard, then extend it to make a somewhat proprietary M$ centric “standard.”

    Google is doing the same with AMP. Granted, there are benefits and it is an open source initiative.

    I’m not in favor but may have to get on the bus one day.

  8. AMP is bad, no one needs another standard to follow controlled by a large company like Google.

  9. How does Divi work with AMP? You referred to the other article, but it is isn’t related to Divi. Do Divi websites still work when you use the plugins mentioned in the other article? Is ET planning to support AMP without the need of other plugins?

    • Divi doesn’t work with AMP. Becoming AMP-compliant requires installing an AMP plugin, which essentially creates separate “template”. You then insert your logo, set colors, and so on. Javascript (and jQuery) are not permitted. That means comments are out. Forget about any animations. You get the idea.

  10. I tried AMP on my travel blog in mid 2017, but later on decided to revert all the changes. Not using it anymore, and honestly can’t see the point of AMP email.

    • I experimented also around the same time. After several months, I deleted everything. Big disappointment.

  11. Personally I don’t like AMP, however if you can’t beat the them you may as well join them!! LOL. So AMP here I come 🙂

Leave A Reply

Comments are reviewed and must adhere to our comments policy.

Get Started With Divi