Easy HTML guide: Review
Review essential best practices for launching Recurly email templates with this comprehensive QA checklist, covering merge tag rules, safe fallback fonts, testing protocols, and next steps for your automated subscription communications.
Review & resources
Check what you learned and find every link in one place.
Navigation Menu
Nice work
You can now edit Recurly's email header and footer, use merge tags, style safely, and test before anything goes live.
Check your understanding
Question 1 of 3 · Multiple choice
What do you do with a merge tag such as {{account_email}}?
See answer
Leave it exactly as written. Recurly replaces the tag with the subscriber's data when it sends the email.
Question 2 of 3 · Multiple choice
Why should every font stack end with Arial or Helvetica?
See answer
Gmail and Outlook for Windows ignore custom fonts. A safe fallback keeps your layout intact.
Question 3 of 3 · Exercise
Apply it to one email
Pick one template, add your logo and footer, send a test to a colleague, and open it in Gmail and Outlook. What is the first thing you would fix?
Best practices checklist
Before you go live
Updated about 1 hour ago
Did this page help you?
Review & resources