Skip to content

Commit c30f541

Browse files
pwsegpwseg
authored
Merge pull request #5411 from segmentio/Engage-content-updates
Engage content updates [DOC-733]
2 parents 340091b + f17f2a8 commit c30f541

File tree

4 files changed

+40
-5
lines changed

4 files changed

+40
-5
lines changed

‎src/engage/campaigns/email-campaigns.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,7 @@ Some email campaign fields, like **Sender email** and **Subject**, are required.
5050
> info "Editing Templates"
5151
> If you use a template for your email, Engage creates an editable copy of the original. Editing the template within the Journey won’t alter the original template.
5252
53+
5354
### Send an email to all users
5455

5556
As you create your email campaign, you can set an email to send to all users regardless of their [subscription state](/docs/engage/user-subscriptions/#the-four-subscription-states). This may be useful, for example, when you need to send a marketing transactional email to a user who hasn't subscribed to your marketing emails.

‎src/engage/content/email/editor.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -153,6 +153,7 @@ To view more examples related to your use case, visit the [LiquidJS docs](https:
153153

154154
For all content editors in Engage, you'll see alerts for any issues in your template, such as invalid profile traits or incorrect [liquid syntax](https://liquidjs.com/tags/overview.html){:target="blank"}. Engage both flags template issue(s), and displays recommended next steps. While you can save these templates, you must fix any issues before using them in Engage campaigns.
155155

156+
156157
## Save the template
157158

158159
After you design the email, click **Create Email Template**.

‎src/engage/content/email/template.md

Lines changed: 37 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -21,10 +21,10 @@ To configure an email template, click **Create Template**.
2121
2. Configure the email template.
2222
1. Add a template name for internal reference.
2323
2. Add an internal description.
24-
3. Enter the sender email address.
24+
3. Enter the sender email address. You can optionally include profile traits.
2525
- Emails can only be sent from verified domains.
2626
4. Enter the sender name.
27-
4. Indicate if you want replies sent back to the initial sender. If not, add a "reply to" email and name.
27+
4. Indicate if you want replies sent back to the initial sender. If not, add a "reply to" email and name, or include profile traits.
2828
5. Add email addresses to receive a blind carbon copy of your email.
2929
6. Add preview text and the subject line. Use [merge tags](#personalize-with-merge-tags) to personalize the email template with real-time profile traits.
3030
3. Select the design method to build your email template:
@@ -55,15 +55,45 @@ You can send test emails before you include a template in marketing campaigns.
5555
5656
{% endcomment %}
5757

58+
5859
> info ""
5960
> You can also test email templates directly from a [Send an Email step](/docs/engage/journeys/build-journey/#send-an-email) in Journeys.
6061
61-
## Personalize with merge tags
62-
Personalize email content in Twilio Engage with real-time profile traits in your email subject line, preview text, and message body.
62+
## Dynamic sender using merge tags
6363

64+
Engage supports dynamic sending using merge tags. Personalize email content by adding real-time profile traits in merge tags to the following fields:
65+
- Subject line
66+
- Preview text
67+
- Message body
68+
- From sender
69+
- Reply to email
6470

6571
As you configure the template, click **Merge Tags** and select the profile traits to include. Engage inserts the merge tags based on cursor placement.
6672

73+
{% raw %}
74+
75+
> success ""
76+
> - For all merge tags, you must add a `default` value inside a single quote. For example: `{{profile.traits.traits | default: 'Default'}}`
77+
> - Only use variable tags in [liquid sytax](https://liquidjs.com/tags/overview.html){:target="blank"}.
78+
79+
The following table contains a description and some best practices for all fields in the email template. Asterisks indicate required fields.
80+
81+
82+
83+
84+
85+
| Field | Description |
86+
|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
87+
| Template Name* | The email template name. |
88+
| Description | A description for the template. |
89+
| From sender* | The email address users will see in the from field of the email campaign. <br><br> For the profile trait and default value, use a valid username. For example: <br> - `default: 'jsmith'` is valid <br> - `default: 'j smith'` is invalid |
90+
| Sender name* | The name users will see next to the sender email. |
91+
| Reply to email* | The email address that will receive any replies users send. You can use different Sender and reply-to email addresses. Email recipients will see this address if they reply to your campaign. <br><br> The profile trait and default value must be one of the following: <br> - A valid email address <br> - A valid username for the email address (the input field needs to end with a valid domain for the email address) |
92+
| Reply to name* | The name users will see next to the reply-to email address. |
93+
| BCC | Email address that will receive a blind carbon copy of your email campaign. |
94+
| Preview text | A brief message that displays next to the email subject. |
95+
| Subject* | The email subject. |
96+
6797
You can also add merge tags in the heading or body text as you design an email with the [Drag and Drop](/docs/engage/content/email/editor/) or [HTML](/docs/engage/content/email/html-editor/) editors. Engage supports [liquid templating](https://liquidjs.com/tags/if.html){:target="blank"} to create dynamic content in the email design editor.
6898

6999
### Use liquid statements with an image URL
@@ -76,7 +106,9 @@ To use liquid statements with an image, Segment recommends using an [**HTML bloc
76106
{% endraw %}
77107

78108
> info ""
79-
> To learn more about profile traits, visit Segment's [Computed Traits](/docs/engage/audiences/computed-traits) and [SQL Traits](/docs/engage/audiences/sql-traits/) documentation.
109+
> To learn more about profile traits, visit Segment's [Computed Traits](/docs/unify/traits/computed-traits) and [SQL Traits](/docs/unify/traits/sql-traits/) documentation.
110+
111+
{% endraw %}
80112

81113
## Include unsubscribe and manage preference links
82114

‎src/engage/content/sms/template.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,7 @@ Use the SMS Templates screen to preview and update existing SMS message template
3737
> info "Engage content validation"
3838
> For all content editors in Engage, you'll see alerts for any issues in your template, such as invalid profile traits or incorrect [liquid syntax](https://liquidjs.com/tags/overview.html){:target="blank"}. Engage both flags template issue(s), and displays recommended next steps. While you can save these templates, you must fix any issues before using them in Engage campaigns.
3939
40+
4041
## Test your SMS template
4142

4243
Send a test SMS message before you include it as a step in your Journey.

0 commit comments

Comments
 (0)