D_COUNT is often the default metric aggregator in Zendesk Explore because it provides a unique count of items, which is generally more useful for accurate reporting.
For example, when counting the total number of tickets an agent has updated with a comment, using DCOUNT ensures that each ticket is counted only once, avoiding inflated numbers due to duplicates. While COUNT can be used for total counts, DCOUNT is preferred for unique counts, which is why it might be set as the default in some cases.
COUNT and DCOUNT are both aggregation methods used in Zendesk Explore, but they serve different purposes. COUNT simply counts the total number of items in a dataset, while DCOUNT counts only the unique items. For example, if you have a list of…
You should use D_COUNT when you need to count only unique items in your dataset. This is particularly useful if you expect an item, like a ticket ID, to appear multiple times and you want to ensure it's only counted once. For instance, if you're…
In Zendesk reports, COUNT and D_COUNT are aggregated within each cell when attributes are placed in rows or columns, rather than for the report as a whole. For example, if you have tags like 'Cat', 'Dog', and 'Bird' across different tickets, COUNT…
In most cases, using COUNT or DCOUNT for rated satisfaction tickets in Zendesk Explore won't make a difference, as both will count the number of ticket IDs. However, if you're using a dataset like Ticket Updates and calculated metrics, DCOUNT…