You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/engage/campaigns/email-campaigns.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,6 +50,9 @@ Some email campaign fields, like **Sender email** and **Subject**, are required.
50
50
> info "Editing Templates"
51
51
> 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.
52
52
53
+
> success "Engage content validation"
54
+
> For all Engage content editors, you'll see alerts for any issues in your template, such as invalid profile traits or incorrect liquid syntax. Engage flags the template issues that require your attention before proceeding, and displays recommended steps to fix the issue.
55
+
53
56
### Send an email to all users
54
57
55
58
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.
Copy file name to clipboardExpand all lines: src/engage/campaigns/sms-campaigns.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,6 +45,9 @@ Follow these steps to create an SMS campaign:
45
45
4. Enter your campaign content into the **Body** field.
46
46
5. Add a STOP/unsubscribe line to the end of your SMS.
47
47
48
+
> success "Engage content validation"
49
+
> For all Engage content editors, you'll see alerts for any issues in your template, such as invalid profile traits or incorrect liquid syntax. Engage flags the template issues that require your attention before proceeding, and displays recommended steps to fix the issue.
50
+
48
51
> warning ""
49
52
> Unsubscribe options are required by law. Your SMS campaign must contain “Reply STOP to unsubscribe.”
Copy file name to clipboardExpand all lines: src/engage/content/email/editor.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -145,6 +145,10 @@ For example, use `{% if %}`, `{% elseif %}`, and `{% else %}` tags to call a pr
145
145
146
146
To view more examples related to your use case, visit the [LiquidJS docs](https://liquidjs.com/tags/if.html){:target="blank"}.
147
147
148
+
## Content validation
149
+
150
+
For all Engage content editors, including the Drag and Drop Editor, you'll see alerts for any issues in your template, such as invalid profile traits or incorrect liquid syntax. Engage flags the template issue(s) that require your attention before proceeding, and displays recommended steps to fix the issue(s).
151
+
148
152
## Save the template
149
153
150
154
After you design the email, click **Create Email Template**.
Copy file name to clipboardExpand all lines: src/engage/content/email/html-editor.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,10 +55,12 @@ Click **Format** at any time to properly indent and format your code in the HTML
55
55
> info ""
56
56
> When you toggle from the HTML editor to the visual editor, Engage may make minor changes to your code formatting. If Engage re-formats your code, it will not affect the email layout.
57
57
58
-
### Error flagging
58
+
### Error flagging and content validation
59
59
60
60
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.
61
61
62
+
For all Engage content editors, you'll see alerts for any issues in your template, such as invalid profile traits or incorrect liquid syntax. Engage flags the template issues that require your attention before proceeding, and displays recommended steps to fix the issue.
63
+
62
64
## Personalize with merge tags
63
65
Add merge tags to personalize your message with user profile traits.
Copy file name to clipboardExpand all lines: src/engage/content/email/template.md
+30-4Lines changed: 30 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,17 +21,20 @@ To configure an email template, click **Create Template**.
21
21
2. Configure the email template.
22
22
1. Add a template name for internal reference.
23
23
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.
25
25
- Emails can only be sent from verified domains.
26
26
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.
28
28
5. Add email addresses to receive a blind carbon copy of your email.
29
29
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.
30
30
3. Select the design method to build your email template:
31
31
-[**Drag and Drop Editor**](/docs/engage/content/email/editor/) is a drag and drop WYSIWYG tool with customizable content blocks.
32
32
-[**HTML Editor**](/docs/engage/content/email/html-editor/) contains both a code and visual editor from a single view. This editor provides complete HTML editing access with error flagging.
33
33
4. Design the email template, then click **Create Email Template**.
34
34
35
+
> success "Engage content validation"
36
+
> For all Engage content editors, you'll see alerts for any issues in your template, such as invalid profile traits or incorrect liquid syntax. Engage flags the template issues that require your attention before proceeding, and displays recommended steps to fix the issue.
37
+
35
38
## Test the Email template
36
39
You can send test emails before you include a template in marketing campaigns.
37
40
@@ -48,15 +51,38 @@ You can send test emails before you include a template in marketing campaigns.
48
51
> You can also test email templates directly from a [Send an Email step](/docs/engage/journeys/build-journey/#send-an-email) in Journeys.
49
52
50
53
## Personalize with merge tags
51
-
Personalize email content in Twilio Engage with real-time profile traits in your email subject line, preview text, and message body.
52
54
55
+
With Engage, you can personalize email content with real-time profile traits.
56
+
57
+
In your template, you can add profile traits in merge tags to the following fields:
-[Reply to email](#use-profile-traits-in-the-sender-and-reply-to-fields)
53
63
54
64
As you configure the template, click **Merge Tags** and select the profile traits to include. Engage inserts the merge tags based on cursor placement.
55
65
56
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.
57
67
58
68
> info ""
59
-
> 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.
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.
70
+
71
+
### Use profile traits in the sender and reply to fields
72
+
73
+
Personalize your email template by adding profile traits in the **From sender** and **Reply to email** fields.
74
+
75
+
For both fields, keep the following best practices in mind as you add profile traits.
76
+
77
+
- To use merge tags, you must add a `default` value inside a single quote. For example: `{{profile.traits.traits | default: 'Default'}}`
78
+
- Only use variable tags in liquid sytax.
79
+
- Use a valid username for an email address in the profile trait and default value. For example: `default: 'jsmith'`.
80
+
- When you send a test message, the trait must be valid for the field you're using it in. For example:
81
+
- If `profile.traits.first_name` is being used in the **From Sender** field, it must be a valid email username.
82
+
- If `profile.traits.email` is being used in the **Reply to Email** field, it must be a valid email address.
83
+
- In the **From sender** and **Reply to email** fields, the profile trait and default value must be one of the following:
84
+
- A valid email address
85
+
- A valid username for the email address (the input field would have to end with a valid domain for the email address)
Copy file name to clipboardExpand all lines: src/engage/content/sms/template.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,9 @@ Follow these steps to build an SMS template:
34
34
35
35
Use the SMS Templates screen to preview and update existing SMS message templates.
36
36
37
+
> success "Engage content validation"
38
+
> For all Engage content editors, you'll see alerts for any issues in your template, such as invalid profile traits or incorrect liquid syntax. Engage flags the template issues that require your attention before proceeding, and displays recommended steps to fix the issue.
39
+
37
40
## Test your SMS template
38
41
39
42
Send a test SMS message before you include it as a step in your Journey.
0 commit comments