​

Overview

​

Channels That Support Personalized Preview

​

Types of Personalization Supported for Personalized Preview

​

Preview Personalized Campaign Content

​

Push, SMS, and WhatsApp

1. Navigate to step 2 of your campaign creation process.
2. Under Preview type, click Personalized. MoEngage will randomly select a user and render a personalized preview for that user.
3. Use the edit icon to change the default user.
4. Use the Select user by and User identifier value lists to select the user you want to use for preview.
   
5. Click Fetch user data. MoEngage will load all the attributes used in the campaign. The fallbacks, where applicable, are displayed next to the attributes.
   • User and event attributes: These values are directly taken from the user data. You can change the attribute values and switch between fallback and actual values.
     After selecting all the values, click Refresh/Update preview to render the preview with the selected values.
     • Old UI
     • New UI

     

     
     To enable Update Preview for your account, please contact your MoEngage Customer Success Manager (CSM) or the Support team.
   • Product sets: These values are directly taken from the product data. However, they are shown as JSON. Change the JSON object based on your requirement and click Refresh/Update preview.
   • Content APIs: MoEngage fetches these values using the configured APIs. You can change values in the JSON object for previews here. If the endpoint is not reachable, an empty response is displayed. This will let you create your temporary data for preview purposes.
6. After selecting the user and previewing them, you can close the slide-out and continue with the campaign changes. The selected user details are stored for your future previews.

​

Email

1. Navigate to step 2 of email campaign creation. You have the following options to create content for your email campaigns:
   • Create content with the Drag-and-Drop editor
   • Create content with Custom HTML Editor
     Both options support a personalized preview as follows:
     • While creating email content with the drag-and-drop editor, you can access the personalized preview as shown below:
     • While creating email content with an HTML editor, you can access the personalized preview through the View advanced preview option as shown below:
2. Similar to Push and SMS, you can select a user and preview your email message for the selected user.

​

Edit Personalized Preview Output

1. On the Personalized preview page, click the text box next to the personalization inputs and enter the data. You can also edit product sets by expanding the product sets list and clicking the edit icon. After editing the output, click Refresh/Update previewto update it.
   To enable Update Preview for your account, please contact your MoEngage Customer Success Manager (CSM) or the Support team.
   • Old UI
   • New UI

   

   
2. Turn on the Use sample data from the personalized preview for the test toggle to test your campaigns with the updated personalized preview output to evaluate their performance and effectiveness before launch.

​

Error Detection

• If your message has multiple issues, such as a broken user attribute and event attributes, they are all displayed simultaneously.
• If your message has issues arising from product set/content API/content blocks/AUX data, the first error category encountered is shown on the UI.
• Each error includes an error category (to identify the source) and a description (to explain the resolution).

​

Error Categories and Descriptions

SMS/Push Preview	Email Preview

​

Custom Jinja Error Messages

​

Example 1: Single Attribute Validation

{% if not EventAttribute['invalidEventAttribute'] %} {% MOE\_NOT\_SEND("invalidEventAttribute is missing") %} {% endif %}

​

​

Example 2: Aggregated Validation (Multiple Errors)

{% if not EventAttribute['Core\_Observability.invalidAttribute'] %} {% MOE\_NOT\_SEND("Core\_Observability.invalidAttribute is missing") %} {% endif %}
{% if not UserAttribute['invalidAttribute'] %} {% MOE\_NOT\_SEND("invalidAttribute is missing") %} {% endif %}
{% if not UserAttribute['invalidAttribute2'] %} {% MOE\_NOT\_SEND("invalidAttribute2 is missing") %} {% endif %}

• Event attribute
  • 1. Core_Observability.invalidAttribute is missing
• User attribute
  • 1. invalidAttribute is missing
  • 2. invalidAttribute2 is missing

​

Validation Scenarios

• Input: The selected user has values for Core\_Observability, invalidAttribute, and invalidAttribute2.
• Result: The message is rendered successfully. The error pane remains empty.

• Input: The selected user is missing invalidAttribute2, but other attributes are present.
• Result: The preview is blocked.
• Error Output: The pane displays a single error under the User attribute category: 1. invalidAttribute2 is missing.

​

Finalize the Preview

1. Review the errors in the right-side pane.
2. Edit your Jinja code or modify the sample attribute values.
3. Click Refresh/Update Preview to see the corrected content.
4. Turn on the Use sample data from the personalized preview for the test toggle to send a test to your device using the debugged data.

​

FAQs