Before launching a template into production, send a test email to yourself. Catching rendering issues, broken tokens, or formatting problems in a test is much cheaper than discovering them after the first 100 real users have received the broken version.
From the template editor
Each E-mail Template has a Send Test button. Click it and you get a small dialog asking for:
- Recipient — your own email address.
- Sample row (optional) — a specific row from the relevant datastore to populate the merge tokens with real data. If left blank, tokens get sample values like "[Sample Customer Name]".
The platform sends the test message using the same path as a real send — same template, same E-mail Account, same merge processing. So if it looks right in your inbox, it'll look right for real users.
What to check in the test
1. Subject line
Does it render correctly with substituted tokens? Is it the right length (under ~60 characters for good inbox preview behaviour)? Does it pass spam-filter sanity checks (no excessive punctuation, no all-caps)?
2. Body HTML
Does it display as expected? Check both light-mode and dark-mode email clients — many email apps invert backgrounds in dark mode, which can break designs that assume white backgrounds.
3. Links
Are they clickable? Do they point to the right URLs? Are tokens correctly substituted (no literal ##URLTOKEN## appearing)?
4. Images
Do they load? Configure them as absolute URLs to your site (not relative paths — relative paths break when the email is opened on the recipient's mail server, not yours).
5. Plain-text alternative
Many email clients (and some recipients) prefer or require the plain-text version. The platform auto-generates one from the HTML — check it makes sense (no orphan tags, links shown as full URLs).
6. Spam score
A tool like mail-tester.com gives a quick spam audit. Forward your test email to the address they provide and they'll score it 0-10 with specific advice on what to improve.
Three real-world test patterns
Pattern 1: Final-design review
After completing a new template, send a test to a small review group (3-5 people). Each views in their preferred email client. Collect feedback on rendering, tone, length, and any issues that catch the human eye.
Pattern 2: Multi-client check
For templates that'll go to consumer audiences, test in Gmail (web and mobile), Apple Mail, Outlook (web and desktop). Each has slightly different CSS support and quirks. Litmus and Email on Acid are paid tools that automate this across many clients.
Pattern 3: Token-substitution check
For templates with many tokens, test with a sample row that has values in every relevant field. Spot any tokens that aren't substituting (rendering literally) or substituting incorrectly (wrong field, escape issues).
Tip: Make test-emails part of your template change workflow. Every meaningful template edit should be followed by sending one test to yourself before considering the change done. The 30 seconds it takes to send and review prevents the embarrassing "hi ##FIRSTNAME##" emails everyone receives at some point.