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/content/email/editor.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -147,7 +147,7 @@ To view more examples related to your use case, visit the [LiquidJS docs](https:
147
147
148
148
## Content validation
149
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).
150
+
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 issue(s) that require your attention before proceeding, and displays recommended steps to fix the issue(s). You must fix any issues before using your template in Engage campaigns.
Copy file name to clipboardExpand all lines: src/engage/content/email/html-editor.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,7 +59,7 @@ Click **Format** at any time to properly indent and format your code in the HTML
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.
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 issue(s) that require your attention before proceeding, and displays recommended steps to fix the issue(s). You must fix any issues before using your template in Engage campaigns.
63
63
64
64
## Personalize with merge tags
65
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
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ To configure an email template, click **Create Template**.
33
33
4. Design the email template, then click **Create Email Template**.
34
34
35
35
> info "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.
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 issue(s) that require your attention before proceeding, and displays recommended steps to fix the issue(s). You must fix any issues before using your template in Engage campaigns.
37
37
38
38
## Test the Email template
39
39
You can send test emails before you include a template in marketing campaigns.
@@ -76,7 +76,9 @@ For both fields, keep the following best practices in mind as you add profile tr
76
76
77
77
- To use merge tags, you must add a `default` value inside a single quote. For example: `{{profile.traits.traits | default: 'Default'}}`
78
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'`.
79
+
- Use a valid username for an email address in the profile trait and default value. For example:
80
+
-`default: 'jsmith'` is valid
81
+
-`default: 'j smith'` is invalid
80
82
- When you send a test message, the trait must be valid for the field you're using it in. For example:
81
83
- If `profile.traits.first_name` is being used in the **From Sender** field, it must be a valid email username.
82
84
- If `profile.traits.email` is being used in the **Reply to Email** field, it must be a valid email address.
Copy file name to clipboardExpand all lines: src/engage/content/sms/template.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ Follow these steps to build an SMS template:
35
35
Use the SMS Templates screen to preview and update existing SMS message templates.
36
36
37
37
> info "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.
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 issue(s) that require your attention before proceeding, and displays recommended steps to fix the issue(s). You must fix any issues before using your template in Engage campaigns.
0 commit comments