Templates are used as the blueprints for campaigns or as transactional emails. From the Communications tab, select Templates. Next, click "Create New".

Inside the Template Editor, notice the following tabs: Basics, Code, Preview, Text Version, Advanced, Trigger.


  • Public Name is the name of the template that will appear to users if they are opting out.
  • From Name refers to the name the subscriber will see that the email is from in their inbox.
  • From Email must be a verified email address. Click the link to add an email address; an email will be sent to that inbox. Click the link inside the confirmation email, and the address is added to your Sailthru list of verified from email addresses. (Note: you must enter at least one Verified Email in order to use the Preview feature.)
  • Reply-To Email should be a monitored address such as feedback@ or support@. Noreply@ is advised against because it alienates subscribers and they are more likely to mark the email as SPAM.
  • Note that you can use variables in the Subject line to personally target your emails or pull from a data feed. See template markup and coding a feed for more.
  • You must enable Link Tracking for reporting purposes. Click here for details on this and Google Analytics.



  • Add your HTML and inline CSS in the Code tab
  • You may include Zephyr syntax to personalize greetings, and pull in content from a data feed (please see Code a Feed into a Template/Campaign).
  • To add images, click "Image Library" and browse to the images you wish to upload. Select the upload image within the library. The HTML code with image size attributes will automatically add to your code! See details here.
  • Add Zephyr variables
  • Add   {beacon}   to your code for tracking (this is required for reporting). Click here to find out how to change the image.
  • Add {optout_confirm_url} to the <a href> tag of your Unsubscribe link. Note that this variable will autoappend into the code if it is not already present. See zephyr basics for more.
  • Make use of the Find/Replace field for HTML edits
Remember: click "Validate" to check the HTML code against our best practices.


  • When your HTML is in place, click to the Preview tab to see how it renders. Click back to the Code tab to make edits.
  • For templates that contain dynamic content (for example, using Zephyr), you can type in the email address of any of your users in the View As User field and click "Refresh" to see how the template would appear to that user.

Text Version

  • After all your HTML changes are complete, click "Convert HTML to Text". A text version is required to send.
Remember: the alt tags for any images included in the template will appear in the text generated by the "Convert HTML to Text" button. If you don't want them, edit them in the Code tab to read better, or simply remove them from the text version after it has generated, and save.


  • Select the data feed from which to pull content into the template. Note that you must first import a feed.


  • Auto-Append Link Parameters can be set to add query string parameters to every link



  • Triggers are a special type of transactional email based off the send of another email. Details of triggers are available here.


Additional Features


  • New Template - click this button to exit the current template and start fresh with a new one.
  • Rename - click this button to rename your campaign. Then click "Save." Note this is for the internal name only; to change the name that subscribers might see (on an optout page for example) change the Public Name in the Basics tab.
  • Save - click this button to save your campaign. Once your campaign is saved, it will turn grey and say "Saved". 
  • Save Copy As... - click this button to create an identical copy of your template that can be modified separately. (Note this is not related to A/B split testing.)
  • Delete - to delete the template
  • A/B Test - test two versions of a transactional email, use A/B Transactional Testing
  • Test Send - click the 'Test Send' button to send your template to the email address of your choice. We recommend you always 'test send' prior to deploying to check rendering and links.
Note:  If your links are dynamic (contain Zephyr syntax), they will not rewrite in a Test Send. You must do an actual send by a) using the API Test Page POST/SEND call to send to your email b) using your API to send c) building a campaign using build from template and sending to a test list.