Overview

The Metrics section of the skill page allows you to view data about your skill's performance, providing visibility into its usage and the value it is (or isn't) providing to your users. This article will cover how to view and access this data.

 

In this Article

 

Counter Definitions & Filters

This shows the metrics section of the skill page

The Metrics section contains a counter of the following types of data:

  • Impressions - Total: This counts the total number of times the skill was seen. For field tags, the user needs to click on the field tag (or Andi® window if the field tag only displays in the window) to log as an impression.

  • Impressions - Unique: This counts the total number of unique users who have seen the skill.

  • Actions: This counts the number of times users took action after seeing the skill, such as clicking the link to an article or URL that is returned.

This data can be filtered based on a Date Range of the past 7 or 30 days, as well as a custom date range. The default filter selection will be the past 30 days.

A few important things to consider about impressions:

  • As long as the skill runs and returns a result, even if not the desired result, an impression will still be logged. Andi® executes based on logic in the shouldIRun and run files, so it is up to skill writers and testers to ensure that if your skill is supposed to return a certain result, a calculation for instance, that, that result appears and not something different (such as a blank response). 

  • Impression data can take a few moments to appear after the skill runs and is seen and/or action is taken. If after a period of time, data does not appear, check the skill history for any potential skill errors

 

Data File

More granular skill data is available as a CSV file accessible by selecting the Download icon. Your selected date range filter will limit the data included in the downloadable CSV file to the selected range. 

Shows the download icon

The file will contain the following:

  • time: The recorded date and timestamp (GMT) that the user saw the skill.

  • skillId: The unique identifier for the skill package that ran.

  • conversationId: The unique identifier that links together events that occurred while a user was in the particular context for which the skill was seen.

  • userId: The unique PrecisionLender identifier tied to the user who saw the skill. 

  • context: The context (location/screen) in PrecisionLender where the skill was seen.

  • recordType: Indicates if the data is an impression or action type.

  • engagementText: The text response shown to the user for a conversational skill.

    • If blank, this could mean that your skill is running, but not returning the desired result. 
  • engagementURL: The hyperlink provided to the user for a conversational skill if the response contains a URL.

    • If a response contains more than one URL, then the impression data will show the hyperlink of the first URL that appears, but the action data will show the hyperlink of the URL the user selected.

    • If blank, this could mean that your skill is running, but not returning the desired result. 
  • organizationName: The name of the organization that the user who saw the skill belongs to.

  • contextId: Within the named context, the unique identifier for where the skill was seen. For example, in the opportunity context, this will be the equivalent of the opportunityId.

Was this article helpful?
0 out of 0 found this helpful