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
Adding a Hidden Preheader
A hidden preheader is a text that follows the subject line in Inbox. Its display and appearance may differ depending on the device and email client. On desktop, preheader text can be between 75 and 100 characters long; on mobile – between 30 and 55 characters.
Tasks of the preheader:
- Complement the subject. Especially applicable to mobiles where the subject display is limited to about 40 characters.
- Show the recipient what content to expect in the email.
- Catch attention with incentives;
- Increase open rate.
How to Add a Preheader to an Email
By default, email clients use the first line of the email copy as a preheader. Depending on the design, it can be image alts, menu titles or anchor links. Such preheaders don’t look nice in Inbox. But with a hidden preheader, you can set the exact text you want to appear as a preheader.
In our platform, you can add it without code editing by adding a preheader to a special field in the template settings. In code, it’s embedded with an esd-hidden-preheader class.
1. Go to Messages > Messages.
2. Open the necessary email or create a new one and click its subject.
3. In Hidden preheader, enter your preheader text.
4. To optimize the text with AI, click Improve with AI and select one of the suggested options.
5. Optionally enable Add white space. It will separate the preheader from the rest of the copy in Inbox, making it look nice and professional.
In code, you can see white space as space symbols that alternate with non-breaking space symbols.
Click to see code
You can remove unnecessary space symbols if needed.
You can use white space without a preheader. This way, only the subject will be displayed in Inbox.
6. Send test messages to test how the preheader looks in different clients on the mobile and desktop.