Skip to main content
Documentation for version v73

v2025.3.73

caution

Starting from v2025.3.74, 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.

Also, campaigns without a linked resource will no longer run. Please make sure that all your campaigns have a linked resource.

v2025.3.73.1 – Attributes, GCG stratification, Scenario improvements​

Added​

Attributes​

Attributes have been added for platform entities. Attributes are special custom fields added to platform entities. They represent a specific parameter with a set of possible values.

With attributes you can:

  • search and organize objects;
  • select campaigns and scenarios for segmentation;
  • insert values into content and API requests.

Learn more about attributes in this section.

Stratification in GCG​

Now you can configure stratification for the global control group. Stratification is a method of randomly selecting profiles with prior division of the audience into subgroups (strata) based on specified characteristics. The audience is split into groups so that each of them reflects the composition of the whole population.

From each group, a portion of profiles is randomly selected proportional to the size of that group. This helps to form a control group with the same distribution of characteristics as the test group, making campaign results more accurate. Stratification setup is described in the relevant article of the documentation.

New Scenario element "Event Waiting"​

A new scenario element has been added — the "Event Waiting" operator. It stops the profile flow until a specific action is performed. As soon as any of the specified events are registered by the platform, the profile moves to the next element along the corresponding branch. If the event does not occur within the specified time, the profile follows another branch.

With this element, you can configure reactivation chains or, for example, an abandoned cart scenario. Read more about the element here.

Profile limiter in the "API Call" element​

For the "API Call" scenario element, it is now possible to limit the number of profiles passing through this node within a certain period of time. This is necessary to avoid overloading the external services that we call from the scenario. The limiter mechanism is based on the "leaky bucket" algorithm. Learn more in the corresponding section of the article "Scenario elements".

Improved​

  • Optimized the performance of proctask and procintegras processes.
  • Updated the CSS inliner in message templates and campaigns.

Other​

  • Various UI/UX issues in the platform have been fixed.
  • Retry counters in senders now correctly display the queue.
  • Fixed errors that occurred when trying to create and save a multivariate test.
  • Display and filtering of senders in the Admin Panel now works correctly.
  • Fixed an error that prevented searching for profiles in a specific scenario element. JSON content linked to this profile in the element now opens without errors.
  • SQL export to segments works correctly again.
  • Fixed errors related to generating and displaying template previews.
  • Added the ability to save a connector to an external database with SSL connection without specifying certificates.
  • Analytics for goals with slashes in the name is displayed correctly again.
References

v2025.3.73.1: PL-18644 PL-18219 PL-18646 PL-18645 PL-18715 PL-18218 PL-18220 PL-18217 PL-18452 PL-18224 PL-18228 PL-18344 PL-17534 PL-18216 PL-18802 PL-18149 PL-18309 PL-18133 PL-18184 PL-18082 PL-17559 PL-18772 PL-16592 PL-18913 PL-18978 PL-18338 PL-18867 PL-18899 PL-18885 PL-18537 PL-18072 PL-18864 PL-18861 PL-18875 PL-18825 PL-12690 PL-18240 PL-16060 PL-18944 PL-18878 PL-18873 PL-18722 PL-18832 PL-18881 PL-15383 PL-18351

v2025.3.73.1140 – Altcraft Mobile SDK v2​

Added​

Altcraft mobile SDK v2​

We have improved our mobile SDK for handling push notifications in applications. Key updates include:

  • Support for multiple authorization types: JWT authorization and Altcraft role token authorization;
  • Ability to display push notifications with context configured in the platform;
  • Automatic token refresh when it changes;
  • Automatic delivery and open event tracking;
  • New functions for working with anonymous and registered users, as well as with multiple users on a single device.

Learn more in the developer documentation section. Altcraft mSDK is available on GitHub.

Other​

  • Added variables for using pixel event data in Scenarios and various types of content. More about these variables here.
  • Added a new tab for managing resource tokens. On this tab, you can create a token for a resource, set its expiration date, and assign roles. You can access this tab after creating and saving the resource (located in the upper-right corner of the screen):

  • Added API handlers for deleting products and SKUs from the Market.
  • Added the option to create an integration with Yandex.Appmetrica without creating a pixel. This can be useful if you need to import profiles without using goals.
  • Added validation to ensure that dynamic JSON provided by the user contains an object (arrays are not accepted).
  • Added the ability to reference the current day in selection conditions and segmentation.
  • Added a Redis connection check during platform startup.

Improved​

  • Message history in Jivo chat is now linked to the user’s login — this helps support staff resolve customer issues more efficiently.
  • Platform process stability has been improved.
  • Various UI/UX component improvements and fixes.
  • The short link generator no longer creates links ending with a dot.
  • The procintegras process logs now include profile-related information and push delivery details for Firebase.

Other​

  • Default value for the FIREBASE_PUSH_BATCH_WORKERS parameter is now 200.
  • Fixed an issue where a dot or comma could be entered into an integer campaign field.
  • SMS sending status handling in the SMS Traffic integration now works correctly again.
  • Fixed an issue that caused segments with the “Participation in segment” condition to be calculated more slowly.
  • Reserved tasks are now correctly set to the registered status.
  • Fixed an issue where a boolean profile field did not update after a form submission.
  • Attributes now correctly substitute values when used in Custom channels.
  • Fixed analytics issues in NPS forms.
  • The integration with EDNA now works properly again.
  • Fixed errors related to data migration during platform updates.
  • Rustore push event registration now works correctly.
  • The formatdate function in the “API Call” scenario element now correctly processes profile fields.
  • Fixed an issue where web version collections were deleted too early.
  • The subscription manager now correctly displays recipients of messages.
  • When updating a template via API, the modification date and time are now updated correctly.
  • Occupied IP addresses are no longer displayed when creating a sender.
  • Fixed an issue that prevented sending a profile to a scenario containing an attribute ignored by the CDP.
  • Fixed several frequent issues in the visual email editor:
    • multiple font display now works correctly;
    • Transition, Perspective, and Transform functions are functioning properly again;
    • background setup and saving issues have been resolved;
    • images in style blocks now load correctly.
  • Link redirection in emails now works correctly again.
  • Default values for parameters SEGSTATIC_PROFILE_CHANGES_BATCH_SIZE and API_GET_PROFILES_BATCH_SIZE have been changed to 20000 and 10000, respectively.
  • Fixed an issue where the templates/list API request did not return the next_from_id field.
  • Password change via the aktool utility now functions correctly.
  • Fixed an issue where the stratification limit from configuration parameters was not displayed in the platform interface.
References

v2025.3.73.1140: PL-19333 PL-19309 PL-19326 PL-18399 PL-19176 PL-19273 PL-18437 PL-17717 PL-18369 PL-18236 PL-17276 PL-19221 PL-19137 PL-18870 PL-18665 PL-17683 PL-17885 PL-17853 PL-17154 PL-17100 PL-19285 PL-18320 PL-19060 PL-18770 PL-19053 PL-19120 PL-19254 PL-19229 PL-18327 PL-19218 PL-18836 PL-15418 PL-19233 PL-19204 PL-17933 PL-19214 PL-19223 PL-18414 PL-19118 PL-19210 PL-18328 PL-19199 PL-18432 PL-18891 PL-19116 PL-19176 PL-19068 PL-18334 PL-10830 PL-19131 PL-19089 PL-19122 PL-19125 PL-18694 PL-19117 PL-17977 PL-18933 PL-17274 PL-18912 PL-18611 PL-17809 PL-17768 PL-18308 PL-13780 PL-18366 PL-19119 PL-18333 PL-19114 PL-19115 PL-18155 PL-18471 PL-18594 PL-18547 PL-16869 PL-19079 PL-19086 PL-19075 PL-19083 PL-19028 PL-19050 PL-17758 PL-19002 PL-19010 PL-18607 PL-18223 PL-18620 PL-16448 PL-17580 PL-19026 PL-19267 PL-19314 PL-19262 PL-16464 PL-18837 PL-19296 PL-19228 PL-19277 PL-18994 PL-19238 PL-18363 PL-19105 PL-18343 PL-19143 PL-18643 PL-18538

v2025.3.73.1942 – Updated email block editor, Faster Imports and Campaigns​

Added​

Updated Block Email Builder​

The Block Email Builder is now more functional and user-friendly. It includes a new "Products" element that automatically pulls products and SKUs from the Altcraft Market.

You can customize the design of product cards and apply filters directly in the editor using an intuitive interface. Data updates dynamically when sending emails, and for one-time mailings, you can lock products in the card to turn them into static content.



The block editor gallery also now lets you edit images — crop, resize, rotate, and flip them directly in the editor.

Other​

  • The SDK now supports registering custom user events.
  • The method /api/v1.1/templates/get is extended: parameters are added to filter templates by channels and to get a list of variables used in the template.
  • If a campaign runs inside a scenario, the methods /api/v1.1/campaigns/triggers/get and /api/v1.1/campaigns/triggers/list now return the workflow ID (workflow_id). The /triggers/list method also allows filtering campaigns by workflow_id.
  • Custom subscription fields can now be displayed in templates using the subscription_field function.
  • A len function was added to compare the length of an array with a given number. For example, to include in a template only products that have images, you can use the expression products("!len(product.pictures, 0)" 10 "manufacturer_name" "desc").

Improved​

  • When exporting collected form data, the profile ID is now included in the report, making it possible to see which profile filled out the form.
  • Improved the audit log event recording process: events are now processed through a separate ak_audit_events queue and saved in batches.
  • Significantly optimized the process of checking and updating sending policies. Previously, during campaign execution, each contact's (subscription's) policy was checked and updated individually; in the new version, policies are processed in batches, which in some cases can increase campaign execution speed up to 10 times.
  • Optimized the profile import process through batch data processing. In some cases, this can double the import speed via API, files, and SQL tables. To enable the new mode, set the IMPORT_BATCH_OPTIMIZER_ENABLE parameter to true.

Other​

  • In the "Dependent objects" section of segments, all related objects are now shown correctly, including scenarios and trigger campaigns.
  • API content is now displayed correctly when viewing a profile through a scenario on wait nodes.
  • Global control group calculation now works correctly for large profile databases.
  • Some security vulnerabilities in the platform have been fixed.
  • Fixed an issue where after merging profiles, a goal was saved in history but the profile did not appear in segment results.
  • Sending policy now works correctly, and profiles that do not match campaign conditions are no longer included in repeated sends.
  • When using SQL queries in templates, the template now renders correctly even if the profile is missing some fields — default values are used instead.
  • Fixed goal registration via API for custom channels using send_message_id.
  • Spaces at the beginning and end of goal names are now automatically trimmed.
References

v2025.3.73.1942: PL-19442, PL-19540, PL-19064, PL-17853, PL-19472, PL-19467, PL-19453, PL-18128, PL-19302, PL-19258, PL-19328, PL-16031, PL-19142, PL-19030, PL-17284, PL-17393, PL-19439, PL-18582, PL-18428, PL-17607, PL-19434, PL-19324, PL-18759, PL-17456, PL-17769, PL-19347, PL-19255, PL-17817, PL-18222, PL-19195, PL-18533, PL-19098, PL-18954, PL-19055, PL-18796, PL-18542, PL-18529, PL-18221, PL-17392, PL-18109, PL-19360, PL-19219, PL-19345, PL-19259, PL-19222, PL-19237, PL-17829, PL-18405, PL-18511, PL-19385, PL-18842

Last updated on