Utilizing conditional logic in automations
Introduction
Conditional logic in automations allows you to create dynamic, personalized customer journeys. By applying specific conditions, you can guide customers through different paths based on their behaviors, attributes, or interactions. This ensures that each customer receives relevant messages and experiences tailored to their needs.
With Dynosend, you can build smart, flexible automations that adjust automatically based on customer data, actions, or other key events.
What is Conditional Logic?
Conditional logic allows you to set "true/false" rules within your automations. For example:
- If a customer opens an email, then send them a follow-up message.
- If a customer doesn't click a link, then send a reminder email.
- If a customer’s doesn't upgrade their trial, then remind them to do so.
These logical rules help you provide personalized experiences at every step of the customer journey.
Benefits of Using Conditional Logic
- Personalization: Customize experiences based on customer behavior.
- Automation: Automatically move users through different paths without manual intervention.
- Higher Engagement: Engage customers with relevant and timely messages.
- Better Conversions: Deliver content that aligns with customer interests, leading to higher conversions.
How to Use Conditional Logic in Dynosend
Follow these steps to create a automations with conditional logic in Dynosend:
1. Create a New automation
- Go to the Automations section of Dynosend.
- Click on New automation.
- Choose a starting trigger, like when a new person is added for example.
2. Add a Conditional Step
- After the trigger, click the “+” to add a new action.
- Scroll down to the “Conditions” list.
- Select your condition:
- Email: To evaluate email opens and link clicks
- Event: Whether a person performed or did not preform a certain event
- Tag: Whether a person is tagged with a specific tag
- Field: To check for custom field values
- Segment: To check if a person is part of a segment
3. Add Additional Actions
On each path (True/False), you can add further actions, for example if someone performs a certain even, you can tag them and send a reminder to the ones who haven't.
Final note
It's important to note that event conditions DO NOT inherently check for events performed before the automation was created. For example, if you are checking for created_project event, it will return a False result if it was performed before the automation's creation date.
If a condition is broken for any reason, for example you forget to save changes or the custom field you are checking in the Field condition was deleted, the condition's result will always be a False and your automations will continue down that path for the rest of the contacts, unless it gets fixed.