05 February 2025
2
6 min
0.00
Yespo System Update for January 2025
In this article, we have compiled the most important Yespo updates for January, from changes in mobile push notifications to improvements in working with widgets (informers) and workflows.
You can find previous updates here.
Mobile Push
Changing of Image Restrictions in Mobile Push Notifications
The image aspect ratio restrictions in the mobile push editor have been removed — now both 2:1 and 1:1 formats are supported.
Working with Segments
Bulk Deletion of Segments
We’ve added the ability to mass delete segments. You can:
- Delete segments only.
- Delete segments along with contacts.
If segments to be deleted are used in active workflows, such workflows must be stopped.
Additional “Between” Operator for Dates and Times
The Between operator allows you to specify a time interval for selecting contacts, for example, to launch a campaign for users who registered during a seasonal sale.
The Between operator is available for fields of type date/regular, date/date with time and when selecting a period by events.
More about working with segments >
Workflows
Checking Event Parameter Values
The new option in the Check values block allows you to check multiple event parameters and contact fields in a workflow at once. For example, if a user purchased in a certain location and if they used a promocode. Using the AND and OR operators makes it easier to combine such conditions.
For more details, see the link >
Stopping a Workflow by Using Multiple Events
We’ve added the ability to add multiple events to the workflow stop configuration.
Now the workflow can be stopped if at least one of the specified events occurs, for example:
- order on the site or in the mobile app;
- subscription placement;
- subscription renewal.
You can configure the workflow to stop on any of these events using the OR operator. This allows you to manage workflows more efficiently and consider different user actions.
About setting the conditions for starting and stopping a workflow >
Transferring a Workflow Launch ID via Webhook
In the Webhook block parameters, it is now possible to send a workflow launch identifier $workflowInstanceId to transfer statistics on the execution of such launch to external data stores.
Telegram
Ability to Mute Telegram Bot Messages
We’ve added the ability to temporarily disable or restore Telegram message reception for a specific user. This makes it more convenient to interact with the bot or operator during messaging.
The functionality is implemented through two new endpoints:
- POST /v1/apps/{app_uuid}/token/mute — mute messages with specifying duration.
- POST /v1/apps/{app_uuid}/token/unmute — restore messaging.
Details regarding the duration of the muting:
- Minimum value: 5 seconds.
- Maximum value: 1 year (31536000 seconds).
- If no value is passed, it is set to "forever" (MuteUntil = 9999-12-31 23:59:59).
The ability to mute messages does not apply to messages in trigger-based worflows, sent using the Send prepared message method, and test messages.
Viber/SMS
New Provider Intel Telecom
Integration with a new provider for sending SMS and Viber messages has appeared.
More on settings of
Widgets
Checking Data Layer Settings in Widget Displaying Rules
Data Layer check has appeared in widget display rules (the On pages section).
This allows you to customize widget displays depending on the availability of the desired Data Layer on the site and personalize widget displays. For example, you can configure the display of a special offer only to visitors who have viewed a specific product or added it to the cart.
Timer
The following updates have been implemented for the Timer element:
- Display countdown without days;
- Display seconds only;
- Updated wait time validation: maximum value – 30 days, minimum – 3 seconds.
API
New API Method: Get Workflows
The new Get workflows API method allows you to get a list of workflows available in the account, simplifying their analytics. Response format:
{
"id": 12345,
"name": "name workflow",
"status": "active",
"tags": [
"tag1",
"tag2"
]
}
New API Request Error Codes
Previously, the API error 429 Too many requests occurred in two cases:
- Sending too many requests (more than 200 requests per second).
- Duplicate requests (repeated request within 1 minute).
These two types of errors are now separated into separate codes:
- 409 Conflict — duplicate requests (repeated request within 1 minute).
- 429 Too many requests — sending more than 200 requests per second.
Implemented for methods:
This simplifies problem diagnosis and allows you to find the source of errors faster.
Want to learn more about the Yespo Omnichannel CDP and our business efficiency solutions? Email info@yespo.io or book a demo.
If you are still looking for specific functionality in your account or have questions about working in the system, please contact the support chat.
