jExperience 2.3.0 is a maintenance release that include a lot of new features for developers and marketers. It is compatible with jCustomer 1.6.x
Digital Marketers
Personalized lists
It is now possible to personalize content lists: right-click on any content list, select "convert to personalize list". This feature can be used in 2 ways:
- Hide or show content items within a list depending on visitor profiles
- Reorder content items, using the sorted by score strategy, to display the best matching content first
Nested personalizations and AB Tests
It is also possible to create a personalized list inside an AB test or a personalization; and the other ways around: AB Test inside a personalization, personalization inside an AB Test, etc..
Control Group - Beta
Control groups allow marketers to exclude a percentage of the traffic from a personalization, to ease reporting and analytics of personalizations. Visitor profiles will be randomly added to a control group for a personalization depending on the percentage set by the business user. The information related to the control group is available in the data layer, so you can use it in your analytics.
New condition: Click events
In the condition builder, available in personalization, segmentation and scoring, you can now use tracked clicks events to filter your audience. The new condition is available under behavioral => time based events => Visitor has clicked on.
To track clicks on your site, developers can find the relevant information on Jahia Academy.
Developers
New documentation
A new version of jExperience developer documentation has been published on the Jahia Academy. It contains additional details as well as tutorials about wem.js, jExperience javascript tracker.
Enrich jExperience data layer
New methods were added to jExperience javascript tracker (wem.js) to allow the digitalData object to receive additional objects or properties and get these new objects/properties handled by wem.js. You can refer to the developer documentation on Jahia Academy for more details.
Groovy actions
Apache Unomi (and jCustomer) 1.6.0 introduced support for Groovy action, jExperience was also updated to allow groovy actions to be deployed automatically for your module.
You can do so by placing .groovy
files inside your module’s META-INF/jexperience/groovy/actions
folder.
For the full changelog please visit store.jahia.com or take a look at the jexperience-2.3.0 release notes page.