v2026.3.79

Reconfiguration required when upgrading to v2026.3.79

When upgrading to version 79, scenarios are migrated to the new drafts and versions model. Back up your data before the upgrade; after the upgrade, check the scenario list and their statuses.

info

Starting from the next platform verison, the following API changes will take effect:

• The old API version 1.0 will be disabled. Please switch to the current version in advance.
• The API token can no longer be sent in GET parameters or in the JSON body. Use the header instead: Authorization: Bearer <token>
• The format parameter will no longer be supported. Set the desired format using the Accept header (for example, Accept: application/json).

We recommend making the necessary changes in advance to avoid API issues.

v2026.3.79.0 — Scenario versions

Version 79 introduces scenario drafts and versions. Segment calculation, scenario operation, and platform security have also become noticeably more reliable.

Scenario drafts and versions

Scenarios can now be assembled in a draft — a working copy where changes are made without affecting the running scenario.

A draft can be saved as a version — an immutable snapshot of the scenario. The version limit is 100; when it is reached, the platform will suggest deleting the earliest archived version before saving a new one. A version can be published — it becomes the main one when the scenario runs. Publishing is unavailable while the scenario contains errors — for example, a deleted resource or an unconfigured node: the system first checks the scenario and will not allow publishing until everything is fixed.

Read more in the scenario drafts and versions section.

Added

• A delimiter between multiple-choice values has been added to the export of filled form data.
• Tracking services can now be assigned their own BASEDIR path — previously they used the platform path.

Improved

• Updatable segment calculation errors (including SQL query timeouts) are no longer masked by the "completed" status — they are written to the calculation history and displayed.
• Segment recalculation is now faster and more stable.
• Scenarios with an enabled tag filter can be selected in campaigns again.
• When a campaign finishes, its scenarios correctly switch to the "Inactive" status.
• Scenarios no longer remain in the trash bin when a campaign is permanently deleted.
• Cloning a campaign with published scenarios completes without errors — scenarios are correctly attached to the copy.
• Changing message settings no longer changes its status.
• The sending policy in the scenario's "Channels" node is no longer treated as an error and no longer drops the profile from the scenario.

Other

• WhatsApp forms now have a window for inserting dynamic content.
• Search in the scenario list with the status filter now works correctly.
• Scenario node statistics are displayed after a platform upgrade.
• The profile update node now modifies the object and object_array fields.
• Bulk editing via a segment now updates the email subscription status.
• In segments with an SQL segmentation query, query field options now display correctly.
• The trigger message list now returns the campaign id for triggers added through a scenario as well.
• After a platform upgrade, scenario statistics now correctly count the profiles that entered the scenario.
• The message editor now has log and report buttons.
• The content_type validation in custom channel pipelines has been fixed.

References

v2026.3.79.0: PL-23148 PL-22944 PL-22547 PL-23090 PL-23100 PL-23075 PL-23120 PL-23117 PL-23115 PL-22347 PL-23111 PL-23106 PL-23045 PL-22919 PL-23092 PL-23068 PL-23073 PL-23058 PL-23065 PL-22924 PL-23050 PL-23039 PL-23023 PL-23044 PL-23025 PL-22744 PL-22946 PL-23034 PL-22982 PL-23024 PL-23031 PL-23029 PL-23026 PL-22983 PL-23017 PL-22849 PL-22745 PL-22980 PL-22981 PL-23003 PL-23005 PL-22812 PL-23001 PL-22997 PL-22808 PL-22994 PL-22651 PL-22896 PL-22892 PL-22939 PL-22792 PL-22820 PL-22964 PL-16418 PL-22941 PL-22809 PL-22952 PL-22916 PL-22918 PL-22505 PL-22650 PL-22837 PL-22791 PL-22749 PL-22911 PL-22801 PL-22895 PL-22884 PL-22728 PL-22887 PL-22843 PL-22876 PL-22852 PL-22804 PL-22859 PL-22834 PL-22772 PL-22821 PL-22751 PL-22817 PL-22752 PL-22757 PL-22731 PL-22743 PL-22727 PL-22789 PL-22652 PL-22540 PL-22707 PL-22686 PL-22376 PL-22635 PL-22539 PL-22502 PL-22488 PL-22498 PL-22497 PL-22453 PL-22458 PL-22444 PL-22437 PL-22389 PL-22369 PL-22380 PL-22343 PL-22297 PL-22326 PL-21569 PL-18834 PL-21992 PL-21991 PL-22257 PL-21995 PL-22098 PL-22145 PL-22097 PL-21888 PL-21913 PL-21222 PL-21263 PL-21463 PL-21743 PL-21094 PL-21838 PL-21741 PL-21408 PL-21261 PL-21122 PL-20944 PL-21409 PL-19615 PL-20920 PL-21391 PL-20947 PL-21260 PL-21105 PL-21247 PL-21148 PL-15491 PL-21128 PL-21095 PL-20946 PL-21092 PL-21091 PL-21134 PL-21112 PL-20942

v2026.3.79.787 — Order-based segmentation conditions, elseif in dynamic content, and fixes

This update expands segmentation conditions with market data, adds the {elseif} expression to dynamic content, and fixes numerous issues in scenarios, segments, mailings, and templates.

Order-based segmentation conditions

New fields are available in market order segmentation conditions:

• Custom fields of an order, product, and SKU — filtering by the values of user-defined fields.
• Order line item statuses — filtering profiles by statuses, including custom ones.
• Order creation and update dates — new date comparison conditions.

The {elseif} expression in dynamic content

The {elseif} expression is now available in template dynamic content: alternative conditions are checked within a single {if} ... {end} block, without nested constructs.

Improved

• Priority queues now support the WhatsApp, VK Notify, Viber, and Max channels.
• The "Order change" trigger now includes the "Order line item status change" condition.
• Scenario relation validation has been relaxed: scenarios with unrelated non-start nodes can now be published.
• Server-side validation of segmentation queries has been strengthened: invalid queries are rejected before execution.
• The profile counter now correctly decreases when the tariff is exceeded, if the actual number of profiles is below the limit.
• The main dashboard now shows absolute event values instead of percentages for the selected period.
• Password protection in Event Capture settings has been strengthened.
• The "not once in mailings/messages" segmentation conditions are now merged into one.
• Loading of the segment editing page with many dependent objects has been optimized.

Other

• Minor interface issues have been fixed.
• The first call to the "API Call" node is no longer rejected by the rate limiter due to an empty token bucket.
• The [few] label no longer appears in the scenario calendar when selecting a date range.
• Profiles no longer get stuck in the "API Call" node when the flow is limited to one profile per minute.
• Fixed an issue where a scenario could stop working due to an extra field in a condition node.
• Order date conditions in scenarios are now migrated correctly when upgrading to v79.
• Crashes during scenario processing and trigger message dispatch have been fixed.
• Profiles no longer leave a scenario with an error at the order date condition node after upgrading to v79.
• The scenario schedule no longer resets after platform services restart.
• Template preview with empty API content no longer fails.
• The push editor no longer freezes when editing an image link.
• The not_in_segment function against a dynamic segment with an exists condition returns the correct number of profiles again.
• Viber mailings via the SMS Traffic provider are sent correctly.
• JavaScript errors on the segment editing page have been fixed.
• Interface dates now respect the account time zone.
• The error window in the event capture test no longer closes instantly, so the error can be reviewed.
• A CSV parsing error is now logged without excessive verbosity.
• Restoring a promo code from the recycle bin no longer causes an error.
• In the general segment list, older segments with multiple databases now show the hint icon about the format change.
• Segment recalculation errors with market order conditions have been fixed.
• The "in progress" and "in delivery" order statuses are displayed in the Market.
• Filtering mailings by custom channel is available again in segment conditions.
• The text in the priority scenario tooltip has been clarified.
• Simultaneous import_batch requests for one profile no longer result in a lost subscription or field.
• The recycle bin clear button is blocked while the cleanup is in progress.
• In-App template export works correctly.
• The scenario pass rate drop after the introduction of scenario drafts has been fixed.
• The error when viewing the "Sent to scenario" action in the audit log has been fixed.
• The checkbox in a custom channel template no longer resets to defaults when reopened.
• File size and format validation in custom channel templates now follows the rules received from the server.
• Deleting an SMS sender no longer creates stray queues.
• Duplicate subscriber limit notifications are no longer sent.
• v79 migration errors during the platform upgrade have been fixed.
• Opening an existing template with custom channels no longer fails with a JavaScript error.
• Push templates with loops in custom JSON are saved again in the push editor.
• Push notifications to Safari 16.4+ without a .p12 certificate are sent correctly.
• Hidden form field values are displayed correctly.
• Periodic web version cleanup no longer blocks the platform.
• Control group calculation on audience expansion is correct again.
• The inflated open and read percentages on the main page have been fixed.
• The Yandex Audience connection status is displayed correctly when a connection fails.
• Mailing sending over the Viber channel works correctly.
• The "Automatic segment update" block no longer disappears after saving without a page reload.
• Downloading the API content file in a scenario no longer produces an empty file.
• After a manual change, an updatable segment no longer stops recalculating.
• Error messages related to trigger nodes have been clarified.
• Platform stability and security have been improved.

References

v2026.3.79.787: PL-23524 PL-23257 PL-23474 PL-23462 PL-23447 PL-21983 PL-23356 PL-23354 PL-23294 PL-22418 PL-22248 PL-22219 PL-21771 PL-20812 PL-21935

v2026.3.79.684: PL-23465 PL-18472 PL-23434 PL-23400 PL-23372 PL-23325 PL-23327 PL-23335 PL-23361 PL-23355 PL-23350 PL-23251 PL-23278 PL-23313 PL-22955 PL-23247 PL-23013 PL-22365 PL-22279 PL-23160 PL-23085

v2026.3.79.499: PL-19940 PL-23228 PL-22524 PL-23328 PL-23353

v2026.3.79.487: PL-23371 PL-23368 PL-21453 PL-23337 PL-23349 PL-23346 PL-23253 PL-23340 PL-23343 PL-23338 PL-23342 PL-23322 PL-23030

v2026.3.79.449: PL-23312 PL-23285 PL-22661

v2026.3.79.431: PL-23277 PL-23296 PL-22713 PL-23283 PL-23240 PL-22620 PL-23171 PL-23260 PL-23244 PL-22684 PL-23175 PL-23205 PL-23069 PL-22673 PL-22218 PL-23222 PL-22840 PL-23199 PL-23166 PL-22536 PL-23036 PL-23078 PL-23071 PL-23162 PL-23089 PL-23118 PL-23054 PL-9836 PL-23088 PL-22196 PL-22972 PL-23070 PL-22830 PL-12562 PL-22860 PL-22589 PL-22344 PL-21825 PL-21224 PL-21052

v2026.3.79.120: PL-23180 PL-23150 PL-23120 PL-22878 PL-23157 PL-23168 PL-23159 PL-22629 PL-22465

v2026.3.79.1168 — MMS via MTS Omni Channel and fixes

This update introduces MMS messaging via the MTS Omni Channel provider, adds In-App events to analytics reports, improves the scenario, segment, and template editors as well as profile import, and fixes numerous issues.

MMS via the MTS Omni Channel provider

The platform SMS channel now supports sending MMS messages (text and image) via the MTS Omni Channel HTTP API provider. Delivery statuses are returned to the platform.

Added

• In-App events (impression, close, and others) are now included in analytics reports.

Improved

• In the web admin panel, the "Campaign" term is replaced with "Mailing".
• In profile import from a file, mapping fields are immediately editable, without the view mode.
• In the segment editor, condition menu items are renamed and re-ordered: repeated words and duplicate channel names are removed.
• In scenarios and campaigns, the general settings menu is collapsed by default, with a collapse arrow added.
• The dark variable validation window in the template editor is replaced with the standard white one.

Other

• Incoming OIDC login via Keycloak now uses PKCE.
• The authentication connector form for the Keycloak type no longer defaults to port 389.
• Event Capture history backfill now includes loyalty program events — historical loyalty data is delivered to external systems.
• Event capture for loyalty transactions now sends the correct event type: point accrual or point redemption.
• Loyalty points with instant activation are no longer activated with a delay.
• The complaint event from the Amazon SES gateway is saved with the complaint time rather than the email delivery time.
• A single sent SMS now registers one delivery event instead of several.
• Scrolling through transaction records in the profile works again.
• Fixed an error where profile database recalculation included fewer profiles than specified in the import file.
• The trigger mailing and the mailing list open again — the channel saving error in a trigger is fixed.
• Recalculating a segment with a date condition no longer fails with a validation error.
• The ERR_TRIGGER_INACTIVE error when starting trigger mailings after platform services restart is fixed.
• Scenario node statistics open again without errors.
• RabbitMQ connection retries are added at mailing start.
• Custom channel events are displayed again in the "Event Waiting" node.
• The phone number is added to the profile during import_batch with phone matching.
• MMS fields are correctly displayed in the template preview in the SMS mailing editor.
• Platform stability and security have been improved.

References

v2026.3.79.1045: PL-23552 PL-23147 PL-23585 PL-23449 PL-23523 PL-23550 PL-23545 PL-23542 PL-21863 PL-23535 PL-23530 PL-23527 PL-23429 PL-23483 PL-23454 PL-23375 PL-23373 PL-23323 PL-23112 PL-22474 PL-22358

v2026.3.79.1107: PL-23659 PL-23643 PL-23606 PL-23494 PL-23431 PL-23435 PL-22698 PL-21558

v2026.3.79.1165: PL-23525 PL-23668 PL-23666 PL-23590 PL-23578 PL-23490 PL-23108 PL-23426 PL-23112 PL-23122

v2026.3.79.1168: PL-22348