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
- 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
Advanced Workflow Block Parameters
Fill the advanced parameters in the following cases:
-
When using custom event parameters
-
For sending messages to an additional contact
-
For inserting dynamic content
List of Additional parameters:
|
Parameter |
Description |
|
Contact ID |
Contact identifier in the system or an event parameter containing it. |
|
|
Contact's email address or an event parameter containing the email address. |
|
Phone |
Contact's phone number or an event parameter containing it. |
|
Token |
Contact's token or an event parameter containing it. |
|
Language |
Message language. Leave the field blank if you use a multilingual message in the workflow. |
|
JSON |
Specific data from the event. |
Let's view each case of parameter configuration in detail.
Using Custom Event Parameters
By default, when starting a workflow, the event should pass standard parameters for contact identification:
|
Event parameters |
Identifiers |
|
ContactId Contact_id |
Contact ID |
|
externalCustomerId |
External ID |
|
EmailAddress UserEmail ContactEmail |
|
|
Phone SMS PhoneNumber |
Phone number |
|
PushToken MobPushToken TelegramBotToken |
Contact token |
Important
-
The primary identifier is ContactId. If it is not specified but at least one of the other identifiers is provided, ContactId will be automatically added to the event.
-
To start workflows, the system identifies the contact for which the event was received. The system searches for the contact using the following rules:
-
Contact ID has the highest priority among all parameters.
-
Entered contact email, phone number, or token are used for sending.
-
If externalCustomerId is specified, the message is sent to the contact it belongs to; among those contacts that were found by email address, phone number or token.
-
If externalCustomerId is not specified, the message is sent to the contact found by email address, phone number or token.
-
If a contact is not found, a new contact will be created for sending.
-
For data consistency, provide parameter names according to the specified list.
If the parameters in the event don't match the standard values, such as using PersonalEmail instead of EmailAddress, like on the screen below
In this case, specify the name of the corresponding variable in the Email field.
Sending Messages to an Additional Contact
For example, if you need to duplicate the message sent to the user and send it to the manager.
Copy the block with the selected message in the workflow and specify the manager's contacts in the advanced parameters.
Inserting Dynamic Content
Use this field to display specific data from the event in the message.
For example, if the event contains JSON:
{
"name": "items",
"value": {
"array": [
{
"name": "Brenda Flatform Sport Sandals",
"price": "100.00",
"url": "https://site.com/catalog/steve-madden-brenda-flatform-sport-sandals?ID=8472233&CategoryID=56233&swatchColor=Natural",
"imageUrl": "https://site.com/uploads/product/big/20161122/20161122_7zvb.jpg"
},
{
"name": "Cloudsteppers Women's Brio Sol Flip-Flop Sandals",
"price": "78.00",
"url": "https://site.com/catalog/clarks-cloudsteppers-womens-brio-sol-flip-flop-sandals?ID=10566812&CategoryID=56233&swatchColor=Red%20Synthetic",
"imageUrl": "https://site.com/uploads/product/big/23112013/2125.jpg"
}
]
}
}
where:
-
name – the field name
-
value – the value to be inserted into the message.
Insert the field name into the JSON parameter in the ${items} format.
Specify the variables that will display the products in the message.
