The Analytics 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
The Analytics section contains a counter of the following types of data:
Total Impressions: 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.
Unique Impressions: 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.
More granular skill data is available as a CSV file accessible by selecting Export to CSV icon. Your selected date range filter will limit the data included in the downloadable CSV file to the selected range.
skillPackageId - the unique identifier for the skill that ran.
skillId - the unique identifier for a particular version of skill code that ran.
key - the unique identifier to identify a particular tag in the application.
appUsername - username for user that experienced the engagement.
The file will contain the following:
time: The recorded date and timestamp (GMT) that the user saw the skill.
- skillpackageId: the unique identifier for the skill that ran.
skillId: the unique identifier for a particular version of skill code that ran.
- skillName: The name of the skill
- organizationName: The name of the organization that the user who saw the skill belongs to.
conversationId: The unique identifier that links together events that occurred while a user was in the particular context for which the skill was seen.
context: The context (location/screen) in PrecisionLender where the skill was seen.
recordType: Indicates if the data is an impression or action type.
- location: Details where an engagement is viewed.
- key: the unique identifier to identify a particular tag in the application.
- userId: The unique PrecisionLender identifier tied to the user who saw the skill.
- appUsername: username for user that experienced the engagement.
- opportunityId: The id associated with the opportunity (as shown in the opportunity URL).