User GuideDeveloper GuideAPI GuideTechnology PartnersNetcore Cloud AI: Co-Marketer
User Guide
BlogLogin

Test Node Message

You can test email template from journey

Suggest Edits

The Send Test Message feature allows you to verify the email content, personalization, and configuration before activating the journey. This helps ensure that the message renders correctly and reaches the intended recipients.

You can use the Test option in two ways.

  1. You can send test emails directly from the Action node on the Journey canvas:
  1. Email Action node in the Journey Builder.
Configure Test message module

Configure Test message in Email Test node

Test Email Configuration

The test panel allows you to specify who should receive the test email.

FieldDescription
Test withDefines the identifier used for testing. For email nodes, this is set to Email.
Email addressEnter the email addresses that should receive the test email. You can add up to 10 email addresses, separated by commas. You can update this in the Admin Configuration of the panel.
Preset Test UsersPreset test users help teams quickly test communications without manually entering email addresses each time. You can preset your emails from Account Configuration > Test Contact

Recently used: You can add all the recently used emails from here without manually entering them.

📘

Note

If an entered email address does not exist in the contact database, the test email will not be sent to that address.

Send the Test Email

After entering the recipients in the Email bar, Click Send. The system processes the request and attempts to send the test email.

A confirmation screen will appear including success or failure details for each recipient.

Email Send Test: Failure Scenarios

Below are the scenarios where a Journey Node Send Test for Email can fail

  1. User Issues: A test email will fail if the user is anonymous and the anonymous feature is not enabled in the system.
  2. Personalisation / Attribute Issues: If there is an error while reading user attributes or event data from MongoDB, the test fails with a personalisation error.
  3. Template / Content Issues: If a merchandising template is used but the mt_request_id is not set in Redis, the test will be skipped.
  4. Recipient Validation Issues: The test fails when the email address is invalid or improperly formatted.
  5. Blacklisted contacts: The email is blocked if the recipient is unsubscribed or present in suppression lists.
  6. Product Recommendation Issues: The test fails if product or recommendation data cannot be retrieved.
  7. Coupon / Content Issues: The test fails when the coupon or dynamic content is invalid, missing, or exhausted.
  8. Gateway Issues: The test fails if the email service provider or gateway is unavailable or encounters errors.
  9. Backend Errors: Any internal service error or downtime leads to test failure.

Updated 7 days ago