Live view links
Every MailInApp email has a live view: the same email rendered as a hosted web page, fully interactive, with zero JavaScript required. It is the universal fallback tier in the three-tier fallback engine — whatever a recipient's inbox can't render, one tap opens the real thing in their browser.
Where live view appears
- Fallback CTAs — static-tier blocks link to the live view: "Vote", "See the collection", "Open the form" all land on the interactive version of that email.
- "View in browser" — the classic escape hatch, powered by the same page.
- Studio preview — the Live view ↗ button in the studio toolbar opens your project's live view, so you preview exactly what recipients get.
Recipients never need a MailInApp account, an app, or a login — the link simply works.
Security model
Live view links are signed capability URLs:
- Each link carries a signed token scoped to one email project — and, when the email is personalized, to one recipient row, so each recipient sees their own personalized page.
- Links minted from the studio are valid for 30 days; tampering with the token invalidates it.
- Live view pages send no referrer information and are marked
noindex, so tokens don't leak through analytics or search engines.
Treat a personalized live view link like the email itself: anyone the recipient forwards it to can see that email's content.
Scanner-proof interaction recording
Corporate security gateways and link scanners (Outlook SafeLinks and similar) prefetch every link in an email — which would corrupt your poll results if a bare click were enough to record a vote. MailInApp is built so that a GET request never records an interaction:
- Link-based actions from the email land on a lightweight confirmation step; the interaction is recorded only on the recipient's explicit confirming action.
- Interactions on the live view itself are recorded through form posts, which scanners don't trigger.
The result: your analytics reflect humans, not security bots. More in Interactions & analytics.
After an answer
A recipient's answer lands them on the live view. With one block that takes an answer, the page thanks them: "Thanks — your response was recorded." When the email asks for answers in two or more blocks, the page shows their progress instead ("1 of 3 answered"). A Next question link goes to the first block they haven't answered, and each one they have shows an Answered mark. After the last answer it shows the final message, or, if you set a redirect, the last answer opens your own https:// page instead.
The studio's Responses panel sets which blocks count, the final message and the redirect. See Collecting an answer to every block.