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
Omnichannel
- Setting Up Widgets for Your Site
- 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
- Using Yespo Extension for Google Chrome
- Creating Pop-ups via Google Tag Manager or WordPress
- Sending Yespo Widget Events to Google Analytics
- Using A/B Tests for Widgets
Automation
- Building and Editing Workflows
- Configuring Workflow Start/Stop Conditions
- Start Block
- Popular Blocks
- Message Blocks
- Contact Blocks
- Conditions Blocks
- Other Blocks
- Message to Segment Blocks
- Time Blocks
- 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 Campaign to Those Who Did Not Open the Previous One
Personalization
Analytics
- Email Campaign Report
- Web Push Campaign Report
- Viber Campaign Report
- Mobile Push Campaign Report
- App Inbox 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
Integration
Other Blocks
Other blocks are applied to solve various tasks, for example:
- Ending workflow paths
- Creating and updating contacts
- Sending obligatory messages
- Creating separate events for each contact in a segment.
Other blocks include:
- End
- Task
- Webhook
- Sprayer
- Check point
End
Task
Webhook
The task of this block is to request the specified URL (use only the HTTPS protocol). Available request types are GET and POST. Data format: JSON, XML, text.
Use webhooks, when you need to access the data source by reference to return a promo code or authorization token, and then display this data in a message within a workflow. With this block, you can also transmit to the specified address:
- parameters from the event that launched the workflow,
- (additional) fields of the contact on which the workflow launched.
To correctly set up the block, in one of the fields, enter the name of the corresponding variable from the event, by which the contact is identified.
The table below shows examples of the parameters that should be used in these fields:
| Launch method / Field in the workflow | Contact ID | Phone number | |
|---|---|---|---|
| ${parameter} | ${parameter} | ${parameter} | ${parameter} |
| For a dynamic segment | ${contactId} | ${phoneNumber} | ${emailAddress} |
| By field change | ${contactId} | ${phoneNumber} | ${emailAddress} |
Where instead of a parameter you should enter the name of the parameter, containing the value of the contact ID, phone, or email in the form in which you transmit it in the event. Enter it without spaces and with preservation of case.
Note
The Webhook block is used only in combination with the block for sending a single message in any channel, and also with the Variable matches regular expression block. For workflows where a message is sent to a group, the Webhook block does not apply.
Read detailed instructions on setting up, testing, and managing webhooks in workflows.
Sprayer
The block creates events for each contact of the selected segment.
As a rule, if the workflow is launched for a segment, you cannot add the blocks designed for contacts. Sprayer enables to do so.
It works as follows:
- The workflow for a segment has been launched (the segment ID was passed in the event, or the segment is selected in the Sprayer settings).
- The workflow reaches the block Sprayer.
- A separate event for each contact is created (transition from segments to contacts).
- This event launches a workflow for each contact.
The events created by the block contain an email address and contact ID. This makes it possible to launch a different workflow with these events and use contact blocks.
The block has 2 parameters:
- Segment: required parameter. Select the segment in the drop-down menu or specify ${segmentId} variable.
- Event: required parameter. Select the event you want to create.
Events must be created beforehand in Automation → Event types.
Note
Sprayer will trigger the event only if the segment includes less than 1 000 contacts.
All attempts to trigger the event for a bigger segment are displayed in Statistics.
