Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Configuring email treatments

Updated on August 4, 2022

The Subject field allows the user to specify the subject for the email. The email subject can be static text, a property reference, or an expression which combines both static text and property references.

Pega Customer Decision Hub

The user can also utilize the Key Code field to specify a code for the Email Treatment. This code can be used by downstream functionality, such as the Send Email shape in the action canvas.

When the Track Email Open Rate checkbox is enabled, the system automatically captures email opens (impressions) in Interaction History. This setting is enabled by default in a new Email Treatment.

The Email Treatment Editor enables the user to design high quality treatments to send to customers. This editor supports two modes of editing:

  • Design – This is the default editing mode. In this mode, users can enter free-form content and use a wide array of editing tools to format this content. To apply formatting to content; select the content first and then, use the formatting icons to update the content’s format.
  • Source – This mode is for advanced users and provides direct access to the source HTML for this treatment. In this mode, the formatting icons are disabled.

Users can switch between the two modes above by toggling the Source button:

The editor also includes an array of buttons to insert content (such as links, images, properties, etc.) into the treatment:

Two of the buttons in this array are essential in designing effective customer-focused treatments. These are further outlined below.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us