Template Options for Email

This document describes configuration options for email templates.

# Table of contents

# Creating and editing templates

To learn how to create templates, read Creating Base Templates. To learn how to edit, clone, preview and delete templates, read Managing Base Templates.

# Email Template tab

The Email Template tab provides basic configuration options for email templates:

• Template Name - The name of the template. Provide a name that will help you find the template when you need it later (for example, when you're setting up a campaign). Used for internal reference only.

• Message Type - The message type associated with this template.

  IMPORTANT

  • If you select a message type associated with a marketing channel (as opposed to transactional), the template must comply with the CAN-SPAM Act. Make sure to provide an unsubscribe link.
  • To learn how to provide an unsubscribe link, read Universal Merge Parameters.

• Enable Dynamic From Email - To have campaign templates based on this base template use different senders for different recipients, enable this option. For details about how to set this up, read Dynamic Sender Email Addresses.

• From Email - The email address to use for campaign templates based on this base template. To learn how to add email senders to your Iterable project, read Add senders.

• From Name - The from name to use for campaign templates based on this base tempate.

• Reply-To Email - The reply-to address to use for campaign templates based on this base template.

• Subject Line - The subject to use for campaign templates based on this base template. Use merge parameters to customize this field with user profile or data feed data as necessary.

• Preheader Text - The preheader text to use for campaign templates based on this base template. Preheader text appears alongside the subject line, providing additional context to readers. If you leave this field blank, email clients will display the first text in the email body. Use merge parameters to customize this field with user profile or data feed data as necessary.

• CC - An email address to CC each time a campaign sends a message based on this base template. Iterable CC's this address for each recipient of a campaign. This field is designed to be used for CRM email addresses.

• BCC - An email address to BCC each time a campaign sends a message based on this base template. Iterable BCC's this address for each recipient of a campaign. This field is designed to be used for CRM email addresses.

# Advanced Options tab

The Advanced Options tab provides further configuration options for email templates:

• Enable Google Analytics URL Tracking - Appends utm_source, utm_campaign, and utm_medium to links for Google Analytics tracking. For more information, read Integrating Iterable with Google Analytics. and Google's Collect Campaign Data with Custom URLs document.

• Enable Template Generation Using Data Feeds - Enables customization of the template with data feeds (external web services). For more information, read Personalizing Templates with Data Feeds. Enabling this option causes various other data feed-related options to appear:

  • Cache Data Feed Response... - This option causes Iterable to cache responses to the data feeds referenced by the template (to reduce load on the servers that host them). For each recipient, Iterable determines the data feed URL to query by substituting parameters from their Iterable profile into the data feed's pre-defined URL. If Iterable has a cached response for that URL from within the past hour, it will use that data. Otherwise, it will query the URL.

  • Merge the Data Feed and User Contexts - Allows the template to reference data feed data with double curly braces ({{productName}}) instead of double square brackets ([[productName]]). Doubly curly braces can still be used to reference user profile data, too. If the same field exists on both the user profile and the data feed, Iterable uses the value from the user profile. With this option enabled, a merge parameter can prefer user profile data but otherwise revert to data feed data.

  • Use Data Feed Alias - Allows the template's content to reference data feeds by their aliases. Using aliases can make templates easier to read and maintain, especially when they reference multiple data feeds. To learn how to define data feed aliases, read Editing a data feed's alias. To learn how to use data feed aliases to reference data, read Using aliases to reference data feed data.

• Enable Custom Link Parameters - Causes the template to add custom query string parameters (of your definition) to the links included in the template's content. These parameters can be used to track data such as the recipient's email address and the campaign's ID. For more information, read Custom Link Parameters.

• Convert CSS Styles from the <head> Element into Inline Style Attributes - Converts CSS styles found in a template's <head> tag to inline styles. Useful for imported templates that contain styles in a <head> tag.

• Show Guidelines for WYSIWYG Editor - Shows guidelines in the WYSIWYG editor.

# Email editor

The email editor sits below the template configuration options:

The specific editor you'll see depends on which one was selected when the template was originally created. For more information, read Template Editors.

# Additional options

Below the template editor, you'll see various additional options:

• To see the template's revision history, click See Revisions.
• To export the template as HTML, click Export as HTML.
• To see the template's spam report, click Check Spam Report.
• To clone the template to the same project, click Clone Template.
• To send a proof of the template to yourself (with your own data), as random users (to yourself, but using data from random contacts in your project), to an internal list, or to someone else, click Send Proof and select an option. For more information, read Sending Proofs.
• To preview the template with user data, or to view how it will look on various devices, click the Preview button and select an option.

# Further reading

• Template Options for In-App Messages
• Template Options for Push Notifications
• Template Options for SMS
• Template Options for Web Push Notifications