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
- SDK for Mobile Apps
- Managing Mobile SDK Access Keys
- Connecting Mobile App
- Creating and Uploading a Firebase Key
- Creating Mobile Push Messages
- Setting Up Delivery and Clicks Analytics
- Deep Link Types
- Scheduled Mobile Push Message
- Sending Test Messages from the Event Debug View
- Error Codes for Mob Push Notifications
- 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
- Using A/B Tests In Workflows
- Sending Extra Campaigns
- Sending Reminders at the Time Specified by the User
- 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
- 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
Muting or Unmuting Telegram Notifications for Users
In some instances, you need to mute broadcasts for Telegram users having a dialog with the bot or an operator to avoid interruptions. And when required, the messaging shall be unmuted.
In our platform, these can be done for users with Telegram tokens. The feature is implemented through two API endpoints described below.
Muting Notifications
To mute notifications, send requests to the following endpoint:
- POST /v1/apps/{app_uuid}/token/mute
Note
Muted users or chats can receive transactional messages (smartsend, test).
The method’s parameters and their description are given in the following table.
| Parameter | Type | Description |
|---|---|---|
| token | string |
Required. User’s Telegram token. |
| duration | long |
Optional. Mute duration in seconds:
If the duration is not specified, mute is set to 9999-12-31 23:59:59, disabling notifications "forever". To change the mute duration, send another request with the new value. |
The response may return the following errors listed in the table.
| Status | Error Message |
|---|---|
| 400 | Wrong app uuid |
| 400 | Tokens must be specified |
| 400 | Duration must be positive int |
| 404 | Not registered application |
The muted contacts in the campaign reports are shown as Unavailable contacts with Other errors as the error type.
The error name in the details is CHANNEL_WAS_MUTED.
Unmuting Notifications
To unmute notifications, send requests to the following endpoint:
- POST /v1/apps/{app_uuid}/token/unmute
The request must contain the following parameter:
| Parameter | Type | Description |
|---|---|---|
| token | string |
Required. User’s Telegram token. |
The response may return the following errors listed in the table.
| Status | Error Message |
|---|---|
| 400 | Wrong app uuid |
| 400 | Tokens must be specified |
| 404 | Not registered application |
