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 Subscription
- 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
Designing Recommendations in Email
Let’s consider the design features of an email template with products from viewed/cart/recommendations, etc.
Selecting Template
You can create an email based on the system's basic templates. Go to Messages → Messages, click New email, and select Abandoned cart or Abandoned browse in the Basic tab:
The Abandoned browse template is universal because it contains several structures with a different number of cards in them. Such a template is suitable not only for triggers based on user browses but also for any other, where, for example, product recommendations are used. The Abandoned browse template already contains all the necessary variables. You just need to adjust the data substitution according to the instructions.
If the proposed recommendation block layout is unsuitable, you can create them yourself. After that, request integration@yespo.io so our specialists set up a dynamic content substitution.
Designing Recommendation Blocks
Customize the appearance of the email and product cards following your campaigns’ design. Structurally, in addition to the standard elements — header, footer, information block — the message must contain:
- Block with one card if a user browses one product;
- Block with two cards;
- Block with three cards.
Lay out structures with a different set of cards in the same stripe, one under the other.
If a user browses 15 products during a session, the last 6 products will be displayed in the email (by default), so there is no need to make up more than 3 product cards in the structure.
If the products in your emails are displayed one in a row, then you do not need to make up stripes with 1, 2, or 3 products.
You can copy such a block from the Abandoned cart template.
Prepare in advance the entire chain of messages that will participate in the workflow.