Flow Analytics metrics and definitions

This article explains definitions for all the Flow metrics captured in Flow Analytics.

Flow Metrics

Flow analytics captures events that take place during user interaction with a chatbot. With each reported event, you can find an agent_id and thread_id. The agent_id relates to the Flow project and the thread_id relates to the interaction with a customer.

When considering the Flow event metrics like interaction, handover or resolve, you might see small variants in the reported numbers; this is expected when you compare a metric for a specific period. Sometimes a user interaction can span a longer period than you are currently looking at, ensure that you are considering the correct timeframe.

Flow Analytics Dimensions

Analytic events are separated into two dimensions: Thread and Brain events.

Thread events

The following events are tagged with the thread events dimension when there is an interaction:

EventDefinition
MESSAGE_INFlow receives a message

Note: This can be either from a customer, a moderator, or an agent (use the originator_role to distinguish).
MESSAGE_OUTA reply is sent back by the automation
LANGUAGEA language is detected (present in the language field)
COUNTRYA country is detected (present in the language field)
EVENT_OPENINGAn opening event is triggered (only supported by certain channels)
EVENT_BROADCASTA broadcast is triggered
PROJECTA new Flow project has been created
ORGANISATIONA new Flow organisation is created
INTERACTION_NEWWhen a new interaction is created
INTERACTION_UPDATEDAn existing interaction is updated
RESOLVED_BY_BOTAn interaction is resolved by the automation
RESOLVED_BY_AGENTAn interaction has been resolved by an agent
TAKEOVERA takeover/handover is applied to an existing interaction
TAG_ADDA tag is applied to a user
TAG_REMOVEA tag is removed from a user
USER_NEWA new user is registered

Specific for voice:

EventDefinition
VOICE_CALL_DISCONNECTA call is disconnected
VOICE_CALL_HANDOVERA handover is applied for a call
VOICE_CALL_CONFERENCE_ENDA call ends
VOICE_CALL_AGENT_JOINAn agent joins a call
VOICE_CALL_HOLD_ONA call is put on hold
VOICE_CALL_HOLD_OFFA call is put back from hold
VOICE_CALL_AGENT_MUTE_ONAn agent puts the call on mute
VOICE_CALL_AGENT_MUTE_OFFAn agent puts the call off mute
FieldDescription
_timeDate in a UTC format
agent_idFlow project ID
channel_idConnected channel or source ID
channel_nameType of channel
countryTwo-letter identifier of the region

For example: us
event_nameType of event

For example: MESSAGE_IN, TAKEOVER, USER_NEW, TAG_ADD
languageTwo-letter language code

For example: en
originator_roleThe originator’s role for the event

For example: SYSTEM, EXTERNAL, MODERATOR, etc.
tag_nameName of the tag that is applied
tag_valueValue of the tag that is applied
thread_idConversational thread between the bot and the customer
resolutionReason of resolution
attachment_event_nameEvent name that is triggered
timestampUNIX timestamp
event_valueRelated Payload
campaign_idBroadcasted campaign
care_conversation_idCare Conversation ID
interaction_idUnique id for every interaction

Brain events

The following events are with the brain events dimension when there is an interaction:

EventDefinition
FLOW_TRIGGEREDA specific flow is triggered
UNKNOWN_TRIGGEREDAn unknown message is received
SENTIMENTAI estimated sentiment

Note: You can find the Sentiment value in the Sentiment field.
TAG_CREATEDOld form of tags for thread params.

Note: You can find usage of it inside of text replies in the Advanced section in the right sidebar.
FieldDescription
_timeDate in a UTC format
agent_idFlow project ID
brain_nameAI model flowai for single language model

or

flowaiv2 for multilingual model
channel_idConnected channel or source ID
channel_nameType of channel
event_nameName of the event that is triggered
flow_idFlow ID that is triggered

Note: This can change between versions
flow_immutable_idUnique Flow ID that is triggered
flow_nameName of the Flow that is triggered
intent_id
Intent ID that is matched

Note: This can change between versions
intent_immutable_id
Unique intent ID that is matched
intent_labelName of the intent that is matched
languageTwo-letter language code
queryThe text utterance
step_idUnique step ID that is matched
step_nameName of the step that is matched
step_typeType of the step that is matched

For example EVENT, INTENT, ANYTHING, NOTHING, etc.
thread_idConversational thread between the bot and the customer
accuracyAI confidence matched with an intent
thresholdConfidence threshold used for matching the intent
timestampUNIX timestamp

What’s Next