Skip to content

Commit 1a2df98

Browse files
rchinn1rchinn1
committed
PM Feedback [netlify-build]
1 parent 9c3da7f commit 1a2df98

File tree

4 files changed

+35
-28
lines changed

4 files changed

+35
-28
lines changed

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

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

148148
## Content validation
149149

150-
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. Engage both flags template issue(s), and displays recommended next steps. You must fix any issues before using your template in Engage campaigns.
150+
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. You must fix any issues before using your template in Engage campaigns.
151151

152152
## Save the template
153153

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ Click **Format** at any time to properly indent and format your code in the HTML
5959

6060
Engage displays in-line error flags in the code editor to help you debug your code. If there are errors, you might not see content as expected in the preview screen until you've debugged your code.
6161

62-
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. Engage both flags template issue(s), and displays recommended next steps. You must fix any issues before using your template in Engage campaigns.
62+
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. You must fix any issues before using your template in Engage campaigns.
6363

6464
## Personalize with merge tags
6565
Add merge tags to personalize your message with user profile traits.

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

Lines changed: 32 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -48,45 +48,52 @@ You can send test emails before you include a template in marketing campaigns.
4848
5. Select **Send test email**.
4949

5050
> success ""
51-
> You can also test email templates directly from a [Send an Email step](/docs/engage/journeys/build-journey/#send-an-email) in Journeys.
51+
> When you send a test message, the trait must be valid for the field it's being used in. For example:
52+
> - If you use `profile.traits.first_name` in the **From sender** field, it must be a valid username.
53+
> - If you use `profile.traits.email` in the **Reply to email** field, it must be a valid email address.
5254
53-
## Personalize with merge tags
55+
> info ""
56+
> You can also test email templates directly from a [Send an Email step](/docs/engage/journeys/build-journey/#send-an-email) in Journeys.
5457
55-
With Engage, you can personalize email content with real-time profile traits.
58+
## Dynamic sender using merge tags
5659

57-
In your template, you can add profile traits in merge tags to the following fields:
60+
Engage supports dynamic sending using merge tags. Personalize email content by adding real-time profile traits in merge tags to the following fields:
5861
- Subject line
5962
- Preview text
6063
- Message body
61-
- [From sender](#use-profile-traits-in-the-sender-and-reply-to-fields)
62-
- [Reply to email](#use-profile-traits-in-the-sender-and-reply-to-fields)
64+
- From sender
65+
- Reply to email
6366

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

66-
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.
69+
{% raw %}
6770

68-
> info ""
69-
> 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.
71+
> success ""
72+
> - For all merge tags, you must add a `default` value inside a single quote. For example: `{{profile.traits.traits | default: 'Default'}}`
73+
> - Only use variable tags in [liquid sytax](https://liquidjs.com/tags/overview.html){:target="blank"}.
7074
71-
### Use profile traits in the sender and reply to fields
75+
The following table contains a description and some best practices for all fields in the email template. Asterisks indicate required fields.
7276

73-
{% raw %}
7477

75-
Personalize your email template by adding profile traits in the **From sender** and **Reply to email** fields.
7678

77-
For both fields, keep the following best practices in mind as you add profile traits.
78-
79-
- To use merge tags, you must add a `default` value inside a single quote. For example: `{{profile.traits.traits | default: 'Default'}}`
80-
- Only use variable tags in liquid sytax.
81-
- Use a valid username for an email address in the profile trait and default value. For example:
82-
- `default: 'jsmith'` is valid
83-
- `default: 'j smith'` is invalid
84-
- When you send a test message, the trait must be valid for the field you're using it in. For example:
85-
- If `profile.traits.first_name` is being used in the **From Sender** field, it must be a valid email username.
86-
- If `profile.traits.email` is being used in the **Reply to Email** field, it must be a valid email address.
87-
- In the **From sender** and **Reply to email** fields, the profile trait and default value must be one of the following:
88-
- A valid email address
89-
- A valid username for the email address (the input field needs to end with a valid domain for the email address)
79+
80+
81+
| Field | Description |
82+
|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
83+
| Template Name* | The email template name. |
84+
| Description | A description for the template. |
85+
| 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 |
86+
| Sender name* | The name users will see next to the sender email. |
87+
| 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) |
88+
| Reply to name* | The name users will see next to the reply-to email address. |
89+
| BCC | Email address that will receive a blind carbon copy of your email campaign. |
90+
| Preview text | A brief message that displays next to the email subject. |
91+
| Subject* | The email subject. |
92+
93+
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.
94+
95+
> info ""
96+
> 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.
9097
9198
{% endraw %}
9299

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Follow these steps to build an SMS template:
3535
Use the SMS Templates screen to preview and update existing SMS message templates.
3636

3737
> info "Engage content validation"
38-
> 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. Engage both flags template issue(s), and displays recommended next steps. You must fix any issues before using your template in Engage campaigns.
38+
> 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. You must fix any issues before using your template in Engage campaigns.
3939
4040
## Test your SMS template
4141

0 commit comments

Comments
 (0)