Explore features time and date calculations that help you to analyze results over a period of time. Both of these calculated metrics are configured in the calculations menu ().
Time comparison calculated metric
- Results against the previous month.
- Results against the same month in the previous year.
- Results against a rolling 12-month average.
A time comparison calculated metric can only use reference metrics from the original dataset, not any calculated metric.
- A name for the metric.
- The metric you are comparing data from.
- Your date field. The date field is a date attribute containing the time periods you would like to measure. In the example below, the calculation is measuring the number of replies by when the ticket was created.
- The offset level. The offset is the time category that will appear on your chart and what your results will be measured against.
- The offset start and end. The offset start and end points are the values the calculations begins and stops measuring at. For example, an offset start point of one would begin measuring at the first Year value. An offset end point of three would stop measuring at the third Year value.
On the column chart below, you can see the time comparison calculated metric and the number of replies. Because the offset start point is twelve, the first twelve months of the time comparison metric are empty.
Time comparison calculated metrics are particularly useful in metric comparison visuals such as KPI, gauge, and bullet charts (see Chart types for comparing metrics). Time comparison calculated metrics are dynamic, so they will react to interactions and filters. For example with date filtering, the offset will remain the same no matter what time period the viewer looks at.
Date range calculated metrics
Date range calculated metrics create totals for a specified period of time. They are useful for looking at metrics with ranges that don't fit into a calendar period, such as the last seven days, the previous seven days, or dates that differ year-to-year like Easter.
When specifying the period of time for a date range calculated metric, you have two different options, simple and advanced.
With the simple option, you can select from a list of named periods or use Custom to select a specific calendar start and end day, month, or year.
With the advanced option, you can select separate beginning and end dates. For each beginning and end date, you can select from a list of named periods, enter in a calendar date, view all history, or select a rolling period. In a rolling period, you can select date ranges like seven days in the past or a year in the future.
You can also repeat the selected range.
14 Comments
Hey @...
Hope you are well.
I can't see the ''Compute separately' option in Date range calculated metric. Has it been removed?
This is what I'm seeing, the scroll bars are right down:

Hi Vladimir Petrushenka, thanks for this feedback. You're right, I can no longer see it also. If you don't mind, I'm going to open a ticket on your behalf so we can find out if this was intentionally removed and when. I'll cc myself on the ticket and update the docs when we hear back. Thanks again!
That's great, thanks for this, Rob!
I was in the Ticket Updates dataset earlier and it didn't allow for the use of the Date Range Calculated Metric - is that expected?
Hi Janaya,
The Date Range Calculated Metric should still work in the Ticket Updates dataset.
As a test, you can try creating a simple date range calculated metric by following this setup:
Choose a date range and make sure to change the metric from SUM to COUNT as well.
Apologies Giuseppe,
I think I've left an important detail out, I can go to date range calculated metric on Support: Ticket updates [default] dataset, but I can't seem to choose a ticket based on the pending status, only for tickets solved and tickets created and the requester would like to have a tickets pending calculated metric as well. Can you advise if this is possible?
Thank-you!
Hi Janaya,
Thank you for the update. The Tickets Solved and Tickets Created Metrics under Ticket Updates dataset are part of the default Metrics, which is why you see them right away.
If you'd like to add a similar Metric for Pending tickets, the formula would most likely be something like this:
Calculated Metric Name: Tickets Pending
But first, we will have to create a Ticket Pending - Timestamp calculated attribute. Again, we can mirror the Ticket Solved - Timestamp as follows:
Calculated Attribute Name: Ticket Pending - Timestamp
You should now be able to use these Metric and Attribute under Date range calculated metric.
Thank-you Giuseppe, when I have a moment I'll give this a try :)
Does anyone know if the preset "Simple" ranges include the current day?
If you use "Simple" as your date range, it will only include the current day if you select Today or designate a range including the current date on Custom.
Hope this helps.
Cheers,
Dane
Is there a way to create custom time brackets?
For example- there are built-in "Requester wait time brackets", but we're looking for better granularity. Can I modify these with a formula? Thanks
Yes, this is possible. Kindly see the instructions addressed in the article "Explore recipe: Displaying tickets answered within different time brackets" - https://support.zendesk.com/hc/en-us/articles/4408825149466-Explore-recipe-Displaying-tickets-answered-within-different-time-brackets
Please, feel free to adapt this to your use case. I hope this helps!
Hi Gabriel,
That's not quite what I'm looking for. I acknowledge the existence of brackets in my question, but what I'm asking is can we customize the brackets themselves?
For example:
Requester wait time brackets have groupings such as 1-3 days, 3-7 days, >7 days
We want to make requester wait time brackets that are 1-2 days, 2-4 days, 4-7 days, etc.
Can this be done?
If you click on the eyeball by the attribute you will be able to see how the formula is constructed which you can then take and create your own formula with whatever time brackets you are looking for.
Best regards,
Please sign in to leave a comment.