Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Insert excerpt
_ExcerptAnalyticsDashboardsOverview
_ExcerptAnalyticsDashboardsOverview
nopaneltrue
 

Panel
borderColor#eeeeee
bgColorwhite
titleColorwhite
borderWidth1
titleBGColor#232323
borderStylesolid
titleIn this page

Table of Contents
depth2

What is Looker?

Looker is Google's BI tool for visualizing and displaying data. For more information about Looker, see the Looker resources page.

Note
titleEmbedded view
Vonage's Analytics Dashboards uses Looker's embedded view. Not all of the functionality in Looker's default experience as described in the documentation is available in the embedded view. 

What are dashboards?

A dashboard is a collection of tiles, displaying data about agent events or interaction events. Analytics Dashboards offers two types of dashboards:

  • Default. 
    Insert excerpt
    _ExcerptAnalyticsDashboardsDefault
    _ExcerptAnalyticsDashboardsDefault
    nopaneltrue
     
  • Custom. 
    Insert excerpt
    _ExcerptAnalyticsDashboardsCustom
    _ExcerptAnalyticsDashboardsCustom
    nopaneltrue

Image Added

What are tiles?

A tile is a single item on a dashboard. Tiles can be one of two types:

  • Text tiles contain static text. 
  • Visualization tiles contain configured data and have various configuration options. For more information see What visualization options are available for tile? section later this page.

Visualization and text tilesImage Added

What data can be displayed in tiles?

Insert excerpt
_ExcerptAnalyticsDashboardsTiles
_ExcerptAnalyticsDashboardsTiles
nopaneltrue

A tile can contain one type of data at any time—agents events or interaction events. 

Tile dataImage Added

Agent events

Each row of data represents a single event for an agent. Agent events can be one of two types—presence and interaction—and each event also has a category:

  • Presence
    • Ready
    • Away
    • ExtendedAway
    • LoggedOut
  • Interaction
    • Ringing
    • Connected
    • Wrap
    • Unexpected
    • Failed

Other agent event data includes start time and date, duration of event, and agent ID. Average, maximum, and minimum duration, and count measures are also available.

For a complete list of agent event fields and their descriptions, see Agent Events fields.

Interaction events

Each row of data represents a single interaction. Interactions can have channels, events, start and end dates, and so on. Interactions have many more dimensions and measures than agent events.

For a complete list of interactions fields and their descriptions, see Interaction Events fields.

Interaction model

Interaction event data describes every call or other type of interaction in a 4-layer structure, each with its own properties or fields:

  • Interactions
    Each interaction has information applicable to the interaction as a whole. Information includes when it started, its status—completed, ongoing, internal error—and its direction—inbound, outbound or internal.
    Interactions have one or more channels:
    • Channels
      A channel represents a party who is connected or attempted to be connected to the interaction. If a party leaves and rejoins, there are two channel instances associated with that party. A party can be external, an agent, or a monitor (a supervisor monitoring an interaction).
      Channels have one or more channel events:
      • Channel Events
        A channel event represents each human or system activity instigated by or affecting the channel—party—or the interaction. Examples of channel events include Ringing, DeliveryFailed, Connected, Applet, Queue, Held, CallRecording, Disposition, Wrap. Multiple channel events can occur at the same time. For example, a Held channel event can occur within a Connected channel event.
        Each channel event has a type, an offset (by default, in milliseconds from the start of the interaction), and a duration (by default, in milliseconds). Queue, Applet and some other events carry a Customer-defined Name
        • Channel Event Properties
          Some channel events, specifically Queue channel events, have additional properties. A queue channel event has a result—for example, HangUp, Delivered or a range of breakouts—a list of presented skills, and virtual queue (or agreement) names.

All interactions have a conversation GUID. A conversation GUID connects all interactions that make up a conversation. For example, a conversation may contain an initial phone call and a callback—both interactions will have the same conversation GUID, but different interaction GUID.

What visualization options are available for tiles?

Tiles display data in different forms, or visualizations. Visualizations can be divided to different types, where each type has different settings you can use to customize its look. Different data works better in some visualizations than others.

Image Added

Visualizations can be of following types:

  • Cartesian charts
    • Column

    • Bar

    • Scatterplot

    • Line

    • Area

  • Pie and donut charts
    • Pie

    • Donut Multiples

  • Progression charts
    • Funnel

    • Timeline

    • Waterfall

  • Text and table
    • Single Value

    • Single Record

    • Table

    • Table (Legacy)

    • Word Cloud

  • Maps
    • Map
    • Static Map (Regions)
    • Static Map (Points)
  • Other charts
    • Boxplot

For detailed information about each Looker's visualization types, see Visualization types (Looker help).

Where does data come from?

Analytics Dashboards are powered by the same data used in Dashboards—Insights Stats API.

Who can access Analytics Dashboards?

Users can have either view or create access to Analytics Dashboards.

The number of these different types of licenses depends on your package type (Express, Essentials, Select, and so on), contract type (named or concurrent) and number of seats. You can buy more licenses. For more information, contact your Account Manager.

Users who do not have an access to Analytics Dashboards can still benefit from its data. You can schedule delivery of dashboards to any user, by providing their email addresses. For more information, see Scheduling delivery of Analytics Dashboards.

What are the current limitations of Analytics Dashboards?

Note
iconfalse

Functionality

  • Agent events and Interaction events show an agent's ID only, not their name.
  • Cannot report by Group or Skill.
  • No clear ownership of Analytics Dashboards: All dashboards can be viewed (and potentially edited) by all users with access to Analytics.
  • Personal Dashboards not accessible: User can create personal dashboards in Looker—these are inaccessible within VCC.
  • Models require steep learning curve. Event-based models are the most flexible, but require a deeper understanding.
  • Embedded version of Looker does not contain exactly the same information as described in Looker's documentation.

Process

  • Vonage has to assign viewer and creator licenses.
  • Analytics Dashboards no longer work when the data model is updated.