It's already halfway through February(!) and time for the 5th CCE release for 2019.
- Added support to unlock 'Read Only' Campaigns within the UI
- Add Host Targeting support
- Pre-migration efforts for new Tech stack upgrades
- CCE Internationalization
- Expanded Auto Optimization capabilities
- Testing Framework improvements
- Improved handling of Highcharts component
- Bug Fixes
- Introducing new section: GOTCHA!
Read Only Campaigns
When we load a campaign in CCE, we compare source content settings and serialized content settings. If they are different, we lock the campaign as 'read only' for safety.
This update adds a notification message enabling the unlock and safe edit of such campaigns. On click of the unlock option, a modal presents showing the original and updated versions.
Selecting "edit" will present the Campaign Wizard allowing updates to the previously in-editable campaign. Once you have finalized the campaign through the wizard steps, selecting "Save & Proceed" will save the campaign with the new format.
Note, we only support variation in `conditions`.
'Host Definition' in Config Settings
We have added support for 'host' definition as Content Condition, thereby allowing dynamic 'host' setting being passed to the module.
Whilst modules are generally defined/ organized by Site, a common practice for deployment is to push to a staging or test environment - a varied site or host definition - prio to a production launch.
This new capability removes the additional steps required for testing and roll out prior to the deployment to the production environment. For further information, refer to the updated 'Context' section within the Content Setting Conditions wiki page.
Tech Stack upgrades
Furthering our performance and efficiency improvements of CCE, we are continuing the evolution our technology stack. Whilst we won't bore you with all the technical details here (...zzz!), the intended result is something I think we can all appreciate:
- Reduced Memory and CPU footprint
- Increased responsiveness of the CCE Interface
Internal tests show a marked improvement in Memory, CPU reductions and GUI responsiveness with this release. Now you have more time and resources to manage other, non-CCE tasks !
Continued Internationalization
Following the support for Japanese Language in Cxense Insight, and the extraordinary response from our Japanese Customers (Domo arigato!), we're continuing the process of internationalization of the CCE application.
As Text and language forms the basis of most communication throughout an application, it is important to ensure consistency and appropriateness of message. A very special thanks to the Cxense Japan for your assistance on the continued i18n project !
Expanded Auto Optimization capabilities - ML+AI=ROI !
Building on the huge leap for auto optimization from 2018 (Cxense delivers auto optimized recommendations capability using Machine Learning and Artificial Intelligence.), we are continuing the expand the capabilities and configurations included in the ML reach or 'touch points'. This results in further improvements in CTR and engagement.
In time, we will be sharing more detail regarding the use and performance benefits of Cxense Auto Optimization - stay tuned !
Big Fixes
Article Performance Report
Bugfix for a nuance in URL structure : In some instances, the impression counts within the Article Performance Report excluded some prefixed URLs. >> Solved!
Setting Page
The Settings page was inaccessible on some modules. >> Solved!
UI slowness
The CCE GUI had reduced performance on Engage modules with high campaign counts. >> Solved!
Introducing a new release notes section, the GOTCHA!. Every so often, we find the internet throws the odd curve ball or two. This new section highlights some of the foibles we've encountered that may also help your digital implementations.
GOTCHA!
The first Gotcha is dedicated to IE11. It was reported some elements delivered from an Engage Module were not rendering as expected. It turns out the Javascript handling in IE has trouble with the shorthand declaration:
item = data.response.items[0];
The solution is especially simple:
var item = data.response.items[0];
If you deliver 'personalized message' experiences via CCE using the above method to IE11 Users they may not be able to see the intended experience - in some circumstances.
Happy Customer Engagement!
Simon and the CCE Team.
Comments
0 comments
Please sign in to leave a comment.