When you launch a simulation, many variants of a message can be generated. So to help you validate all the variants, it is stongly suggested to create regions to validate your message in order to test parts of the message instead of the entire message at once. It is much easier to check a specific region that the entire message, which usually produces too many variants to validate.

You can also add parameters to the message that will identify sections that do apply to a contact by showing a related indicator. That way, sections of the message that contain met conditions will be more easily found.


Prerequisite This feature is not available by default; it is only available upon request.
Access Path > Messages > EMail > Select a message

 How To

Create a region

A region lets you group conditions together in order to validate the different variants of a specific region.

Region name The name will show in the simulation results.
Must be a simple text.
Cannot include variables.
Opening tag An Html tag allowing you to quickly see the region in the simulation results.
  • Recommendation: Use a colored background within a DIV or SPAN.
  • Optional: Add "id='region-anchor' " to your tag so that the document scrolls to this region when it is selected (quite useful to validate footers).
Closing tag A closing tag corresponding to the opening tag.
Example [[#Region("Region Name"){]]

[[#Region("Region Name", "<div id='region-anchor' style='background-color: #FFDDDD;'>", "</div>"){]]

  • If less than 4 regions are defined, they will show on one single line with a selector

  • If more than 4 regions are set, they will be listed in a drop-down menu

Create a condition with a marker

To identify positive conditions (those that are true for the contact).

Expression Standard
Marker Name of marker.
Must be a simple text.
Cannot include variables.
Examples [[ if (Contact.f_City == "Quebec", "Québec") {]]

[[ if (Contact.f_Sex == "M", "Men") {]]

[[ if (Contact.f_Sex == "F", "Women") {]]


Cancel the message to be sent to this contact

Allows you to cancel the message for the current contact.

Lets you target complex cases of personalization that cannot be validated with groups.

For example, a message with promotional offers but no offers displays in message.

Code (optional, by default 100) Code of error type
  • Generic = 100,
  • MissingData = 101,
  • InvalidData = 102,
  • NoContent = 103
Error code Client's message.
Must be a simple text.
Cannot include variables.
Examples context.cancelExecution(“Invalid ID”);
context.cancelExecution(101, “No representative”);
context.cancelExecution(102, “Invalid postal code”);
context.cancelExecution(103, “No promotion”);
Illegal use
context.cancelExecution(103, “Invalid sex ” + Contact.f_sex);