New flexibility to Agillic configurators
Release 18.1 focuses on flexibility, stability and performance. It features brand new possibilities within the Agillic Email Editor, allowing configurators more flexibility in their daily work. And we know many of you will appreciate the UX improvements, as well as notable performance improvements to the data-look-up and one-to-many.
Get to know Agillic 18.1
Email template upgrade
The 18.1 release introduces an improvement to the Agillic Email Editor. It is now possible for a template developer to enable a configurator to make changes that were not previously possible. Examples are:
- Change the colour of an element. This means that you can now change background colours and colours of the call to actions. Previously it was necessary to develop more of the same block with different colours. Now you will only need one block.
- Work with background images. Whether on the template or on blocks, you can change a background image behind elements. For example, if you have a text element and an image behind it.
- Change the meta tags of a template. Meta tags are used whenever you share on social media. Now you can write your own headline and description and use your preferred image whenever you share.
This is just to name a few things which can now be enabled. Essentially it is now possible to change any value of any attribute on a template through the content editor. A few things to discuss with your template developer could be: Widths, Heights, Sizes, Colours, Images, Borders, Classes, Styles, Texts, Links
UX improvement: Close all tabs option
Many of you have expressed that they would like it to be easier to close all tabs. We have also observed that under certain circumstances, having many tabs open may slow down page loading time.
In this release, we are introducing a new "Close all tabs" button that sits quietly to the outer right of the tabs list. When clicked, it closes all tabs open in the current view, except tabs that have "unsaved changes". That means you will not risk losing changes unexpectedly.
UX improvement: Validation of email subject line
We have implemented several validations that help and guide email editors to minimise the risk of human error when using merge-fields to personalise subject lines with person data, global data or promotions. Similar validation is added when using subject line test.
New ‘List unsubscribe feedback’ experience
We have updated the way Agillic handles "list unsubscribe feedback" from email clients.
Previously, Agillic would handle a "list unsubscribe feedback" by setting the person data "COMPLAINT" to "True" and setting the "COMPLAINT_DATE" + firing any event added to the "list unsubscribe event list" that can be administered in "System settings" → "Email" → "unsubscribe".
Now, Agillic will handle a "list unsubscribe feedback" by setting the person data "UNSUBSCRIBE" to "True" and setting the "UNSUBSCRIBE_DATE" + firing any event added to the "list unsubscribe event list" that can be administered in "System settings" → "Email" → "List unsubscribe".
When migrating customer instances to this behaviour, we are also aligning existing recipient person data to the new behaviour using the following logic:
IF a recipient has used "List unsubscribe" in the past with the result that "COMPLAINT" has been set to "True" AND is still "True" + "COMPLAINT_DATE" is set, THEN the following happens:
"UNSUBSCRIBED" PD field will be set to "True" and "UNSUBSCRIBED_DATE" is set to the same value as "COMPLAINT_DATE" has. "COMPLAINT" should be cleared, "COMPLAINT_DATE" should be cleared.
Can this article be improved? Please let us know, and we will update the article
Please sign in to leave a comment.