First steps
User Data
- Responsive Email Editor Review
- Designing your email
- Creating Synchronized Modules
- Setting Up Responsive Email Design
- Setting Up Smart Containers
- Creating a Gmail Promotions Annotation
- Adding The Rollover Effect
- Adding Anchor Links
- Module Library
- Adding a Table to an Email
- Adding Custom Fonts
- Creating CTA Button
- Working with Images
- Creating Timer
- Using AI in the Email Editor
- Messenger Protocol Support in Email Clients and Platforms
Omnichannel
- Setting Up Widgets for Your Site
- Widgets Gamification
- Widget Calling
- Setting Up Locations for the Widget Calling Rules
- Storing data from widgets to contact fields
- Using Annoyance Safeguard
- Actions After Form Submission
- Replacing Double Opt-In System Workflow
- Creating Pop-ups via Google Tag Manager or WordPress
- Sending Yespo Widget Events to Google Analytics
- Using A/B Tests for Widgets
- Collecting Contact Information Using Request Forms
Automation
- Building and Editing Workflows
- Configuring Workflow Start/Stop Conditions
- Start Block
- Popular Blocks
- Message Blocks
- Using One from Many Message Block
- Contact Blocks
- Conditions Blocks
- Other Blocks
- Message to Segment Blocks
- Time Blocks
- Advanced Workflow Block Parameters
- Setting Up Allowed Send Time
- Using Workflow Launch History
- Webhook Workflows
- Workflow Troubleshooting
- Double Opt-In
- Welcome Сampaign
- Welcome Series Segmented by Category
- Launching a Workflow After a Contact Import
- Regular Workflow for a Segment
- Birthday Campaign
- Linking Workflow to the Button
- Using Variables from Order in Workflow
- Collecting Order Feedback
- Customer Reactivation
- Sending Extra Campaigns
- Sending Reminders at the Time Specified by the User
- Sending Campaign to Those Who Did Not Open the Previous One
- Using A/B Tests In Workflows
Personalization
Analytics
- Email Campaign Report
- Web Push Campaign Report
- Viber Campaign Report
- Mobile Push Campaign Report
- App Inbox Campaign Report
- Telegram Campaign Report
- In-App Report
- Widget Report
- Triggered Campaign Report
- AMP Campaign Report
- SMS Campaign Report
- Multilingual Campaign Report
- Setting up UTM Tags
- Revenue from Campaigns
- Tracking Campaign Performance in Google Analytics 4
- Message Analytics
Multilanguage Campaigns
Events and Behaviour Tracking
Recommendations
API
Security and Compliance
Splitting the Workflow Depending on the Event Parameters
The Condition block allows you to split the workflow depending on the parameters of the event that launched the workflow. These can be the following parameters:
- Category of the site visited by the contact
- City of residence
- Clothing size
- Product preferences
- Gender
For example, you need to send emails with selections of products for men and women, depending on gender, the value of which is passed in the event by the Generate event API method:
{
"eventTypeKey": "event_name",
"keyValue": "user@example.com",
"params":
[
{
"name": "EmailAddress",
"value": "user@example.com"
},
{
"name": "Name",
"value": "John"
},
{
"name": "lang",
"value": "EN"
},
{
"name": "gender",
"value": "M"
}
]
}
Workflow Settings
1. Create a workflow with two Condition blocks that check the event parameters and send the contact to the appropriate branch. An example of such a workflow:
2. Set up the first Condition block:
1) Select Variable matches regular expression in the Task name field to check the contents of the gender parameter.
2) Add the name of the validation parameter in the name field, in our case, it is gender.
3) Specify the value of the request parameter in the pattern field in the following format: .*M.* (male).
Important
The case of the letter in the pattern field must match the case of the letter in the event parameters
3. Add the second Condition block to the workflow with the same settings as the first one, but with the .*F.* (female) pattern.
If the event parameters match the value specified in the first condition, contacts will go along the “Yes” branch; if not, they will go to the next checkpoint.
Contacts without gender specified in the request will go through the third workflow branch.
Similar articles: