Skip to content

Commit cebc61b

Browse files
committed
First pass
1 parent 8c06219 commit cebc61b

File tree

6 files changed

+46
-5
lines changed

6 files changed

+46
-5
lines changed

src/engage/campaigns/email-campaigns.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,9 @@ 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+
> 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+
5356
### Send an email to all users
5457

5558
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/campaigns/sms-campaigns.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,9 @@ Follow these steps to create an SMS campaign:
4545
4. Enter your campaign content into the **Body** field.
4646
5. Add a STOP/unsubscribe line to the end of your SMS.
4747

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+
4851
> warning ""
4952
> Unsubscribe options are required by law. Your SMS campaign must contain “Reply STOP to unsubscribe.”
5053

src/engage/content/email/editor.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -145,6 +145,10 @@ For example, use `{% if %}`, `{% elseif %}`, and `{% else %}` tags to call a pr
145145

146146
To view more examples related to your use case, visit the [LiquidJS docs](https://liquidjs.com/tags/if.html){:target="blank"}.
147147

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+
148152
## Save the template
149153

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

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,10 +55,12 @@ Click **Format** at any time to properly indent and format your code in the HTML
5555
> info ""
5656
> 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.
5757
58-
### Error flagging
58+
### Error flagging and content validation
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 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+
6264
## Personalize with merge tags
6365
Add merge tags to personalize your message with user profile traits.
6466

src/engage/content/email/template.md

Lines changed: 30 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,17 +21,20 @@ 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:
3131
- [**Drag and Drop Editor**](/docs/engage/content/email/editor/) is a drag and drop WYSIWYG tool with customizable content blocks.
3232
- [**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.
3333
4. Design the email template, then click **Create Email Template**.
3434

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+
3538
## Test the Email template
3639
You can send test emails before you include a template in marketing campaigns.
3740

@@ -48,15 +51,38 @@ You can send test emails before you include a template in marketing campaigns.
4851
> You can also test email templates directly from a [Send an Email step](/docs/engage/journeys/build-journey/#send-an-email) in Journeys.
4952
5053
## 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.
5254

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:
58+
- Subject line
59+
- Preview text
60+
- 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)
5363

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

5666
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.
5767

5868
> 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)
6086

6187
## Include unsubscribe links
6288

src/engage/content/sms/template.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,9 @@ Follow these steps to build an SMS template:
3434

3535
Use the SMS Templates screen to preview and update existing SMS message templates.
3636

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+
3740
## Test your SMS template
3841

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

0 commit comments

Comments
 (0)