jExperience Release Notes

September 29, 2025

jExperience 3.6.2

Experience 3.6.2 is a new minor version. It requires the use of jCustomer 2.5.0 and Jahia 8.1.5.0. It is also the recommended version to use with Jahia 8.2.

Please review upgrade instructions for both jExperience and jCustomer carefully.

Starting from jExperience 3.5.0, search events are not tracked by default anymore.

Improvements

  • Introduced compatibility with page builder for pager personalization and AB Test
  • Added an HTML title header on jExperience admin pages
  • Added jexperience permissions to site admin by default
  • Added option to set a page variant as control / default variant
  • Switched synchronous login to true by default, this can be modified via the jExperience configuration `waitForProfileMergeOnLogin.

Bugfixes

  • Fixed an issue during jCustomer migration by removing suffix in exportconfigid when it exists in jcustomer before getting exportconfig details
  • Fixed issue with wem:variantsTraffic not handled correctly on promote ab test
  • Fixed white page on goal after migration from version older than 3.5.1
  • Fixed an exception in jExperienceProbe when jCustomer is not responding properly
  • Fixed performance issue by using * instead of *** in search profile queries when the term is empty
  • Removed redundant unauthenticated Http client call to get connectivity details
  • Removed "Healthcheck heartbeat timestamp" property from the profile property management UI
  • Corrected typos in French labels

jExperience 3.5.1

jExperience 3.5.1 is a new minor version. It requires the use of jCustomer 2.5.0 and Jahia 8.1.5.0. It is also the recommended version to use with Jahia 8.2.

Please review upgrade instructions for both jExperience and jCustomer carefully.

Starting from jExperience 3.5.0, search events are not tracked by default anymore.

Deprecations and Removal

  • Campaign tracking has been deprecated and is now disabled by default. It can be re-enabled using a new “enableCampaignTracking” property available in jExperience configuration file.
  • Consent manager has been deprecated and is now disabled by default. It can be re-enabled using a new “enableConsentManager” property available in jExperience configuration file.
  • The async HTTP client and methods using it (such as performAsyncRequestContext) that were deprecated in jExperience 3.0.0 have been removed.

#### Improvements

  • Added the template name in the variant title in AB testing reports.
  • Removed the delete variant option from manage experience screens. This feature is still available via page composer.
  • Updated the minimum jCustomer version to 2.5.0. This is needed since the unomi-tracker 1.5.0 uses a search event schema only available in jCustomer 2.5.0

Bugfixes

  • Added "Project jExperience permissions" by default to the digital-marketer role
  • Fixed a UI issue happening when editing and saving a campaign
  • Updated jExperience Server Availability Probe (SAM) to better detect when jCustomer is unreachable.
  • Fixed an issue allowing personalization to be edited if its content was removed
  • Prevent jExperience Server Availability Probe (SAM) from being unregistered when SAM is restarted
  • Fixed a missing jExperience permission for users with Editor or editor in chief roles
  • Send an error notification when editing a profile with a wrong Unomi thirdparty provider configuration
  • Removed unnecessary duplicates of Video json schemas
  • No longer index jExperience interest in Jahia searches
  • Fixed an issue resulting in multiple nodes sending jExperience objects to jCustomer. Updated to only send this from the processing node.
  • The jExperience actions Add personalization and Add AB test are displayed in the header bar only when there is only one selected content.
  • Fix an issue causing a UI crash with a specific view for content set in JSP.
  • Fixed search event registration format in Elasticsearch to reduce the risk of mapping explosion

Misc

  • Updated chart.js to 2.9.