| Audience | Marketers, lifecycle and CRM teams |
| Prerequisites | An email message with content |
Preview renders your email against real profiles from your warehouse, so you see what a recipient sees before you send.
Preview against a real profile
In email, open the Preview tab. In SMS, the preview sits beside the editor and updates as you type.
Either way, the message renders with a real profile that matches your audience. Variables show actual values. Email shows the subject and pre-header above the body. SMS shows the link in its shortened form.
The Profile panel on the right shows the attribute values behind the render. From there you can:
- Shuffle sample profile to render a different person.
- Preview a specific profile to search for one by name or identifier.
- Edit an attribute value in place to see how an edge case renders, such as a very long product name. This changes the preview, not the data in your warehouse.
- Reset profile to return to the profile's real values.
Check the values your email depends on
The Variables sidebar lists each variable used in the message alongside its most common values across your audience. Step through them with Back and Next to see how the email renders for each.
Use it to catch a layout that breaks on a long value, or a fallback that never fires.
Send a test
| Channel | How to send |
|---|---|
| In the Profile panel, open Actions and select Send a test message. Enter an address. | |
| SMS | Select Send test… from the ⋯ menu or above the preview. Enter a phone number. |
The test renders with the previewed profile's data, so personalization appears as it will in the real send. Sending a test requires a sender identity on the message.
For SMS, read the test on a phone. That's where you'll see how a long message splits and how the link renders in a real messaging app.
A test email doesn't check subscription status or send limits. It goes to the address you enter.
Check how it renders across mail clients
Select View device previews from the Actions menu to render the email across common clients and devices. Use it to confirm how dark mode, mobile widths, and image-blocking clients render.