LiveLike

The LiveLike Developer Hub

Welcome to the LiveLike developer hub. You'll find comprehensive guides and documentation to help you start working with LiveLike as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Livelike Analytics Dictionary

Created by: Livelike Analytics Team

This document is built with an intention to provide an overview about the content of the LiveLike Analytics dashboard so that the users are aware of different KPIs which are being shown on the dashboard

Overview Tab

  1. Period - This is the period that can be further broken down into day, week or month as per the user’s choice in the filter section provided on the page.

  2. Clients - These are the number of new clients which LiveLike has tied up with for the respective time period.

  3. Applications - These are the number of applications that are created under each organization in either of their environment like production, testing, etc.

  4. New Users - These are the new users who were present during a particular event on our client applications. Also, note that some of the users might be dummy users which might have been created during the initialization of an application from the customer side.

  5. Active Users - These are the users who were active during an event or we can say these users must have interacted with at least 1 widget or seen a widget getting published.

  6. Program - These are the number of programs created inside an application.

  7. Chat Rooms - These are the total number of chat rooms that got created during a particular program. Please note that these are the list of chat rooms which are created by the Admin.

  8. Widgets - These are the total numbers of widgets that were pushed during an event from LiveLike producer suite.

  9. Interactions - This number depicts the total interactions that happened across all interactable widgets which got published during a program.

  10. Unique Interactions - A unique interaction is counted only when a user interacts with any interactive widget, such as Textquiz, Textpoll, Imagepoll, etc. The unique interactions are calculated here on a month level instead of application level or widget level which you will see in the next tabs/sections in the dashboard. We don’t record interaction on the below widgets -

    1. Alert
    2. Rich Post
    3. Social Embed
    4. Twitter Spotlight
    5. Video Alert
    6. Follow-Up Widgets
  11. Impressions - These are the total number of impressions that got recorded when a widget appears on the users’ timeline or screen.

  12. Unique Impression - These are the total number of unique impressions that got recorded when a widget appears on the users’ timeline or screen. Here we are calculating these metrics on a monthly level. For example - Let’s suppose a user Max was present during multiple events in a particular month or timeframe we are going to consider him only once in this KPI (The same logic is applied on Unique Interactions as well)

  13. Engagement % - This metric has been calculated using this formula - Unique Interactions / Unique Impressions

Applications Tab

  1. Month - This is the timeframe which user has selected to view their KPI or data in the dashboard.
  2. Application Name - This is the application name under which several programs are hosted or scheduled. All organizations have multiple applications like Production application, Testing application, etc.
  3. Organization - This is the organization name that is assigned in LiveLike CMS.
  4. New Profiles - This number depicts those users who were created newly in a particular organization. These profiles didn’t exist before the particular timeframe set in the dashboard.
    a. Returning Profiles - The small sized numbers in this columns are the count of those profiles which return after a particular event.
  5. Profiles (Profiles Active Count) - These are the total numbers of profiles that got created for a particular organization in a particular time frame.
  6. Total Profiles Active Count - These small sized numbers in this column are the total number of profiles which got initialised during a particular event.
  7. Unique Impressions - A unique impression is then counted when a widget is published from the producer suite and a user sees that widget. For example - If a user sees multiple widgets during a particular event they will be counted only once, not multiple times.
  8. Total Impression Count - This small sized numbers are Total impressions count which got registered on a particular widget published
  9. Unique Interaction - Definition for this KPI is the same provided in the Overview section at the top. For user comfortability, filters have been provided in the dashboard for the Interactive & Non - Interactive Widgets. Users can group them into 1 single bucket based on their choice. Also, the Unique Interaction is calculated on an application level unlike the monthly level described above
  10. Total Interaction Count - This is the count of total interaction which got registered on the widgets
  11. Engagement - This metric has been calculated using this formula - Unique Interactions / Unique Impressions
  12. Application Client ID - This is a unique 40 digit alpha-numeric key which is assigned to each application. If anyone wish to see the ID assigned to each of their application then they can visit the Livelike CMS producer.
  13. Organization ID - This is a 36 digit alpha numeric key which is assigned to each of the organization to uniquely identifier to each of the organization.

Widgets Tab

  1. Widget Kind - These are the widgets that were published during a program by the producer suite.
  2. Widget - These are the questions/feeds that are being displayed to the users when a particular widget is been published.
  3. Program - These are the list of all the programs that were published or scheduled in a particular organization in the producer suite.
  4. Application - This is the application name under which several programs are hosted or scheduled. All the organizations have multiple applications like Production application, Testing application, etc.
  5. Widget Published - This is the timestamp when a particular widget is been published to users. These are customizable to different timezone like UTC, EST, IST, etc. as per the user’s choice. This option is default set to UTC timezone.
  6. Unique Impressions / Interactions - This is similar to the above what we have used on Page 2. But in this scenario, the users will be counted on each widget. This logic will capture each unique impression of each and every user on each widget level.
  7. Engagement % - Calculation of this metric will be similar to the one which we have used on Page 1 & 2 i.e., Unique Interactions / Unique Impressions
  8. Widget ID - This is a unique 36 digit alpha-numeric ID which is been assigned to each widget when they get published
  9. Program ID - This is a unique 36 digit alpha-numeric ID which is tagged to each program created by you in Livelike CMS
  10. Application Client ID - This is a unique 40 digit alpha-numeric key which is assigned to each application. If anyone wish to see the ID assigned to each of their application then they can visit the Livelike CMS producer.
  11. Organization ID - This is a unique ID given to each of our customers
  12. First & Last Impression At - This is the time when the event recorded the first and last impression during a particular event respectively
  13. First & Last Interaction At - This is the time when an event recorded its first and last interaction during a particular event
  14. Total Impression/Interaction Count - It is the count of total impressions or interactions on widget level in a particular program
  15. Timezone - This columns depicts which timezone is set by the user who is viewing the data on the dashboard. Note that by default the timezone is UTC. User can change it to some other timezone which might suit their needs or analysis.

Updated 2 months ago

Livelike Analytics Dictionary


Created by: Livelike Analytics Team

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.