Release 1.8
Release Version | v1.8.x |
Release Date | |
Previous Version | v1.7.1 |
Active Patch Version | v1.8.1 |
Version 1.8 of Amplify includes bug fixes, improvements and new features to the system.
What’s new in 1.8
Insights
In 1.5, we announced the feature of session tracking (see Release 1.5 | Amp-session-tracking). Now we are releasing the first visual overview of that data to all users on a Business or Enterprise plan.
An ‘Insights’ button is now available in the dropdown on any Live amp. Once people start interacting with your live amp, insights such as responses to questions, number of sessions, country and device data and time spent can be seen on the insights page.
Insights are filtered based on the selected domain and the selected date range, and can be exported as PDF and JSON.
Example of the amp insights view
Conditions and Storage
Working with condition nodes and defining the value to check for has formerly been dependent on the user adding the value as text, which could lead to spelling errors and inconsistencies.
Condition nodes now provides you with a dropdown of values, which are defined inside the selected storage. A custom/non-defined value can still be added by simply typing it into the field.
Additionally, the storage key can now be adding into text nodes by clicking the :storage: icon in the text toolbar to fetch the user selected value, if previously defined. Renaming storage keys are now also supported and changes are reflected across the amp.
Linking to webpages via the Go To node
With this release it is possible to link the user to a different page on the current webpage and then continue the conversation from there. This can be done via the new “Links” tab in the popover of the Go To node.
The new links tab in the Go to node settings enables the editor to guide the user to different webpages.
Other notable improvements
We have made improvements to how nodes are displayed in the Review document PDF.
Improvements to the line calculations between nodes in the amp builder to avoid overlapping lines.
For the most cases, we try to mend the conversation tree, when nodes are being deleted. If this is not possible, e.g. when a node has multiple paths, we have implemented a popup to make sure the user is aware that all children will be deleted.