How to Embed a Survey in an Email (Outlook, Gmail, HTML)
Key takeaways
- Email clients strip form tags, so you must build surveys using clickable buttons or linked images that point to pre-filled URLs.
- Outlook desktop uses Word's engine to render emails, requiring you to use its native Microsoft Forms button or degrade to plain text links.
- Gmail and Apple Mail support basic HTML, allowing inline radio buttons or star ratings as long as they are under 600px wide to avoid clipping.
- Embed only the first question in the email to maximize response rates, moving branching logic and open-text follow-ups to a landing page.
- Test your embedded survey across Gmail, Outlook, and Apple Mail before scaling sends because rendering reliability varies by client.
Yes, you can embed a survey in an email, but only three methods work reliably: a Microsoft Forms button in Outlook, inline HTML radio buttons or star ratings built with table-safe markup, and a one-tap first-question link that opens the rest of the survey. Which one you should use depends on whether your list opens mostly in Outlook desktop, Gmail, or Apple Mail, since each renders forms differently.
Can you embed a survey question directly in an email body, and which email clients will render it?
Yes, but only in limited forms: a question with clickable answer options can live inside the email itself, while full interactive forms mostly cannot. Email clients strip <form> tags, so practical embedding means one-click buttons, image-map ratings, or a first question whose taps open a prefilled response. Tools built for this, like One Question, handle the tracking so you don't paste raw HTML by hand.
What actually renders: forms vs links vs buttons
| Method | Gmail | Apple Mail | Outlook desktop |
|---|---|---|---|
<form> element | Stripped | Stripped | Stripped |
| One-click buttons / linked images | Works | Works | Works |
| Embedded web form (iframe) | Blocked | Blocked | Blocked |
Buttons and linked images render everywhere because they're just HTML links. That's why "embedded in the email" in practice means a one-tap first question, not a full survey.
Why Outlook desktop is the constraint
Outlook desktop renders email with Microsoft Word's engine, not a browser, so it ignores modern CSS and interactive elements. Microsoft's own workaround is inserting a poll or Forms survey via a built-in action, which renders as a card rather than raw HTML (Microsoft Support). Design your embed to degrade to plain buttons there.
How do you embed a Microsoft Forms survey in an Outlook email step by step?
The native Forms button in Outlook
Open a new email in Outlook (desktop, Windows), go to the Message tab, and click Forms. Pick an existing form or build one, then insert it. Outlook adds a link plus a preview card showing the first question. You need a Microsoft 365 work or school account, and the button is missing from the Mac client and most web versions, so Gmail and Apple Mail recipients get the link only.
What recipients see and what you can track
The recipient answers inside the Outlook client if they open it there, and responses flow back to your Forms dashboard with names attached (unless you turn that off). Anyone on Gmail, Apple Mail, or mobile apps outside Microsoft sees a link and a thumbnail, which means the in-email experience breaks exactly where most of your list lives. That is the trade-off: zero setup and clean tracking for Outlook-to-Outlook, a plain link for everyone else.
If your list is mixed, a purpose-built tool like One Question keeps the question itself in the email body so one-tap replies work across clients.
How do you build an inline HTML survey embed that works in Gmail and Apple Mail?
Gmail strips <form> elements, so a real HTML form with radio inputs will not submit inside the message. The workarounds are interactive-free: style clickable elements to look like radio buttons or star ratings, and have each one link to a pre-filled URL or mailto that records the answer. Gmail supports basic HTML and CSS in messages (Gmail email rendering documentation), but anything script- or form-based gets dropped.
Radio buttons and image-map ratings that survive clipping
Build each option as a table cell with a border and a link, so one tap on "Great", "Okay", or "Poor" opens a URL like yoursite.com/feedback?rating=great. Keep the whole block under about 600px wide and put the question text above it, because Gmail clips long messages and Apple Mail's preview pane cuts off anything below the fold. Image-map ratings (five stars as one image with clickable regions) render well but die when images are blocked, so always pair them with text links as a fallback.
Dark mode and image-blocking pitfalls
Dark mode can invert your button colors and turn white text on white cells invisible; use dark text on light backgrounds and avoid relying on background images. If images are blocked, your stars vanish, which is why text-based one-tap buttons are the safer default. Tools like Alterable and Survicate handle these quirks for you, or you can hand-roll the HTML and ask us to check it at https://onequestionemail.com/contact.
How do you embed an NPS survey in an email without hurting deliverability?
Why the 0–10 scale works as a one-liner
NPS compresses into a single row of eleven clickable numbers, which is why it embeds better than any multi-question survey. Build it as a one-row table with each score as a link, and keep the whole thing under 100px tall so it survives Outlook's table quirks. The question line ("How likely are you to recommend us?") is plain text, so nothing breaks when styling is stripped.
Link-based fallbacks when images are blocked
Never render the scale as a single image map. Gmail clips large emails and Apple Mail blocks remote images until the reader taps "load images," so an image-based scale reads as a blank box for a chunk of your list. Text-number links with a fallback URL per score still work with images off, and each tap can carry the score in the query string so you know what they picked without a landing page. Ask one follow-up on the page after the tap, not in the email.
Should you embed the full survey or just the first question in the email?
Embed the first question only. Every extra step between the email and an answer costs respondents: one click to a landing page, one page load, then however many questions the form has. An in-email one-tap answer removes all three, which is why the first question gets far more responses than anything behind a link.
The cost of each extra click
The trade-off is rendering. Full forms inside email depend on HTML form support that Outlook desktop does not reliably provide; Litmus documents which CSS and form features each Outlook version supports. A single question rendered as styled buttons or an image-map-style tap target degrades more gracefully than a multi-field form.
When a landing-page survey is the right call
Send respondents to a page when you need more than one or two answers, open-text comments alongside a rating, or consistent tracking across clients. A hybrid works well: one-tap answer in the email, then a prefilled follow-up on the landing page for anyone willing to continue.
What response-tracking do you lose when the survey lives inside the email instead of on a landing page?
What you keep: one-tap responses and open-side signals
You keep the biggest win: the response itself. A one-tap answer inside the email needs no login and no long form, so completion happens almost on the spot. With One Question, the tap opens one short Confirm page, which keeps clicks from email security scanners out of your results. You also still see opens and clicks from your email platform, and a click on an answer button is itself a signal you can track per recipient.
What you give up: branching, partials, and rich metadata
The trade is depth. An in-email answer is usually a single tap, so branching logic ("you picked 3, why?") has to happen on a follow-up page or not at all. You lose partial responses, typed comments tied to a score in one session, and metadata a landing page collects automatically: time on page, device, referrer, and full question sequences. If a respondent taps a score but abandons before any follow-up, you have a number with no reason attached.
For a solo post-purchase check-in, that trade is usually worth it. For a longer CSAT survey with open-text questions, it may not be.
Which embedding method should you choose for your email volume and tool stack?
The decision matrix
Match the method to what you already run. If you live in Outlook and send internal or B2B check-ins, the Microsoft Forms embed is the fastest path and you should accept that Gmail recipients may see a link instead. If you paste HTML into Gmail or Apple Mail sends, use inline radio buttons or a one-tap NPS row, and keep it to a single question so a broken render costs you little. If deliverability is your main worry, remember the practitioner warning that embedded surveys render unreliably across many email clients, which is why some senders abandoned the tactic years ago (HubSpot Community). Low volume and one question: embed it. High volume or multi-question: link out.
Where One Question fits, and where it falls short
One Question is built for the embed-first path: the question sits inside the email, one tap and a short Confirm page record the answer, no login. You can add one optional follow-up question after the vote is confirmed. That suits a solo ecommerce sender running post-purchase CSAT from Gmail. The honest trade-off: you lose the landing-page analytics a full survey tool gives you, and it offers Faces, Yes / No, a 1–5 List and Open text, not a 0–10 NPS scale. The answer buttons are plain HTML links, so they show the same way in Gmail and Outlook.
How do the main in-email survey tools compare?
Tools to shortlist
Five tools do the in-email job: Alterable, Survicate, EnCatch, Responsly, and Zonka Feedback. All let a reader answer inside the email body with one click and no login, which is the whole point of embedding rather than linking out.
For a solo sender, the practical differences are pricing tier shape, which clients each tool guarantees rendering in, and whether you get response tracking per email. Check each tool's own docs for client support before committing, because rendering claims vary and your list's client mix decides the result.
Run any shortlist against the same test: send a real campaign to your own Gmail, Outlook, and Apple Mail addresses, click every answer, and confirm the response lands in your dashboard.