Skip to main content

v2021.4.57.0 - JSON profile fields, transition to new analytical storage

Major changes​

JSON profile field​

In some cases, it is necessary to save a subtable or a large set of flags to the profile, and it is pointless to create fields for them.

To make this possible, 2 new types of additional fields have been added to the profile database.

  • Object — for ambiguous data (complex structures).
  • Array of objects — for subtables, for instance, a list of contracts, managers, etc.

Profiles can now be segmented by any nested property of the fields. Read more about it right there.

The profile field update triggers are now compatible with the new field types.

Functional field update​

It is now possible to specify the type of action for each field in all spaces of profile import and profile update. For example, when importing profiles from a file, some of the fields can be filled in with constants and the rest with a value from the file. It is possible to increment number fields or modify a list of tags. Read more about available types in the article.

Transition of profile history storage to ClickHouse​

The first stage of analytics transition to Clickhouse will allow real-time analytics queries to beperformedon big data. It is also the groundwork for the transition to customized reports.

Linking promo codes to profile when generating in loyalty program​

A new option in the loyalty program. When activating this option, select a database and profile matching settings. Generation of promo codes on the loyalty page will add promo codes to the found profiles.

Segmentation of profiles after filling out the form​

Now you can create a segment of profiles that, for instance, filled out a form for the selected period. The following conditions are available:

  • Filled out / did not fill out;
  • Filled out for the selected period / did not fill out for the selected period;
  • Filled out in the last (x) from the current date.

Other changes​

  • Several mobile network operators can be activated in the resource.
  • The saved database configuration password in the admin panel is not displayed in the UI.
  • Standardmatching settingsare available intheprofile history request.
  • Facebook* connection now supports API v12.
  • AKMTA default bounce patterns have been updated

Bug fixes​

  • When adding a subscription, the specified status is not ignored in scheduled imports.
  • Fast segmentation, when database sampling is conducted, now returns a result not just from the first base.
  • When testing a push campaign all events have the same sending ID.
  • The message type selection field is no longer blocked for unsaved campaigns.
  • Pagination in an API request for profile data extraction from a static segment has been fixed.
  • Interrupting segment calculation via the UI completes the task.
  • Broadcast and regular campaigns will now send pending messages according to the schedule after an error in segment or database rewind.
  • The «Add to static segment» event is now correctly displayed in profile history when opening profile import API with the add_to_segments option.

References: PL-3009 PL-6973 PL-7119 PL-7317 PL-7627 PL-7699 PL-7883 PL-7938 PL-8026 PL-8074 PL-8110 PL-8153 PL-8249 PL-8257 PL-8258 PL-8264 PL-8282 PL-8291 PL-8309 PL-8334 PL-8345 PL-8347 PL-8355 PL-8370 PL-8371 PL-8380 PL-8400 PL-8499 PL-8505 PL-8517 PL-8580 PL-8582 PL-8615 PL-8654 PL-8678 PL-8688 PL-8695 PL-8718 PL-8720 PL-8740 PL-8745 PL-8750 PL-8752 PL-8756 PL-8758 PL-8769 PL-8774 PL-8782 PL-8789 PL-8797 PL-8798 PL-8801 PL-8809 PL-8810 PL-8820 PL-8826 PL-8827 PL-8828 PL-8845 PL-8854 PL-8868 PL-8882 PL-8883 PL-8884 PL-8886 PL-8890 PL-8896 PL-8911 PL-8918 PL-8924 PL-8935 PL-8940 PL-8953 PL-8956 PL-8990

*The Meta organization, which owns Instagram, Facebook and WhatsApp products, has been declared as extremist and banned in Russia.

Last updated on