- Home
- What's New
- Customer Segmentation Suite for Magento 2
🎯
Feature Spotlight
Overview
16 releases in the last year
Each square is a week. Pick one to jump to its releases.
Less
More
November 2026
Nov 18
1.3.18
Nov 18
Fixed
- Fixed a security issue in the "Customer Segment" condition of cart price rules: the shopper's segments were looked up by the e-mail entered in the cart, so a guest could type the e-mail of a segment member at checkout and get a discount meant only for that segment. Segment membership for a logged-in customer is now taken from their customer account, and a guest qualifies by e-mail only when no registered customer of the website uses that e-mail. Registered customers still qualify for the segments they joined through guest orders placed with their account e-mail before they registered
Nov 17
1.3.17
Nov 17
Fixed
-
Fixed the Adobe Commerce Marketplace build of 1.3.16 not listing
mirasvit/module-report-apiamong its packages.mirasvit/module-reportrequires it, so installing 1.3.16 from the Marketplace could not resolve its dependencies. The extension code is unchanged from 1.3.16, and installs from Mirasvit's own repository were never affected
Nov 9
1.3.16
Nov 9
Fixed
- Fixed a security issue where admin users without the Customer Segment access permission could view or export segment data — segment members' names, e-mails, dates of birth and guest billing addresses — through the segment grids, the segment form, the segment comparison and the validation preview. All of this data now requires the Customer Segment permission
- Fixed a security issue in the "Shopping Cart Amount", "Shopping Cart Products", "Sales Amount" and "Purchased Quantity" segment conditions: an admin user with access to segments could submit crafted condition values that ran their own database queries during segment refresh and read the results back from the refresh error message. These conditions now accept only the options offered in the condition editor and a numeric value
- Fixed the "Shopping Cart Products" segment condition failing to refresh when set to "is" or "is not" — these comparisons now work as expected
Nov 6
1.3.15
Nov 6
Fixed
- Fixed a security issue in the segment grid and the segment validation preview: a segment title or condition value containing script code could run in the browser of every admin who opened the page. Segment titles and condition texts are now shown as plain text, and error messages in the segment refresh panel are no longer interpreted as HTML, so a failing refresh can't inject content into the page
Nov 5
1.3.14
Nov 5
Fixed
- Fixed the "Sales by Segment" report data being available to admin users without the report access permission: the data loaded into the report grid and charts (and exported from it) now requires the same "Sales by Segment" permission as the report page itself
Nov 5
1.3.13
Nov 5
Fixed
- Fixed a security issue in the date range picker used in segment conditions: an admin page link with a crafted parameter could run unwanted scripts in the admin browser, and admin users without the Customer Segment access permission could open the picker. The picker now requires the Customer Segment permission and accepts only valid form field identifiers
Nov 5
1.3.12
Nov 5
Fixed
- Fixed a security issue in the Follow Up Email "Subscription" segment condition: a customer could register with a specially crafted e-mail address that altered the database query run during segment refresh. Customer e-mail addresses are now passed to the database safely, so unusual addresses no longer affect the query or break the refresh
October 2026
Oct 26
1.3.11
Oct 26
Improved
- Compatible with Mirasvit Core 2.0 — the extension can now be installed alongside both the 1.x and 2.0 versions of the core package
- The segment refresh and progress screens in the admin no longer depend on other scripts loading first, making them more reliable
Fixed
-
Fixed the "Purchased Quantity" segment condition ignoring the decimal part of the entered value (e.g.
2.5was treated as2), which could put the wrong customers into the segment
September 2026
Sep 26
1.3.10
Sep 26
Fixed
- Deleting and refreshing customer segments in the admin now requires the Customer Segment access permission, so admin users without it can no longer trigger these actions.
June 2026
Jun 17
1.3.9
Jun 17
Fixed
- Fixed the guest customers grid inside a segment, which could fail to load on Magento 2.4.9. The list of guest shoppers now opens correctly again.
- Fixed an error when refreshing a segment that had already been deleted — you now see a clear "This segment no longer exists" message instead of a crash.
- Fixed an error on the segment listing when a row pointed to a segment that no longer exists.
- Fixed a possible error when refreshing a segment that uses the Follow Up Email "Subscription" condition.
May 2026
May 27
1.3.8
May 27
Fixed
-
Removed legacy PHP-serialize branch in the Segment save controller — rule conditions now always go through Magento's
Jsonserializer. -
Added a one-time data patch that converts any legacy PHP-serialized segment conditions to JSON on
setup:upgrade. Stores already on JSON are unaffected.
April 2026
Apr 21
1.3.7
Apr 21
Improved
- Added i18n support for 15 core locales (ar_SA, cs_CZ, de_DE, es_ES, fr_FR, it_IT, ja_JP, nl_NL, pl_PL, pt_BR, pt_PT, sv_SE, tr_TR, uk_UA, zh_Hans_CN)
March 2026
Mar 11
1.3.6
Mar 11
Fixed
- Magento 2.4.9 compatibility
January 2026
Jan 30
1.3.5
Jan 30
Improved
- Refactor Last Order condition to support flexible date filtering with child conditions (Date Range, Days Ago, Status)
Jan 22
1.3.4
Jan 22
Improved
- Improved segment refresh speed recovery after heavy server load
Fixed
- The issue with error during refreshing the segment related to the float number passed as a current page of the collection
December 2025
Dec 5
1.3.3
Dec 5
New
Ability to duplicate customer segments
Fixed
- The issue with “Days Ago” condition considers time during validation