Elaine provides complementary ways to inspect message variants, deliver a campaign-specific preview message, analyze common error sources, and test email rendering across clients. Use the checks that match the channel and the type of change being released.
Choose the right check
| Check | Primary purpose | When to use it |
|---|---|---|
| Profile preview | Renders a message with selected contact data, placeholders, conditions, and content variants. | While editing and whenever personalization or audience data changes. |
| Campaign preview message | Delivers a preview of the concrete campaign to a controlled email address or test group. It supports campaign approval and can reveal problems in sender settings, links, personalization, or data integration. | For every email campaign before approval and production delivery. |
| Automated email-client preview | Generates screenshots in a selection of email programs and device contexts so teams can compare rendering without maintaining every client themselves. | Especially when a framework template is new or has changed, and after changes to layout-critical modules. |
| Message Analysis | Identifies configured content, structure, and quality findings that can become error sources. | During creation and before approval, with critical findings resolved or explicitly assessed. |
Recommended procedure
- Create representative test contacts for normal, missing-data, language, consent, and branch edge cases.
- Use profile preview to inspect the relevant personalized and conditional variants.
- Run Message Analysis and resolve findings that could affect content, links, accessibility, structure, or delivery.
- For email, send a campaign-specific preview message and verify the received message, sender, subject, preheader, links, tracking, data integration, and fallbacks.
- For a new or changed email template, run the automated email-client preview and compare its screenshots across the supported clients and devices.
- Repeat affected checks after corrections and retain evidence when the approval workflow requires it.
How the checks complement each other
A campaign preview message validates one concrete campaign and its current data and settings. An automated email-client preview focuses on the visual behavior of the underlying email markup across programs and is therefore particularly useful for template quality assurance. Neither replaces the other, and screenshots do not validate live data integration or every behavior of an interactive element.
Note
Exact UI labels, client coverage, availability, and behavior can depend on the Elaine.io release, licensed capabilities, permissions, channel, and project configuration.