Add metric cards

You can, among other things, add metric cards to dashboards to quickly evaluate metric values, such as the number of clicks for a city in particular for the current week compared to the previous one.

Add metric cards in usage analytics dashboards

  1. In an existing dashboard, access Edit mode by clicking Edit in the upper-right corner.

    Note

    In a new dashboard, the report is in Edit mode by default.

  2. In a section, click Add card to section to access the Add a Card dialog.

    Tip

    You can also duplicate an existing card with copy16px, and then only modify what needs to be different.

  3. In the Add a Card dialog:

    1. Select Metric.

      Example

      You can create a metric card representing the number of clicks for a city in particular.

      Admin-MetricCardb
    2. In the first input, enter a meaningful Card title (for example, Clicks in Seattle).

      Note

      When you leave the box empty and save the dashboard, the card title will be the name of the selected metric (for example, Click Event Count).

    3. Under Metric, click the dropdown menu, and then select one metric to be shown in the metric box (for example, Click Event Count). You can do one of the following:

      • Click the links (Search, Click, and Custom) to quickly browse metrics by event category, and then select the one of your choice.

        Note

        Custom data can only be leveraged when using the UA Protocol. If your Coveo implementation uses the Event Protocol, custom event types shouldn’t be added to a report since they won’t function as expected.

      • Click All, and then use the Filter box to find and select the metric of your choice.

    4. (Optional) In the Advanced Settings section:

      • Click filter-add-2, and then create one or more dimension filters (for example, City is Seattle).

      • When you want to see trend data relative to the previous equivalent period as the one that’s currently selected, select the Display trend data option.

        The trend value appears next to the metric value as a percentage with an up or a down arrow respectively indicating an increasing or a decreasing trend.

        Admin-UATrendValue2

        The option is turned off by default, because calculating the trends increases the dashboard complexity and slows down the dashboard generation. Enable this option when you really want it.

      • 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.

    5. Click Add Card.

      Note

      Relevance 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:

        Admin-ColoredMetricsValuesb
  4. 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
Analytics - Dimensions
Analytics - Reports
Organization - Organization

View

Edit dashboards

Analytics - Analytics data
Analytics - Dimensions
Organization - Organization

View

Analytics - Reports

Edit

Analytics - Administrate

Allowed