Interactive email lets recipients do something inside the message rather than clicking through to a page — answer a poll, browse a carousel, complete a form, add to a cart. It has been the next big thing in email design for about a decade, which should tell you something.
The honest position is that a small subset works reliably, a larger subset works in some clients with fallbacks, and the most ambitious version requires infrastructure most senders will not build.
The three tiers
CSS interactivity. Achieved with the checkbox hack — a hidden input with :checked selectors driving visibility. Accordions, tabs, image carousels, hover effects. No JavaScript, so it passes filtering that would strip anything scripted.
Works in Apple Mail and some webmail. Does not work in Gmail, which strips the necessary attributes, or Outlook on Windows, which does not support the selectors. So you are building for roughly the same audience that gets your web fonts.
AMP for Email. A Google-backed framework allowing real dynamic content — live data, forms that submit, content that updates when the message is opened rather than when it was sent. Genuinely capable.
The cost is real. You must register as a sender with each provider that supports it, send a text/x-amp-html part alongside your HTML and text parts, host and maintain the AMP endpoints, and comply with each provider's requirements. Support is limited to Gmail, Yahoo and Mail.ru, and Apple Mail — the client most receptive to everything else on this page — does not support it at all.
Enhanced fallbacks. Not interactivity, but the thing most senders actually want: an email that looks live because it was assembled at open time. A dynamically generated image showing current stock, a countdown timer rendered server-side as a GIF, a personalised image built per recipient. These work everywhere images work, which is most places.
What is worth building
Countdown timers. Server-rendered as an animated image, they work in nearly every client and genuinely lift urgency-driven campaigns. The cheapest interactive-feeling element available.
Live content images. An image URL that generates the current content when requested — remaining stock, a live leaderboard, today's price. Works because it is just an image.
A single-question poll. Implemented as several links, one per answer, each pointing at a URL that records the response and lands on a thank-you page. Not technically interactive and functionally identical from the reader's point of view, with none of the client support problems. This is the version to build.
Accordions for long content, in an email where the audience is Apple-heavy and the fallback — everything expanded — is acceptable.
What is not
Forms in email. The fallback problem is severe: a form that does not render leaves either nothing or a broken box, and forms are exactly what security gateways and filters treat with suspicion. Link to a page.
Add-to-cart in email. Requires AMP or a provider-specific integration, breaks in most clients, and the click-to-page path is not the bottleneck in the purchase anyway.
Anything requiring JavaScript. Stripped by every mail client. Not a support gap — a deliberate security decision that will not change.
Complex carousels. High build cost, works in a minority of clients, and the fallback is usually a stack of images that would have been fine on its own.
The question worth asking first
Interactive email is usually pitched on engagement lift, and the reported gains are real in the clients that support it. But the comparison that matters is not interactive-versus-static. It is interactive-versus-what-else-you-could-have-built-with-that-time.
For nearly every sender, an afternoon spent on segmentation or on building an abandoned cart flow returns more than an afternoon spent on a carousel that renders for a third of the list. Interactive email is a refinement for programmes that have already done the fundamentals, and it is very often pursued by programmes that have not.
If you build it
- The fallback is the design. Build the non-interactive version first, make it complete, then layer the interaction on top for clients that support it.
- Test the fallback more than the enhancement, because more people see it.
- Check dark mode and images off — interactive elements often fail both.
- Watch the file size. Gmail clips messages past roughly 102KB, and interactive markup is verbose. See why your email looks broken in Outlook.
- Keep it accessible. Checkbox-hack interactivity is frequently invisible to screen readers.
Frequently asked questions
Does AMP for Email still work?
It works in Gmail, Yahoo and Mail.ru for senders who register and maintain the required infrastructure. Apple Mail does not support it, and adoption among senders has stayed low because the setup cost is high relative to the audience reached.
Which email clients support interactive email?
Apple Mail supports CSS-based interactivity most reliably. Gmail strips the attributes the checkbox technique depends on, and Outlook on Windows supports neither. AMP has a different and non-overlapping support list.
Is interactive email worth the effort?
For most senders, no — not before segmentation and automated flows are in place, which return more for the same effort. Server-rendered countdown timers and live-content images give most of the perceived benefit at a fraction of the cost and work nearly everywhere.
Can I put a form in an email?
You can, and it will fail for most recipients and look suspicious to filters and security gateways. Link to a page built for the form instead; the extra click is not what is costing you completions.
