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
Setting Up Recommendations for Trigger Campaigns
The recommendation blocks in the email are placed in stripes. Stripe’s code contains the rules for substituting dynamic data.
You will find the Abandoned browse template in your account, where this stripe is already set up.
You only need to create data sources and insert their names into the stripes’ code.
We will show how to create a trigger template with two dynamic stripes: one with products viewed by the user and one with recommendations based on products viewed. Each stripe requires its data source.
Recommendation Setup Steps
1. Create data sources based on the Abandoned view (up to 6 products) and Recommendations for 6 abandoned views (up to 6 rec.) algorithms.
Note
Most algorithms are designed for specific advanced segmentation triggers and work only in them. Setting up a universal algorithm is described in the article Setting Up Product Recommendations for Promo Campaigns.
2. Go to the Messages section on the Messages tab and click New Email.
3. Select the Abandoned browse basic template.
The template contains 2 stripes with product cards:
- the first (You recently viewed) — with dynamic settings;
- the second (You may also like) is illustrative, without dynamic settings.
4. Select the first stripe with products and open its code.
5. In the #foreach($item in $data.get('views')) line, replace views with the name of the data source you created based on the Abandoned view (up to 6 products) algorithm.
6. Customize the stripe’s appearance.
The stripe’s structure is universal: depending on the number of viewed items, the recipient will see one, two, or three cards in a row.
You can change the design of the stripe’s elements: colors, text, and background.
We do not recommend changing the stripe’s structure, i.e., the arrangement of its elements to each other: this will break the layout, and the recipient will see an incorrect display of the email’s content. Also, you cannot change the variables specified in the structure blocks since they are responsible for displaying product data from your feed.
If you want to create a fundamentally different structure with dynamic content, please send a request to support@yespo.io
Learn more about designing recommendations in email.
7. Save the stripe as a module.
You can insert the saved module in any campaigns with product selections, for example, for the Abandoned cart trigger. You just need to replace the name of the data source.
We will use the saved module in the same template as a stripe with recommendations for viewed products.
8. Remove the illustrative stripe with product cards from the template (You may also like).
9. Insert the module you saved before in place of the removed stripe.
10. Replace the name of the data source in the stripe’s code with the one you created for the Recommendations for 6 abandoned views (up to 6 rec.) algorithm.
This completes the recommendation settings. You can insert saved modules into your trigger template or redesign the template you are currently working on to match the style of your site.
Note
You can define what to do with messages when there is no data for recommendations - to send or not. To do this, add one of the variants of the Velocity command to the recommendations’ code:
- $!datasource('source_name').required('false') — send,
- $!datasource('source_name').required('true') — do not send.