v2026.1.76

v2026.1.76 — MAX integration, Loyalty Programs & Segments optimization

Migration

danger

Migration is required for the platform to function correctly.

To perform the migration, follow these steps:

1. Replace the platform files with the files from the new build;
2. Set the CH_READ_ACTIONS: true parameter in the configuration file on ALL hosts;
3. Run ./akd upgrade and confirm the migration;
4. Set the CH_READ_ACTIONS: false parameter in the configuration file on ALL hosts;
5. Fully restart the platform using the ./akd restart command.

The migration is resource-intensive and requires updating all profiles across all account databases. MongoDB and ClickHouse databases are involved in the process.

---

Additionally, in this update, all active mailings that do not use a resource will stop working.

To ensure mailings continue to work correctly, create a new or select an existing resource and assign it in the mailings settings.

A list of such mailings can be obtained using the command ./aktool campaigns upgrade-blocker-list or ./aktool campaigns upgrade-blocker-list --account-id 12345 (for a specific account).

MAX messenger integration

This update introduces support for a new communication channel — integration with the MAX messenger. Two types of integration are available:

• MAX Bot — for sending personalized messages to users
• MAX Group — for sending messages to group chats

You can create a message template for the MAX messenger using the built-in template editor. A template may include the following elements:

• Text;
• Image;
• Video;
• Audio;
• File.

You can also immediately add interaction buttons for recipients:

• Text button — displays a button with text;
• Link button — opens a specified link;
• Callback button — returns a specified text or command to the bot after clicking;
• Open application — opens a mini-application;
• Request location — requests the user’s location;
• Request contact data — requests the user's contact details and phone number;
• Button group — a combination of buttons of several types.

The channel can be used in mailings, scenarios, and campaigns, and analytics is also available:

Segmentation Optimization

Processing of "exists / does not exist" conditions for channel events (send, open, click, etc.) has been optimized, significantly accelerating segmentation:

• up to 90x faster for simple conditions;
• up to 8x faster for complex conditions with multiple filters.

The algorithm for recalculating static segments based on dynamic conditions has also been optimized, reducing database load and speeding up recalculation of large segments.

To use the accelerated segmentation mechanism, complete the migration steps described at the beginning of the article.

Other

• When importing into the stop list, a report with rejection reasons is now displayed (similar to database import).
• Added the ability to update object attributes (for example, completed Campaigns).
• Fixed an issue where Campaigns inside a campaign were not sent when using dynamic segments.
• Fixed an issue with procloyalty startup on dedicated servers.
• Product segments can now be used in order filters.
• Added logging for Web Push notifications in Safari.
• Fixed an issue where links did not work in preview for Telegram bot templates and Custom channels.
• Improved loyalty program analytics interface.
• Fixed an issue where it was impossible to add a Mailing via a Custom channel after cloning a Scenario.
• Optimized performance of loyalty program APIs.
• Fixed event duplication in ClickHouse. Added deduplication and reversal mechanisms for duplicate events (send, open, click, etc.) and pixel goals.
• Fixed an issue with profile entry into a Scenario when using scheduled segments with the "in dynamic segment" condition.
• Fixed an issue where profiles returned to a previous node if the "Condition" node was unavailable.
• Fixed an issue where static segments with conditions were not recognized as updatable.
• Profiles now correctly exit the "Wait for event" node in Scenarios.
• Fixed incorrect display of Scenario IDs in condition nodes.
• Attributes can now be selected in segment or RTG setup even if no value is assigned.
• Deactivated and hierarchically assigned attributes are now available for viewing in entity objects.
• Fixed issues related to form creation and configuration.
• Fixed an issue where content in the event capture storage was saved when it should not have been.
• Fixed an issue when creating a transaction with points accrual and a 5-year expiration.
• Added message lifetime (TTL) configuration. You can now define message validity in Smart Mailing settings or via API when launching triggered Campaigns. Messages with expired TTL are guaranteed not to be delivered.
• Segmentation by Custom channel events now works correctly.
• Fixed issues with parallel execution of identical tasks on different cluster hosts.
• Fixed an issue where scheduled segments did not start in Scenarios linked to Campaigns.
• Unsubscribe events via API are now correctly captured in event tracking.
• Link shortening in Telegram communications works correctly again.
• Reduced memory consumption of certain platform processes.

References

v2026.1.76.0: PL-21468 PL-16462 PL-21464 PL-21432 PL-21456 PL-21443 PL-20569 PL-21441 PL-21439 PL-21425 PL-21438 PL-21137 PL-15793 PL-21420 PL-21418 PL-21397 PL-21413 PL-21360 PL-21369 PL-21377 PL-21402 PL-18631 PL-21374 PL-19708 PL-21142 PL-21376 PL-19366 PL-21229 PL-21364 PL-21357 PL-20988 PL-21193 PL-21294 PL-21295 PL-17213 PL-21269 PL-21209 PL-21230 PL-21223 PL-21215 PL-21217 PL-21214 PL-21162 PL-21190 PL-21183 PL-21003 PL-21164 PL-17598 PL-17820 PL-17675 PL-21135 PL-21147 PL-21108 PL-20839 PL-21045 PL-19209 PL-21004 PL-20969 PL-20775