SciVisum enables users to configure parameters every step of the way in their Dynamic User Journeys on SciVisum Monitoring Portal, providing an unprecedented level of detail and allowing for very fine grained investigation and control.

The main rollout this month was the ability to set performance parameters for individual steps within a dynamic user journey.

This was developed with our super user community who really get down to the fundamental nuts and bolts of both the technical workings of the site and the front end user experience. These users need more detail than most people who look at overall journey time, as they are fine tuning every aspect of performance. When working at this zoomed in level the overall journey time can" hide a multitude of sins” within the delivery of each step, especially on a long and complex journey.

When talking to clients about development they had concerns such as such as:

“I want to be able to see which particular steps are causing a journey to fail.”

“I want to see if there are steps within a journey that are taking too long for good customer experience even if the entire journey does not fail.”

“Some steps are more important than others within a journey (whether in terms of value, user experience or KPIs) so we need to be alerted if they are running slowly.”

“I want to be able to receive alerts for slow running or failing steps, not just entire journeys.”

“Where a journey has a slow running step but still completes within its overall cut off time I would like the step to be marked.”

Some steps, for example “search” are more important to user experience (and keeping users on the site) than others, and may cause other issues to manifest later in the journey depending on certain variables such as number of options chosen, so now users can easily configure these parameters to suit their requirements and will be alerted if there is a problem with any step within the overall journey.

We have also rolled out the following upgrade with this new release:

Visible Maintainence Periods

The SciVisum Monitoring Portal allows administrators to set "Planned Maintainence Exclusions"(or PMEs) to define time-lines, during which:

- the data collected can be filtered to exclude it's effect from your overall availability and delivery times
- alerts can be disabled

By using PME settings for all of your planned and intended outages - you can ensure that a Journey reports as 100% Available, even though it had errors, so long as the errors occurred only in the PME time windows that are not considered true downtime within your organisation. These excluded errors can still be viewed and investigated if needed.It is still possible to still allow alerting when you configure PME windows - this can be useful for any predictable time periods where Errors may occur and you wish to be notified for support, annotation, recording or analysis purposes, but the impact of errors in these timelines is not considered true downtime within your organisation.

There are Ad Hoc PME Windows:

- ones that you create for a one-off event
- e.g. for a planned maintenance slot coming up

and Recurring PME Windows:

- for predictable events - such as a weekly overnight batch process on your site which causes Journeys to fail and trigger Alerts you don't wish to receive
- for predictable events that briefly cause Journeys to run slowly, and you want to ignore that from calculating overall Delivery Times

The default is now set to have PME windows visible on the Wallboard and Live Status (they are displayed as grey bars) but administrators can choose to display data to users without the PMEs showing.

Request Demonstration

View our client testimonials If you would like one of our service professionals to contact you to arrange a demonstration of our web testing services or discuss your web site performance goals/needs free of charge please contact us. To contact a service professional call us on +44 (0) 1227 768276 or request a telephone/email call back