When you create a query, you must add at least one metric and optional attributes. Metrics are quantifiable values, such as the number of tickets, replies to tickets, and agent or customer wait times. Attributes are non-quantifiable values, such as ticket ID, ticket tags, and assignee names.
There are many metrics and attributes that you can use for each Zendesk product. To learn what's available, see Understanding Explore datasets.
Using metrics in queries
You can add metrics in different sizes, colors, on a dual axis, to a trend line, or include them in datatips.
You can calculate your metric results in different ways, such as summation (SUM) or count (COUNT). The aggregator in front of the metric name tells you which calculation is currently applied. Explore automatically applies a default aggregator, but you can select a new one. See Changing metric aggregators.
This section contains the following topics:
Measuring results by color and size
You can measure a metric's results in a color gradient or with different display sizes.
In the image below, Agent replies has been added as a color-encoded metric. At the upper-right of the chart, you can see how results are distributed in the color gradient.
In the image below, Agent replies has been added as a size-encoded metric. At the upper-right of the chart you can see how results are distributed in the different sizes. Size-encoding options cannot be edited.
- In the Metrics panel, click the Color-encoding icon () or the Size-encoding icon ().
- Select the metric you want to color-encode, or size-encode..
- Click the chart configuration icon ().
- Click Colors.
- From the Color encoding drop-down list, choose a new color style.
Adding a metric as a secondary axis
On some chart types, you can add a metric as a dual axis, or secondary axis. This is an easy way to compare metrics with different scales and separate results that would be difficult to analyze.
In the image, the Unresolved unreplied tickets metric uses a much smaller scale than the Agent replies and Tickets metrics. As the image below shows, the results from this metric are difficult to view.
To make data easier to view, you can add Unresolved unreplied tickets as a dual axis. This displays the metric by its own scale and visualization as displayed below:
- In the Metrics panel, click the dual axis icon ().
- Select the metric you want to use for the dual axis.
Displaying a metric's result as a trend line
Similar to a dual axis, you can add a metric as a trend line to separate results. You can also display the trend for each metric by adding trend lines in Chart configuration> Trend line.
- In the Metrics panel, click the trend line icon ().
- Select the metric you want to add as a trend line.
You can edit trend line options, including hiding and displaying values in Chart configuration>Trend line.
Restricting metric results to datatips
If you do not want a particular metric to display on the query, but still want users to be able to see the data, you can add the metric as a datatip. Any results from the metric added as a datatip will appear when a user hovers over a data point. For more information on adding and customizing datatips, see Working with datatips.
In the image below, only the replies metric is visible on the report, but when a viewer hovers over a data point, they can see the corresponding number of tickets results.
To add a metric as a datatip
- In the Metrics panel, click the datatips icon ().
- Select the metric you want to display as a datatip.
Using comparison lines to highlight metric results
Comparison lines can highlight multiple metric results for one value. When you add a comparison line, you can hover over any data point to view all results for the same X axis location. Comparison lines are useful when your attribute has several values, but your screen size cannot display each label.
- In the chart configuration menu (), select Datatips.
- Select Comparison line from the Mode drop-down list.
Using attributes in queries
Within a query, you can add attributes to the Columns, Rows, Filters, and Explosions panels.
Adding attributes to columns
Columns slice your results by the attribute's values in one chart. To add an attribute to the Columns panel, click Add, then select an attribute.
Below is an example with the attribute Ticket created - Month added as a column.
Adding attributes to rows
If you add an attribute to the Rows panel, you can see individual charts for each of your attribute's values without selecting or excluding results. You can view a value using the Row Selector to the left your chart.
Below is an example of a report with the Ticket status attribute added as a row. The value Closed is selected in the row selector.
Adding attributes to explosions
Similar to rows, attributes added to the Explosions panel break your report into individual charts based on the attribute's values. Unlike rows, explosions show all charts side-by-side. This provides a simple way to compare results, but if your attribute has several values, you should consider selecting values to display or using rows.
You can display a maximum number of 30 charts using an Explosion. If the attribute you add to the Explosions panel returns more than 30 values, apply a filter to restrict the number of values returned.
Adding attributes as filters
Attributes added as filters enable you to select or exclude values to include in the query results. Results are filtered to the values you select, but the attribute names do not appear on your query. Instead, all your applied filters are listed underneath your report. This list includes any result manipulations you create.
For example, the results below are filtered by the Open ticket status, but the attribute name is not displayed on the report.
To limit performance issues, Explore currently returns only the first 50,000 rows from a query. To successfully run the query, consider using a filter to limit the results returned.