E-mail templates
For example, you can create a generic e-mail that includes an e-Marketing Spot. The logic defined in the e-Marketing Spot is evaluated when the e-mail is created. This results in content that can be different depending on the customer segment to which the customer belongs. For example, the e-Marketing Spot might display an image which is specific to a particular customer segment. Other elements that can be defined in general, and then rendered at the time the e-mail is being created include the individual addresses of the target customer segment, the subject, the reply-to e-mail address, and finally the body of the e-mail. Any of these pieces of information can be changed dynamically according to your business needs.
In an extended
site model, the extended store’s e-mail
template list displays the e-mail activity templates created in the
extended
store and its asset stores. However, the e-mail activity templates
created
in the asset stores are read-only. This allows asset stores to define
e-mail
templates that can be used by any extended site, helping to ensure
a consistent
look and feel for e-mail activities sent by the extended sites. For
example,
if an e-mail template named ET1 is created in the asset store, it
is listed
in the extended store’s e-mail template list, and available for use
as the
basis of an e-mail activity. However, if a user selects the ET1 and
clicks Change or Delete,
the user receives an alert message that the action is not allowed.
If your store has enabled workspaces, e-mail
templates
may be managed using workspaces and inherit the benefits from that
feature.
Specifically, your e-mail templates become managed assets, and are
subject
to your workflows.
Related concepts