Using Email Templates and Email Content Together

The email templates created in the Email Template Builder are used in Lightning Experience and Account Engagement Lightning App.

In Lightning, a template made in the Email Template Builder is a basic layout that contains default content. You can use it as a starting point for customizing future email messages, or send it as-is. An email content record contains metadata and content that’s used for one or more email sends.

Note If you use a Lightning web component in an email template and that component is updated, you need to save the email template again to reflect the change.

Information about classic email templates is also available: Classic Email Templates.

Email Templates Usage and Reporting

The Email Template Builder is available for use by Account Engagement, Sales Cloud, and Service Cloud users. In Account Engagement, you can select an email template as the basis for creating an email content record. Sales and Service users can send their templates in a few ways, such as in Sales Engagement or the docked composer.

Standard reports for email templates include engagement metrics and usage. In Account Engagement, engagement metrics appear in the Email Content related list on an email template record.

Email Content Usage and Reporting

The drag-and-drop builder for email content is available in Account Engagement only. Email content records created in Account Engagement can’t be shared to Sales or Service users.

Note If you update an asset to reference a new Email Content record, reporting is bundled under the original Email Content record. If a given asset contains multiple Email Content record references, reporting for each Email Content record is aggregated rather than reported separately.

Engagement metrics for marketing emails appear in several places including the Email Sends related list, Engagement History, and List Email reports. You can review metrics on a specific send record or look at aggregate metrics on an email content record. Metrics for operational emails aren't included in the Email Sends related list or Engagement History.

Example Marketing manager Gina creates an event invitation template that provides space for a banner, logistical information, and RSVP button. For brand consistency, she adds her company’s default header and footer. She names it Template: Event Invitations. Later, the event specialist, Kamal creates an email content record for an upcoming meet-and-greet at a local restaurant. When he starts building the email, he selects Gina’s template to work from. He fills in specific content in each area: an image from their last meet-and-greet, the restaurant name, the event time and date, and the link to where he’s tracking RSVPs.

Example A few sales reps tell Gina that they also want to invite people to the meet-and-greet. She and Kamal create another email template with the event information. They name this public template Event Invitation: July Meet-and-Greet. Now the finalized template appears to all the sales reps so that they can send it directly to their leads and contacts.