Skip to main content
Version: v72

v2025.1.71

v2025.1.71.0 - Global control groups, administrative panel rework, NPS testing​

caution

For the platform to work correctly after the upgrade you need to perform a migration, to do this:

1. Before running procevent, perform the data migration for ClickHouse:

/opt/MarketingPlatform/ak/bin/aktool profile_history add_gcg_id_column --config /opt/MarketingPlatform/config/main.json
/opt/MarketingPlatform/ak/bin/aktool history_storage add_gcg_id_column --config /opt/MarketingPlatform/config/main.json
/opt/MarketingPlatform/ak/bin/aktool history_storage add_profile_marks --config /opt/MarketingPlatform/config/main.json

The platform can only be started after the ClickHouse migrations are completed.

2. After completing the ClickHouse migrations, run aktool from the new build to migrate MongoDB:

./aktool --config config/main.json profiles migrate-gcg-flags

Note that the MongoDB migration may take from one to several hours. The global control groups feature will be available only after the MongoDB migration is completed.

3. Start procevent.

Major changes​

Global control groups​

The platform now includes a feature to select global control groups. Global control groups are parts of the customer base that temporarily does not receive marketing communications in order to analyze the effectiveness of marketing strategies. After some time, the user can compare key metrics of the main part of the clients and the control group. In case the groups' metrics differ insignificantly, the marketer can conclude that his campaigns are ineffective:

You can read more about global control groups here.

NPS testing in Forms​

You can now add a NPS survey to web forms created in the Altcraft platform. These surveys help you calculate the Net Promoter Score (customer loyalty index), a metric that shows customer commitment to a company or product. This index is one of the main indices for measuring customer loyalty. NPS allows you to analyze the strengths and weaknesses of a product and adjust your marketing strategy:

To learn how to set up NPS surveys in the platform, read the article or use this video guide.

Block email editor​

The block editor Pixcraft has been added to the email template editor. It allows you to quickly and easily create an email template that will display correctly on all types of devices. The editor also supports AMP content for your emails:

You can read more about block editor here.

Redesigned administrative panel​

The administrative panel has been significantly redesigned: the interface has been changed, new functionality has been added, and the panel engine has been completely updated:

warning

Starting with version 72, the platform will require the use of Redis-compatible storage, we suggest using Kvrocks. Kvrocks documentation is available here.

Integration with the SMS provider Stream Telecom​

Added an integration with the Stream Telecom SMS provider. To set up the integration, configure the corresponding sender type in the Administrative Panel.

Minor changes​

  • Mass operations in the platform (activation, deactivation and deletion) for such elements as scripts, templates, users, etc. have been improved.
  • Added support for Request-ID and Token header passing for API 1.1. requests, also improved request deduplication operation.
  • The connection interface has been updated.
  • Added a warning when attempting to delete profiles that have recently participated in campaigns.
  • Updated the scheduling settings interface for some platform sections.
  • Clicking the "Save" button no longer closes the editor or redirects the user to the section menu.

Fixes​

  • Fixed a bug where the status of machine learning settings was not saved in the platform.
  • Now the user cannot delete entities from the cart if the account is frozen.
  • Fixed a bug that caused clicks in SMS and push messages to register unnecessary delivery events.
  • Fixed errors in Tag Manager variables.
  • Scenarios configured to capture when a pixel is activated now work correctly.
  • Made some changes to the Rich Push editor.
  • Fixed a bug where while importing products with custom fields, an attempt was made to re-create the field.
  • Screening a link with parameters inside a pixel now works correctly.
  • Improved stability of the procworkflow, procintegras, proctask, proctrigger, procevent and akmtad processes.
  • Fixed an issue where a Viber campaign with SMS Traffic sent a message to only one subscriber.
  • Information about a profile's participation in a scenario is now updated correctly.
  • Resolved an issue where login credentials were not displayed in the welcome email.
  • Messages in RabbitMQ queues are now processed correctly again.
  • Added validation for file extensions when creating a segment based on the "In file column" condition.
  • Special characters in file names no longer cause errors when querying the data table.
  • The SMS template is now can be saved even if the "SMS Limit" field is empty.
  • Resolved issues with test sending for Telegram channels.
  • Form data is no longer duplicated when transferred to the platform.
  • Fixed an issue where clicking links in push notifications did not work in Mozilla Firefox.
  • Telegram campaigns now use less memory when launched.
  • Improved stability of the Analytics module: fixed various issues related to report generation and data collection.
  • The $dateNowFunc function in JSON requests now works correctly again.
  • Fixed an issue where tags were not added to multiple objects.
  • Template preview images are now exported correctly.
  • Fixed errors in the market/sku/import and profiles/segstatic/list API requests.
  • Added validation for deleting external databases.
  • Deep Links no longer disappear when saving a template in the push message editor.
  • Tags in scenarios are now displayed correctly.
  • Fixed an issue where a campaign would not open when navigating from a report or profile history.
  • Profiles frozen in a scenario are no longer deleted when the scenario is modified.
  • Fixed a bug where AKMTA was sending empty messages.
  • Day of the week waiting condition works correctly in scripts again.
  • Improved validation of email addresses in the list of recipients of a hidden copy of an email.
  • Push message receive and open events are logged correctly.
  • Optimized the process of generating and sending Push messages.
  • Improved logging for certain processes.
  • Interface improvements: fixed display issues for some elements and resolved errors and typos in platform texts.
References

v2025.1.71.0: PL-17608 PL-17599 PL-17574 PL-17572 PL-17570 PL-17564 PL-17558 PL-17556 PL-17549 PL-17526 PL-17524 PL-17519 PL-17518 PL-17516 PL-17508 PL-17497 PL-17494 PL-17487 PL-17486 PL-17470 PL-17459 PL-17455 PL-17448 PL-17429 PL-17426 PL-17424 PL-17410 PL-17402 PL-17398 PL-17374 PL-17373 PL-17372 PL-17369 PL-17327 PL-17322 PL-17305 PL-17303 PL-17287 PL-17285 PL-17283 PL-17282 PL-17278 PL-17277 PL-17259 PL-17258 PL-17247 PL-17240 PL-17220 PL-17208 PL-17187 PL-17170 PL-17132 PL-17126 PL-17114 PL-17084 PL-17078 PL-17074 PL-16987 PL-16979 PL-16954 PL-16953 PL-16930 PL-16907 PL-16854 PL-16701 PL-16700 PL-16679 PL-16641 PL-16640 PL-16607 PL-16600 PL-16579 PL-16558 PL-16542 PL-16539 PL-16537 PL-16523 PL-16515 PL-16513 PL-16498 PL-16493 PL-16479 PL-16477 PL-16468 PL-16460 PL-16430 PL-16414 PL-16410 PL-16406 PL-16404 PL-16403 PL-16386 PL-16358 PL-16350 PL-16348 PL-16344 PL-16328 PL-16296 PL-16247 PL-16201 PL-16144 PL-16069 PL-16024 PL-16003 PL-15998 PL-15997 PL-15994 PL-15980 PL-15944 PL-15852 PL-15829 PL-15825 PL-15777 PL-15647 PL-15639 PL-15557 PL-15498 PL-15404 PL-15379 PL-15378 PL-15370 PL-15327 PL-15245 PL-15021 PL-14968 PL-14230 PL-13369 PL-12949 PL-12732 PL-12297 PL-17562 PL-17634 PL-17579 PL-17613 PL-17036 PL-17576 PL-13434 PL-17358 PL-17135 PL-16695

v2025.1.71.255 - Mandatory use of the resource in campaigns​

caution

Starting with the next update, sending campaigns without an assigned resource will not be possible!

If you have been using campaigns without a resource, please assign a resource to them.

Major changes​

Mandatory use of the resource in campaigns​

From the next update, all campaigns in the platform will use a resource. Therefore, it is now impossible to save campaigns without specifying a resource:

Minor changes​

  • Improved logging of Reply processing in AKMTA.
  • Added configuration parameter responsible for the maximum size of unloaded data from a SQL table column.

Fixes​

  • Fixed display problems with some interface elements.
  • Improved operation of scenario elements "Capture profiles on pixel activation" and "Profile update", as well as campaigns launched from the scenarios.
  • Fixed errors occurring when registering Viber events in SMS Traffic integration.
  • Viber integration with Rapporto now works correctly on all accounts.
  • Optimized procevent queue parsing process.
  • Fixed a bug where deleting profiles was available to users without proper permissions.
  • Profile counter in a segment now works correctly when sending via Telegram bot.
  • Fixed an issue where data received from push messages was not fully transferred to the platform.
  • Improved stability of procworkflow and proctask processes.
References

v2025.1.71.255: PL-17644 PL-17561 PL-17618 PL-17648 PL-17643 PL-17640 PL-16953 PL-17552 PL-17557 PL-17508 PL-17481 PL-17467 PL-17270 PL-17039 PL-17031 PL-16369 PL-15722 PL-17164 PL-17650 PL-17597 PL-17360 PL-17680 PL-15760 PL-17505 PL-16454

v2025.1.71.507 - Restructuring the policy counter repository​

caution

You will need to migrate for the platform to work correctly after the upgrade. Before launching the new version, do the following:

  1. Stop the required platform services:
./akd stop {proctrigger,procworkflow,proctask}
  1. Run aktool from a new build with the command:
./aktool migrate policystore --config /opt/MarketingPlatform/config/main.json
  1. Restart the platform services:
./akd restart

Help for the migrator:

Migrate policystore db to accounts dbs collections policy_contact, policy_profile

Usage:
  aktool migrate policystore [flags]
  aktool migrate policystore [command]

Available Commands:
  ensure_policystore_indexes Ensures policystore migrate indexes created

Flags:
      --account int          account id
      --batch_interval int   batch interval in seconds (default 1)
      --batch_size int       batch size (default 10000)
      --batch_workers int    number of batch workers (default 8)
  -h, --help                 help for policystore
      --workers int          number of workers for accounts (default 8)

Global Flags:
      --clickhouse_database_name string   usage database for clickhouse
      --config string                     config path (default "/opt/akd/config/main.json")
  -o, --output string                     file path to output in the result of the command (default "stdout")
      --truncate                          whether to truncate the file specified by --output

Use "aktool migrate policystore [command] --help" for more information about a command.

Changes​

  • Optimization of the repository structure of sending policy counters has been performed.
  • Metrics on API calls to the scenarios are now available in analytics.
  • Special characters can now be used in entity names.
  • Fixed some bugs in the functionality and interface of the Administrative Panel.
  • Logging of some platform processes has been improved.

Fixes​

  • Fixed an error where push campaigns generated a large number of non-existent undeliveries.
  • Statuses in SMS integration with Devino Telecom are now processed correctly.
  • Fixed errors occurring when testing custom channel campaigns.
  • Entity analytics with HTML tag in the name works correctly again.
  • Fixed errors occurring when registering events in Viber integration with SMS Traffic.
  • Improved stability of Web Push SDK methods.
  • Fixed some interface bugs.
  • Improved stability of proctask process.
References

v2025.1.71.507: PL-17756 PL-17753 PL-17446 PL-17727 PL-17731 PL-17728 PL-17715 PL-17720 PL-17586 PL-17718 PL-17711 PL-17706 PL-17704 PL-17648 PL-17698 PL-17677 PL-17670 PL-17656 PL-17642 PL-17626 PL-17641 PL-17249 PL-17272 PL-17631 PL-17619 PL-17507 PL-17211 PL-17111 PL-16993 PL-16354

v2025.1.71.627 - RMQ buffer base mode​

Changes​

  • Added buffer base mode for RMQ in prochook.
  • Metrics on API calls to the scenarios are now available in analytics.
  • Special characters can now be used in entity names.
  • Added the option to configure global qos for RMQ.
  • Fixed some bugs in the functionality and interface of the Administrative Panel.
  • Logging of some platform processes has been improved.

Fixes​

  • Fixed an error where push campaigns generated a large number of non-existent undeliveries.
  • Statuses in SMS integration with Devino Telecom are now processed correctly.
  • Fixed errors occurring when testing custom channel campaigns.
  • Fixed a bug related to incorrect display of inactive campaign status.
  • Entity analytics with HTML tag in the name works correctly again.
  • Fixed errors occurring when registering events in Viber integration with SMS Traffic.
  • Improved stability of Web Push SDK methods.
  • Fixed some interface bugs.
  • Improved stability of proctask process.
References

v2025.1.71.627: PL-17756 PL-17753 PL-17446 PL-17727 PL-17731 PL-17728 PL-17715 PL-17720 PL-17586 PL-17718 PL-17711 PL-17706 PL-17704 PL-17648 PL-17698 PL-17677 PL-17670 PL-17656 PL-17642 PL-17626 PL-17641 PL-17249 PL-17272 PL-17631 PL-17619 PL-17507 PL-17211 PL-17111 PL-16993 PL-16354

v2025.1.71.873 - SSL support for CH​

Major changes​

SSL support for ClickHouse​

Added support for SSL-secured connections to ClickHouse DB. To enable this, activate the corresponding option in the Admin Panel.

Minor changes​

  • The global control group now retains groups assigned to the original profile database.

Fixes​

  • Custom channel events are now displayed correctly in profile history.
  • Improved message sending via Telegram bots in scenarios.
  • Campaign testing within scenarios is functioning correctly again.
  • Fixed an issue where subscription fields for user channels were not saved.
  • Relations now work correctly in message templates.
  • Fixed an issue causing the send_message_id parameter to take different values for the same message in action hooks.
  • Phone number filtering in scenarios is functioning correctly again.
  • Fixed an issue causing sending policy parameters to change randomly.
  • Several improvements and fixes in the Admin Panel.
  • Fixed issues related to formatting floating-point numbers.
  • Improved profile history and certain logs.
  • Fixed an unintended subscription priority change when modified via API.
References

v2025.1.71.873: PL-17067 PL-17351 PL-17361 PL-17888 PL-17876 PL-17814 PL-17801 PL-17536 PL-17748 PL-17532 PL-17798 PL-17723 PL-17433 PL-17824 PL-17719 PL-17846 PL-17555 PL-17810 PL-17774 PL-17757 PL-17755 PL-17587 PL-17447 PL-7853 PL-17795 PL-17801 PL-17627 PL-17703 PL-17796 PL-17707 PL-17729 PL-17472 PL-17708

v2025.1.71.1059 - Scenario API improvements​

Major changes​

  • Added activation and deactivation requests for a scenario: /workflows/activate and /workflows/deactivate.
  • Scenario API responses now include campaign and template identifiers, as well as information about transitions to another scenario.

Minor changes​

  • The maximum length of scenario titles has been increased to 156 characters.
  • Improved logging of certain platform processes.

Fixes​

  • Improved layout for several UI elements.
  • Fixed an issue where test launches of campaigns using a dynamic segment as a subscriber source were not possible.
  • LDAP authentication now works correctly again.
  • The campaign filter now finds campaigns that were created within a scenario.
  • Fixed errors occurring during Yandex.Audience segment resynchronization attempts.
  • Fixed an issue where form publish and hide times were incorrectly set in the settings.
  • Tracking services again correctly listen to the address and port passed through parameters.
References

v2025.1.71.1059: PL-17896 PL-17938 PL-16077 PL-17925 PL-17832 PL-17831 PL-17823 PL-16045 PL-16896 PL-17773 PL-17765 PL-9599 PL-17930 PL-17482 PL-17899 PL-17538 PL-17291 PL-17762 PL-17668 PL-17664 PL-17636 PL-17928 PL-17881 PL-17868 PL-17834

v2025.1.71.1487 - API calls optimization, improved logging​

Changes​

  • Extended data type support in ClickHouse table integrations.
  • Added the option to specify the launch time of global control groups in the platform configuration file.
  • The platform now logs the processing time for each profile at every campaign stage.
  • Added a button to stop segment recounting.

Fixes​

  • Fixed an issue where data from a deleted profile field was still returned via the API.
  • Duplicate relations no longer appear when created via API.
  • Optimized the /profiles/import_batch API method.
  • The formatted date variable in the "API call" scenario element works correctly again.
  • Fixed font rendering issues in popups.
  • Links to the web versions of emails now work correctly in test sends.
  • Fixed several UI-related bugs.
  • Render errors are now properly displayed in the campaign log.
  • Fixed an issue where templates and campaigns were not moved to the trash.
  • The "Profile update" scenario element can now set a null value.
  • The blockquote tag renders correctly in Telegram templates.
  • Fixed several bugs related to custom channel.
References

v2025.1.71.1487: PL-17984 PL-18003 PL-17901 PL-17947 PL-15365 PL-13140 PL-17926 PL-17900 PL-17945 PL-17568 PL-17684 PL-17709 PL-17052 PL-17356 PL-15570 PL-17949 PL-17254 PL-17786 PL-17663 PL-17701 PL-17553 PL-18018 PL-17953 PL-17996 PL-17970 PL-16377 PL-17931 PL-17525 PL-17968 PL-17938 PL-16892 PL-17965 PL-17097 PL-17280 PL-17808 PL-17841 PL-17767 PL-17825 PL-17766 PL-17785 PL-11838 PL-17241 PL-17074 PL-17738 PL-17689 PL-17603 PL-15518 PL-8650 PL-16616

v2025.1.71.2447 - SberMobile and Intellin integrations​

Major changes​

New integrations: SberMobile and Intellin​

The following integrations have been added:

  • integration with the Intellin SMS provider;
  • integration with the SberMobile SMS gateway.

Improved data logging for sends and scenarios​

  • Logs for Notify requests have been added to retrieve integration statuses. These logs help you understand why your integration may have become inactive.
  • The USMID has been added to AKMTA headers. USMID is a unique message identifier that contains detailed information about the send. Knowing it can help you analyze possible delivery issues more easily.

You can now list multiple URLs in the segmentation condition "Link click".

Minor changes​

caution

If you specified an address in the RPC_HOST_CLI parameter, all clients (even from other hosts) will connect via this address. Before installing the update, be sure to set a public or “gray” address for this parameter.

  • The procworkflow RPC client now connects using the address set in the dedicated configuration parameter.
  • Added the ability to batch-send web versions of messages to S3 storage.

Fixes​

  • Fixed issues related to two-factor authentication in the Admin Panel.
  • Improved the stability of the Tilda integration.
  • Fixed a bug where scheduled segments were not recalculated when a scenario was launched.
  • Revised the logic for sending form submission reports, improving data accuracy.
  • The format function now works correctly in loops and when used with apicontent.
  • Improved click registration in Telegram bots.
  • Delivery statuses and duplicate messages are now correctly registered for SMS campaigns.
  • Resolved issues where users without appropriate roles could access platform entities.
  • Test campaigns with dynamic subscriber segments now launch correctly.
  • Fixed several UI/UX issues in the interface.
  • Resolved errors related to using conditions in segments and scenarios.
  • Custom bounce rules for AKMTA now function correctly again.
  • Improved stability of the following processes: webcontrol, procintegras, proctask, prochook, and procworkflow.
References

v2025.1.71.2447: PL-18148 PL-18022 PL-18189 PL-18131 PL-18102 PL-17352 PL-17981 PL-17931 PL-17397 PL-17357 PL-15357 PL-15143 PL-18194 PL-17998 PL-18130 PL-15386 PL-18079 PL-18077 PL-18178 PL-18165 PL-18123 PL-18105 PL-18112 PL-17821 PL-17615 PL-18054 PL-17695 PL-18048 PL-18047 PL-15625 PL-17771 PL-17735 PL-17770 PL-17689 PL-17653 PL-15344 PL-14393 PL-12555 PL-18122 PL-18127 PL-18098 PL-17804 PL-18060 PL-18084 PL-17799 PL-18050 PL-17976 PL-17983 PL-17721 PL-17395 PL-16585 PL-15340 PL-18090 PL-17957 PL-17275 PL-17803 PL-18097 PL-17463 PL-18074 PL-17179 PL-15009 PL-17861 PL-17977 PL-17874 PL-17400 PL-17003 PL-16578 PL-16589 PL-16022 PL-17105 PL-17489 PL-17972 PL-17294 PL-17942 PL-17836 PL-17488 PL-17747 PL-17943 PL-17967 PL-18031 PL-17550 PL-17279 PL-17815 PL-17950 PL-15815 PL-17286 PL-17896 PL-17887 PL-8823 PL-16693

v2025.1.71.2873 - Hive connector support​

caution

You will need to migrate for the platform to work correctly after the upgrade. Before launching the new version, do the following:

  1. Stop the required platform services:
./akd stop {proctrigger,procworkflow,proctask}
  1. Run aktool from a new build with the command:
./aktool migrate policystore --config /opt/MarketingPlatform/config/main.json
  1. Restart the platform services:
./akd restart

Help for the migrator:

Migrate policystore db to accounts dbs collections policy_contact, policy_profile

Usage:
  aktool migrate policystore [flags]
  aktool migrate policystore [command]

Available Commands:
  ensure_policystore_indexes Ensures policystore migrate indexes created

Flags:
      --account int          account id
      --batch_interval int   batch interval in seconds (default 1)
      --batch_size int       batch size (default 10000)
      --batch_workers int    number of batch workers (default 8)
  -h, --help                 help for policystore
      --workers int          number of workers for accounts (default 8)

Global Flags:
      --clickhouse_database_name string   usage database for clickhouse
      --config string                     config path (default "/opt/akd/config/main.json")
  -o, --output string                     file path to output in the result of the command (default "stdout")
      --truncate                          whether to truncate the file specified by --output

Use "aktool migrate policystore [command] --help" for more information about a command.

Major changes​

SQL Connector Hive​

Added support for the SQL Hive/Hadoop connector as an external database. Learn more about configuring the connector here.

Minor changes​

  • Updated APIs for the new versions of Google Ads and Facebook™* Ads Manager.
  • Added support for Rabbit version 4+.
  • The Altcraft platform has been certified for compatibility and proper operation with the domestic operating system "RED OS 8".
  • The MTA_DEFAULT_TTL parameter, which defines the delivery waiting time for SMS and Email, now defaults to 3 days (259200 seconds).
  • The "not\\savailable" blocking rule has been removed from the MTA sender rules because it caused errors in email campaign operation.

Fixes​

  • Enhanced platform security mechanisms.
  • Fixed various UI/UX issues.
  • Improved stability of akd, akmta, aktool, procpiper, proctrigger, procintegras, proctask, and procworkflow processes.
  • Optimized oxy_triggers queue parsing.
  • Custom bounce rules in AKMTA now work correctly.
  • Optimized log rotation mechanism.
  • Web versions of emails sent through the platform are now saved in the correct format.
  • Improved 2FA stability.
  • Fixed issues related to editing message templates within the platform.
  • JSON filter now works correctly for nested objects.
  • Fixed an issue where form data was mistakenly submitted twice.
  • Added validation for certain fields in the Admin Panel.
  • Fixed some issues related to access roles.
  • Additional profile fields are now exported correctly in personal data exports.
  • Fixed an issue where apicontent was incorrectly handled during bulk profile imports into a Scenario.
References

v2025.1.71.2873: PL-17550 PL-18489 PL-18393 PL-18384 PL-18106 PL-18136 PL-15177 PL-18457 PL-18247 PL-18386 PL-18382 PL-18215 PL-18104 PL-15824 PL-18424 PL-18401 PL-18312 PL-18238 PL-18244 PL-18139 PL-18415 PL-18238 PL-18350 PL-18402 PL-18145 PL-18177 PL-18331 PL-18339 PL-18287 PL-15410 PL-18294 PL-18289 PL-18135 PL-18235 PL-18314 PL-18290 PL-18198 PL-18145 PL-18175 PL-18013 PL-18281 PL-18154 PL-18229 PL-18150 PL-17878 PL-17807 PL-18283 PL-18268 PL-17604 PL-18038 PL-18169 PL-18073 PL-18168 PL-18263 PL-18265 PL-18255 PL-17816 PL-18053 PL-18161 PL-17546 PL-18196

v2025.1.71.3092 - Event backward compatibility​

Changes​

  • Added backward compatibility for events from custom channels of legacy platform versions.
  • Security mechanisms optimized.

Fixes​

  • Test sends to Telegram now work correctly.
  • The value 0 in the "in data table" condition is now displayed when passed via query parameters.
  • Fixed an issue in the form editor where incorrect access rules were applied.
  • Added a timeout for hanging queries in PostgreSQL.
  • The ability to specify a custom configuration file path for platform services now works properly.
  • Improved readability of API logs.
  • Tags and additional fields are now correctly processed when creating objects via API.
  • The visual editor now correctly updates custom block settings.
  • Fields of type "Integer" now work properly when forming a control group from a file.
  • Reduced memory consumption by the campaign process when sending Telegram messages with attachments.
  • Confirmation link check now works correctly in templates.
  • Fixed the "Prioritize new subscriptions" option in resource settings.
  • AKMTA now correctly switches to backup MX records when the primary is unavailable.
  • The profile date is now correctly inserted in templates when using the formatdate function.
  • Fixed issues related to handling events from Amazon SNS sender.
References

v2025.1.71.3092: PL-10119 PL-18521 PL-18315 PL-17401 PL-18125 PL-18000 PL-17857 PL-17818 PL-18266 PL-18426 PL-18544 PL-17224 PL-18478 PL-18269 PL-18193 PL-18384 PL-18323 PL-17622 PL-18527 PL-17548 PL-18041 PL-18425 PL-18368 PL-18237 PL-18151

*Meta Platforms Inc., the company behind Instagram, Facebook, and WhatsApp, has been designated as an extremist organization and is banned in the Russian Federation.
**Viber is a trademark of Rakuten Group, Inc. and is blocked in the Russian Federation.

Last updated on