Mailmodo 0ff833fb

Mailmodo Support

Stay updated on the status of all your company's support tickets.

Raise a Ticket here

Customer portal

Use ‘Opened’ as a campaign condition to check whether the contact in the running journey has opened the email or not. 

For example - Use this as a campaign condition to send another reminder to the contacts who have not opened the last campaign. 

 Drag and drop ‘Opened’ card from the left panel. 

 Connect it to the ‘send campaign’ card in the journey. 

 Click on the ‘Opened’ card to open the right panel. 

 Add a maximum wait time for the condition. It would mean that the journey would wait for the given time before applying the condition to qualify the contacts in the next step. 

For example - If the maximum wait time is set to 2 days. The journey would only qualify the openers to the next step and would give non openers a time for 2 days to open the campaign and qualify for the opened route. 

 Click on the ‘Save’ button to complete the configuration. 

This would mean, whenever contact reaches the ‘opened’ campaign condition, it would wait as per the maximum wait time and qualify contacts into Opened and Not opened routes in the journey. 

Opened as Campaign activity condition in the journey

Use ‘Clicked’ as a campaign condition to check whether the contact in the running journey has clicked on the URL in the email or not. 

For example - Use this as a campaign condition to send another reminder to the contacts who have not clicked a URL in the last campaign. 

 Drag and drop ‘Clicked’ card from the left panel. 

 Click on the ‘Clicked’ card to open the right panel. 

For example - If the maximum wait time is set to 2 days. The journey would only qualify the clickers to the next step and would give non-clickers a time for 2 days to open the campaign and qualify for the clicked route. 

 In case you want to qualify contacts just on the basis of clicked, click on the ‘save’ button to complete the configuration. 

Or if you want to qualify contacts when a specific URL is clicked, click on the Specific URL option to create rules for different URLs in the email. 

In this scenario the journey understands that, if the contact has clicked but the clicked URL does not match to the URLs set in the rules, that contact should go to the not clicked route. 

This would mean, whenever contact reaches the ‘clicked’ campaign condition, it would wait as per the maximum wait time and qualify contacts into Clicked and Not clicked routes in the journey. 

Clicked as Campaign activity condition in the journey

Use ‘Submitted’ as a campaign condition to check whether the contact in the running journey has submitted the form in the email or not. 

For example - Use this as a campaign condition to send another reminder to the contacts who have not submitted the form in the last campaign. 

 Drag and drop ‘Submitted’ card from the left panel. 

 Click on the ‘Submitted’ card to open the right panel. 

For example - If the maximum wait time is set to 2 days. The journey would only qualify the contacts who have submitted to the next step and would give contacts who did not submit a time for 2 days to open the campaign and qualify for the submitted route. 

 In case you want to qualify contacts just on the basis of submitted, click on the ‘save’ button to complete the configuration. 

Or if you want to qualify contacts when a specific question is answered, click on the Specific submission option to create rules for different questions of the form in the email. 

While adding rules based on multiselect form inputs, use contains operator instead of equals operator

In this scenario the journey understands that, if the contact has submitted the form but did not submit the specific question selected in the rules, that contact should go to the not submitted route. 

This would mean, whenever contact reaches the ‘submitted’ campaign condition, it would wait as per the maximum wait time and qualify contacts into Submitted and Not submitted routes in the journey. 

Submitted as Campaign activity condition in the journey

’ block helps you add a condition to check whether a particular contact property of a person entered into the journey is equal to the value added in the input field or not and send the person down different paths based on this.

Imagine you offer different subscription plans for your software, and you want to provide an exceptional experience for customers who upgrade to a higher-tier plan.  You can automatically send the contact to different paths whenever a contact changes their "Billing Plan" from a lower-tier plan to a higher one. 

 Drag and drop ‘Contact property’ card from the left panel. 

 Connect it to the desired card in the journey. 

 Click on the ‘Contact property’ card to open the right panel. 

You can add more rules by clicking on 'Add Rule'.

This would mean, whenever contact reaches the ‘Contact property’ condition, it would check for the contact property value equal to the value entered in the journey and qualify contacts into YES and NO routes in the journey.

 to find quick guides and walkthroughs. If you face any problem or want to share your opinion then reach out to us at 

Contact property as a condition in the journey

’ block allows you to check whether a contact in the running journey belongs to a particular list/segment selected or not. 

For example - Use this condition when you want to qualify a contact who belongs to the active users segment based on email opens and send a special discount campaign to reward them. 

 Drag and drop the ‘List/segment membership’ card from the left panel. 

 Click on the ‘List/segment membership’ card to open the right panel. 

 Select the list/segment from the dropdown. 

This would mean, that whenever a contact reaches the ‘List/segment membership’ condition, it would check for presence in the list/segment and qualify contacts into YES and NO routes in the journey. 

It is recommended to add a delay of ~10 minutes before the list/segment membership block for the case where the contact is getting added to the said list/segment via an action in the current journey. This is to ensure that the list or segment being used in the condition gets accurately updated up till now.

If you have any queries, then reach out to us at 

List/segment membership as a condition in the journey

’ block allows you to create a condition to check the event property of the event selected in the trigger - Occurrence of an event. 

Let's say you're setting up a system to send campaigns based on how customers sign up, such as whether they signed up using a mobile device or a desktop computer. For instance, you want to send different product resources to those who signed up on their mobiles versus those on desktops. You can easily achieve this by using this condition block by choosing the event property based on the sources of how they have signed up. This way, you can tailor your promotions to match the way customers join, making the experience more personalized for them.

 Drag and drop ‘Custom event condition’ card from the left panel. 

 Click on the ‘Custom event condition’ card to open the right panel. 

 Select the event property from the dropdown. 

 Select the operator and add the event property value in the input field.

  Click on the ‘Save’ button to complete the configuration. 

This would mean, that whenever a contact reaches the ‘Custom event condition’, it would check for the event property value equal to the value entered in the journey and qualify contacts into YES and NO routes in the journey.

Custom event condition as a condition in the journey

The ‘Form submission condition’ block adds branching logic to your journey triggered by a form submission.

Consider a scenario where you wish to trigger a journey based on the submission of any form. You may intend to add further logic to it and branch out the flow for different types of submissions. In that case ‘Form submission condition’ block can be used.

1. A submission in a course registration form can be used to trigger a journey but you may want to engage a contact to different flows depending on online learning or offline classroom mode selected by the user. This can be handled by the ‘Form condition submission’ block.

2. You can engage a user with a different flow depending on the feedback given in any NPS form i.e. different email flow for detractors and promoters

3. Or, you can use this condition block for submissions in a conference registration form to qualify contacts on the basis of the CITY(New York, Los Angeles, etc) selected and enroll them in a different email flow.

 Create a new journey by going to the Journey page. Use Form submission as a trigger

 Select the template and the form for which you wish to trigger the journey. You can add, ‘Trigger for specific submissions’ if specific rules have to be added.

 Add action cards to the journey and create your flow

 Find the ‘Form submission condition’ card  in the right panel, drag and drop it into the canvas

 Set the rules by choosing the form question from the dropdown.

The form fields available in the ‘Form Submission Condition’ block to set the rules will be of the same form which is used in the ‘Form submission Trigger’ block.

This also means that if you add a ‘Send Campaign’ action block in the journey with a form in it, form submission condition block will not use that form. It will only use the form used in the trigger block.


You can add multiple rules to create different paths. Click save once done to save the configuration. This would mean, post publishing the journey, whenever a contact reaches the ‘Form submission condition’ block in the flow, journey would look for the submission in trigger block, check the rules set here, and direct the contact to the respective route in the journey.

 Complete your flow. Once you are done, publish the journey.

Form submission condition as a condition in the journey

’ block allows you to create a condition to check the event property of the event selected in the trigger - Occurrence of an event, specifically a Shopify event. 

Let's say you're setting up a system to send campaigns based on customers Shopify activity. For instance, you want to send campaign for a particular product to users who have not bought it yet. You can easily achieve this by using this condition block by choosing the event property based on the product types. This way, you can tailor your promotions to match the way customers behave, making the experience more personalized for them.

’ card from the left panel, from under 'Advanced conditions'.

 Click on the ‘Shopify activity condition’ card to open the right panel. 

The event properties visible in the dropdown depend on the Shopify Activity which you chose as trigger. For example- 'Placed Order' has 'Payment Method' as a property but 'Cart Abandoned' does not.

’ button to complete the configuration.

This would mean, that whenever a contact reaches the ‘Shopify activity condition’, it would check for the event property value equal to the value entered in the journey and qualify contacts into YES and NO routes in the journey.

If you have any query then reach out to us at 

Conditional node in the journey