Add table cards
Add table cards
usage analytics (UA) dashboards offer many ways to review the data collected by Coveo Usage Analytics (Coveo UA) (see Review and manage dashboards).
You can, among other things, add table cards to dashboards to quickly list dimension values such as the queries that lead to the creation of a support case.
Add table cards in usage analytics dashboards
-
In an existing dashboard, access Edit mode by clicking Edit in the upper-right corner.
NoteIn a new dashboard, the report is in Edit mode by default.
-
In a section, click Add card to section to access the Add a Card dialog.
NoteYou can also duplicate an existing card with the icon, and then only modify what needs to be different.
-
In the Add a Card dialog:
-
Select Table.
ExampleYou can create a table that presents the top items viewed during visits that resulted in a case deflection.
By creating content that answers these queries, you can significantly improve the case deflection trend inside your organization (see Use Case: Create a Dashboard Linking to the Visit Browser).
-
In the first input, enter a meaningful Card title.
NoteWhen you leave the box empty and save the dashboard, the card title will be Table (for example,
Top Items Viewed During Visits That Resulted in a Case Deflection
). -
Under Dimensions and Metrics, click the dropdown menu, and then do one of the following:
-
Click the links (Search, Click, and Custom) to quickly browse dimensions and metrics by event type, and then select the one(s) of your choice.
Custom data can only be leveraged when using the UA Protocol. If you’re using the Event Protocol, keep in mind that custom fields have been replaced by predefined events and dimensions. To learn more about the available protocols, see Track usage analytics.
-
Click All, and then use the Filter box to find and select the dimension(s) and metric(s) of your choice.
-
-
(Optional) In the Advanced Settings section:
-
Click , and then create one or more dimension and/or metric filters.
Examples-
Custom Event Value is caseCreate
-
User Query is not blank or n/a
-
City is Seattle
-
-
In the Value Destination Link and Header Destination Link boxes, set destination links when clicking table values or title .
-
Select the following options: Column header and Row count column.
Notes-
When you select the Column header option, the selected dimensions and metrics names appear in the table header.
-
When you select the Row count column option:
-
(if the Column header option is selected) the number of different results appears in parentheses next to the dimension name, for the selected date interval and filters.
-
(if the Column header option isn’t selected), the row number appears next to the dimension value.
-
-
-
Select the Sort direction to be Ascending or Descending.
-
When you report on a custom event and on a search or click event (you added a filter or selected a dimension or metric related) at the same time, or on an all event category metric or dimension (for example, Unique User IP and Browser), choose to Create a relation using the Last search or the Visit between the event categories.
Notes-
We recommend that you select Last search in situations where the last query performed by the user is the reason why they did the custom event.
For example, in Salesforce, when agents attached a result to a case (
caseAttach
), the last query they made gave them the results they used to do the custom event. -
We recommend that you select Visit in situations where all the queries performed by the user during the visit didn’t resolved their matter.
For example, when one of your clients creates a case (
caseCreate
), they, more often than not, tried to get the information they needed by querying on the subject of their matter before doing the custom event. You can then use these queries to create knowledge base article(s) and therefore fill the content gap. -
The Create a relation using parameter has no effect when you report only on search and click events.
-
Last search links each custom event to the query immediately preceding (if any) and Visit links each custom event to all queries performed during the user visit in which the custom event happened.
-
-
-
Click Add Card.
NoteRelevance metrics (Average Click Rank, Search Event Clickthrough, and Relevance Index) values (if any) have a color that represents if the value is good (green), neutral (black), or poor (red) depending on predefined thresholds.
The predefined thresholds for each metric are the following:
-
Average Click Rank: 1-3 = good (green), 3-6 = neutral (black), and > 6 = poor (red)
-
Search Event Clickthrough: > 60% = good (green), 40-60% = neutral (black), and < 40% = poor (red)
-
Relevance Index: > 0.7 = good (green), 0.5-0.7 = neutral (black), and < 0.5 = poor (red)
For example:
-
-
-
Back on the dashboard, click Save in the upper-right corner.
Required privileges
The following table indicates the required privileges to view and edit dashboards from the Reports (platform-ca | platform-eu | platform-au) page and associated panels (see Manage privileges and Privilege reference).
Note
Access to dashboards or part of their content may be further restricted as a function of the member (see Manage access to reports and Manage permission filters). |
Action | Service - Domain | Required access level |
---|---|---|
View dashboards |
Analytics - Analytics data |
View |
Edit dashboards |
Analytics - Analytics data |
View |
Analytics - Reports |
Edit |
|
Analytics - Administrate |
Allowed |