v2026.2.77
v2026.2.77.189 — IDigital Direct API integration and improvements
IDigital Direct API SMS provider integration
This update adds support for a new SMS provider — IDigital Direct API.
When configuring a sender for this provider, you need to specify a token for API authorization.

Supported:
- Request format — JSON array (batch sending up to 1000 messages)
- Callback statuses:
delivered,undelivered,unsent - Retry logic for HTTP codes 429, 500, 502, 503 (exponential backoff)
If needed, the sending URL can be overridden via the SMS_IDIGITAL_CUSTOM_SENDING_URL configuration parameter.
Improved
- Changed the sorting library, which accelerated the recalculation of static segments.
- Improved error messages when calculating a global control group with stratification.
- Optimized the PostgreSQL database process, simplifying compliance with information security requirements when deploying the platform.
- Added the ability to automatically clean up old files in the
download_taskreportdirectory. - Added localized messages for new error types in the mailing log.
- The scenario editor performance has been improved.
- Improved interface:
- the sender queue view button is now only displayed for Email channels;
- the list of product segments now correctly shows the user who last updated the segment.
Other
- Fixed the passing of
custom_datafields to event capture when launching a scenario via theworkflows/startAPI. - In the mailing testing section, a test profile is now created only if there is at least one subscription.
- When deactivating a global control group, the ability to remove profiles from the group has been added, and the system will register an exit event.
- Fixed the execution of the
point_trc_migratepoints transaction migration for ClickHouse in replicated mode. - Importing templates via archive no longer results in
httpbeing substituted into image links, reducing the risk of emails going to spam. - In scenarios, when configuring a "Scheduled segment", the selected launch month is now correctly saved. Selection of past dates is prohibited.
- Fixed error display when no profiles match the stratification conditions in the global control groups interface.
- Fixed the default value substitution for numeric fields using a predefined list of values in custom channels.
- Fixed an issue where profiles with a large number of additional fields were not added to the loyalty program.
- In the "Update static segment" scenario node, only segments from the current profile database are now available for selection.
- In analytics reports, deleted loyalty program group levels no longer appear as empty lines — their status and ID are now visible.
- Fixed an issue where profiles were not captured into a scenario when switching the trigger condition from "Click on link in Email" to "Any click in Email".
- When creating indexes in the Admin panel, the
_xxhfield can now be manually selected from the general field list instead of being automatically added via a separate checkbox. - When changing the schedule type in broadcast mailings, incompatible options are no longer saved.
- In segments, user fields are no longer replaced by system fields when creating selection conditions.
- Fixed the display of
procmarketandwebmarketprocess versions. - Added new conditions to segments for selecting profiles based on exclusion from the global control group.
- Fixed the issue with selecting resources and segments in segment conditions for users with limited permissions.
- Fixed an issue where only numeric values were written to a field of type "List" when importing profiles via API.
- Fixed profile capture into a scenario when activating a pixel with the "contains" or "does not contain" selection condition.
- Improved the event capture interface for custom channels: eliminated the ability to select an event that is not processed by hooks.
- Fixed the issue with campaign activation when one of the MongoDB replica members is unavailable.
- Attribute fields with editing restrictions in active objects are now correctly disabled after activation.
- Fixed the "for the last X days" condition in segments: value 1 now correctly selects events only for the current day.
- Fixed slow processing of the
hook_eventsqueue when capturing events with message content. - Fixed an issue where synchronization of static segments with Facebook Ads Manager did not work when selecting the "External identifier" data type.
- When sending a broadcast mailing by profile time zone, if no matching profiles are found, the message "No profiles found for the selected time zones" is now displayed.
- Fixed the display of field headers in segment conditions — the headers defined in the segmentation query are now used.
References
v2026.2.77: PL-18253 PL-19527 PL-20943 PL-20994 PL-21310 PL-21505 PL-21515 PL-21579 PL-21610 PL-21698 PL-21704 PL-21749 PL-21769 PL-21783 PL-21786 PL-21794 PL-21806 PL-21819 PL-21821 PL-21826 PL-21851 PL-21857 PL-21858 PL-21860 PL-21868 PL-21879 PL-21880 PL-21885 PL-21899 PL-21909 PL-21922 PL-21929 PL-21931 PL-21934 PL-21937 PL-21949 PL-21967 PL-21970 PL-21988 PL-22007 PL-21198 PL-18441 PL-18398 PL-8898 PL-18381 PL-21870 PL-21596 PL-21990 PL-12550 PL-17566 PL-21192 PL-21773 PL-21517 PL-21796 PL-21442 PL-20763 PL-20475 PL-21745 PL-21834 PL-21965 PL-21953 PL-21713 PL-21847 PL-20466 PL-19945