Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit5d3692c

Browse files
authored
Merge pull requestsegmentio#5479 from segmentio/Engage-content-validation-
Separate content validation content
2 parents9a2032e +d11ce5f commit5d3692c

File tree

4 files changed

+18
-1
lines changed

4 files changed

+18
-1
lines changed

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

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

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

152+
##Content validation
153+
154+
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.
155+
152156
##Save the template
153157

154158
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 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.
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: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,9 @@ To configure an email template, click **Create Template**.
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+
>info "Engage content validation"
36+
>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. While you can save these templates, you must fix any issues before using them in Engage campaigns.
37+
3538
##Test the Email template
3639
You can send test emails before you include a template in marketing campaigns.
3740

@@ -45,6 +48,11 @@ You can send test emails before you include a template in marketing campaigns.
4548
5. Select**Send test email**.
4649

4750
>success ""
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.
54+
55+
>info ""
4856
>You can also test email templates directly from a[Send an Email step](/docs/engage/journeys/build-journey/#send-an-email) in Journeys.
4957
5058
##Personalize with merge tags

‎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+
>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](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.
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)
[8]ページ先頭
©2009-2025 Movatter.jp