2018: AMP for Email: Google's Bold Bet on Interactive Inboxes

In March 2018, Google announced a technology that was supposed to be the most significant evolution of email since HTML formatting: AMP for Email. The pitch was seductive. Emails wouldn’t just be static documents you read — they’d be interactive mini-applications where you could RSVP to events, browse product catalogs, fill out surveys, and complete tasks without ever leaving your inbox.

It was bold, technically impressive, and — as it turned out — almost nobody wanted it.

The Vision

AMP, which originally stood for Accelerated Mobile Pages, was a Google-backed framework for building fast-loading web content. It had gained traction (and controversy) in the web publishing world since its 2015 launch. Bringing AMP to email was Google’s attempt to extend the framework into the messaging space.

The concept was demonstrated with impressive examples. An email from an airline could display a real-time flight status widget. A retail email could contain a browsable product carousel with current prices and inventory. A meeting invitation could include an interactive RSVP widget that updated the calendar without opening a new tab. A survey email could collect responses right in the inbox.

Technically, it worked by adding a third MIME type to emails. Traditional emails contain plain text and/or HTML. AMP emails added a third version — text/x-amp-html — containing AMP markup that supported a subset of web functionality including form submissions, image carousels, and dynamic content loading.

The Reality

The problems started immediately and compounded over time.

Client support was anemic. For AMP emails to work, the receiving email client had to support the AMP MIME type. Google controlled Gmail, so Gmail supported it. Yahoo Mail signed on. Mail.ru, the largest email provider in Russia, joined as well. But Apple Mail — used by hundreds of millions of people — didn’t support it. Microsoft Outlook — dominant in corporate environments — didn’t support it. The vast majority of the world’s email clients simply ignored the AMP content and rendered the HTML fallback.

For email marketers, this meant that building AMP emails was building a special interactive version that would only work for a subset of recipients. Everyone else would see the plain HTML version. The effort-to-reach ratio was, for most teams, unfavorable.

Implementation was complex. Building AMP emails required learning a new markup language, handling the additional MIME type in email infrastructure, and registering with Google as an approved AMP sender. The registration process required proving domain ownership, meeting sending reputation requirements, and getting explicit approval. For small businesses and individual senders, this was a significant barrier.

Security concerns were real. The traditional email security model relies on emails being essentially static documents. An email in your inbox yesterday is the same email today. AMP emails, by contrast, could load dynamic content from external servers — meaning the content of an email could change after it was delivered. This raised concerns about phishing, tracking, and content manipulation that the email security community was not comfortable with.

The use cases were narrow. The demo scenarios — interactive RSVPs, real-time pricing, in-email forms — were genuinely useful but addressed problems that most organizations solved through other means. Link to a web page for RSVP. Link to the current product catalog. Send a follow-up email with a link to a survey form. These weren’t elegant solutions, but they worked across every email client, and that universal compatibility trumped interactivity for most senders.

Who Actually Used It

Despite limited adoption, AMP for Email found some genuine use cases. Google itself used it extensively in its own products — Google Docs comment notifications in Gmail allow users to reply directly from the email using AMP. Pinterest built AMP-powered emails that let users browse and save pins without leaving Gmail. Some e-commerce companies experimented with interactive product browsing.

The most practical application turned out to be forms and surveys. Companies like Google Forms, Doodle, and some enterprise feedback platforms used AMP to let recipients respond without clicking through to a web page. For use cases where the response rate matters — internal company surveys, event RSVPs within organizations where everyone uses Gmail — the friction reduction was meaningful.

The Broader Pattern

AMP for Email fits a pattern in email technology that goes back decades. Every few years, someone proposes making email more capable — richer formatting, interactive elements, embedded applications — and every time, the combination of client fragmentation, security concerns, and the raw simplicity of email-as-document pushes back.

Microsoft tried interactive email with TNEF (Transport Neutral Encapsulation Format) in the 1990s. Various proposals for embedded JavaScript in email were floated and rejected. Even basic CSS support remains inconsistent across email clients. The lesson is consistent: email’s strength is its universality, and universality requires simplicity. Every feature that requires client support fractures that universality.

Where It Stands

AMP for Email is not dead, but it hasn’t fulfilled Google’s ambitions either. Google continues to support it in Gmail. A small number of high-volume senders use it for specific, high-value interactions. But it hasn’t become a standard part of email marketing the way responsive design or dynamic content personalization have.

The irony is that the interactive email features users want most — confirming an appointment, approving a request, answering a quick question — would be genuinely useful if they worked everywhere. But “if they worked everywhere” is the whole problem. In email, partial adoption means practical irrelevance for most senders, and AMP for Email has never solved the adoption equation.

Email remains, in its essence, a document delivery system. And for most purposes, that’s enough.

Infographic

Share this visual summary. Right-click to save.

Frequently Asked Questions

What is AMP for Email?

AMP for Email is a Google technology that allows emails to contain dynamic, interactive content. Users can take actions like RSVPing to events, browsing product carousels, or filling out forms directly within the email, without opening a browser.

Why hasn't AMP for Email been widely adopted?

Limited email client support (mainly Gmail and Yahoo Mail), complex implementation requirements, security concerns about dynamic content in emails, and the need for senders to register with Google have all hindered adoption.

Which email clients support AMP for Email?

As of 2025, AMP for Email is supported in Gmail (web and mobile), Yahoo Mail, and Mail.ru. Apple Mail, Outlook, and most other email clients do not support it.