This document walks you through creating custom properties and using them to visualize in Insights.

Orbita Insights

Using Orbita Insights, we can easily perform advanced data analysis and visualize the data in a variety of charts, tables, and maps. Orbita Insights makes it easy to understand large volumes of data and quickly create and share dynamic dashboards that display changes in real-time

Custom Analytics

Using Orbita Insights, you can monitor and visualize not only the data from pre-built data properties but also the from custom properties that you created create in the Experience Designer. This document briefs you on how to create custom properties and use them to visualize in Insights

Custom Schemas are used mostly to log data but this is no longer recommended for most cases now.

Instead of Custom Schema, the Analytics Message Object could be used for adding custom data.

Data Collection

As a Voice Experience Developer you can extend the scheme fields under the an admin user, you can define your own property to capture customized data. You can have your own unique names for the properties msg.analytics.attributes.{uniqueKeyNames}.

While creating the properties, it is recommended to have structured data with 3 top-level property key names.

...

In the below example, we have passed a string, integer, boolean, object data_types within the msg.analytics.attributes property.

Place this sample code in the function node in Experience Designer.

var _ = global.get('lodash');
var  tv_series=  ['Bones', 'Psych', 'Big Bang Theory', 'Mad Men', 'Breaking Bad', 'Modern Family', 'Game of Thrones', 'Dexter'];

rndnum = Math.floor(Math.random() * 8);

node.warn(tv_series)
node.warn(rndnum)

msg.analytics.attributes = {
    'str': `this is a string`, 
    'const': 2,
    'bool': true,
    'mycontextData': {

       // 'name': `name_${_.sample(tv_series)}`,
        'series_name': tv_series[rndnum],
        'value': `value__${_.sample(tv_series)}`
    },
};
return msg;

for every agent, there will be a separate schema.

for every agent type(flow, answer), 3 properties are available. id, name, contextData.

Context data will have more properties such as state, faq, and so on.

To address the backward compatibility, some of the data is duplicated.

These new fields are not visible in the visualization.

To get the new fields, you have to click on the Refresh button.

When Sample screenshot after adding the function node to the Experience Designer.

...

Data Visualization

For insights to capture the new properties,

1. Go to Management

2. Index Pattern

3. Search for and select Voice-agent-<domain>-backend.

4. Click on the Refresh Icon.

...

...

...

Under context data, the fields are not supposed to change. If they want to change anything here, send a mail to support@orbita.ai

Attributes

Name space key is introduced so that the admin user can have their own data.

You can have your own unique names for the property names. msg.analytics.attributes.{uniqueKeyNames}

Admin should make sure that there are no conflicts with the names in the other projects.

We recommend 3 top level keys l be well structured data

going forward, we will reserve the top level name space keys for easier access.

It is recommended to have 5 branches at the maximum.

Indexed data will be kept only for 3 months. rest will be archived.

The data type values should not be different. When the same field name is used, it will work as if it has the same data type.

Data types

String (recommended), integer, boolean.

Donot use arrays

Engage Dashboard enable by default.

In insights, voiceagent.response.platformAgent.<agent_type>.contextData.<custom_field>

...

The Indexed data will be available only for 3 months, if not in use, and will be archived after 3 months.

The data from the above example code will be available at express.voiceAnalytics.voiceAgent.attributes.<custom_key>

Using these fields, you can create your visualization.

For example, to create a new visualization for the above sample code,

1. Go to Visualization

2. Click on Create new Visualization

3. Add a bucket and select the X-axis.

   Image Added

4. Select the following
   Aggregation - Terms
   field - express.voiceAnalytics.voiceAgent.attributes.mycontextData.series_name
   Click on the play button.

   Image Added

5. You will find the visualization of data on the right.

   Image Added

Save the visualization or fiddle with the options here to get the required visualization.

There could still be situations where Custom Schemas might be needed to log custom data.

For example, in situations like sending an Email where the Analytics Message Object isn’t available.

Related Articles