Metrics and attributes for Zendesk Guide

Return to top

41 Comments

  • Steve Tilley

    Hi!

    I'm currently trying to build a bit of a handover dashboard and want to show a count of the top problem IDs for the last 12 hours.

    Is there a way to get a metric to filter when tickets were initially marked as incidents and assigned to a problem ID?

    Thanks!

    0
  • Dane
    Zendesk Engineering
    Hi Steve,
     
    You can try to use this formula to extract such tickets. 
     
    IF ([Changes - Field name] = "type"
    AND ([Changes - Previous value]=NULL OR [Changes - Previous value]="Question")
    AND [Changes - New value]!="Incident")
    THEN [Update ID]
    ENDIF
     
    Afterwards, modify this simple query depending on your preference.
     

     
    0
  • Brianne Reinhardt

    Is there a recipe for upvote count, downvote count, vote date, and user role, name, email for article votes? I see it for the Community posts, but not the articles.

    1
  • Christine Felicia
    Zendesk Engineering
    Hey Brianne, 
     
    The current dataset only provides the net votes (SUM of upvotes and downvotes) and calculating them separately is not yet possible.

    Also outlined in Metrics and attributes for Zendesk Guide:

    Votes currently reflect the sum of upvotes and downvotes. For example, if you had ten upvotes (which each add one vote to the total) and five downvotes (which each subtract one from the total), this metric would return "5".

     
    In Q3 we will roll out the article upvotes and downvotes metrics. We're working on it as we speak, you may follow this similar feature request that is already marked as Planned by our Product Managers.
    -1
  • Laura

    Hey,

     

    In the Team Publishing metrics, the metric Articles published has the following formula:

    IF [Publishing event type - Unsorted]="Translation published" THEN [Event article ID] ENDIF

    I thought this was a mistake. The metric says that it counts the number of articles that have been published and not the translations that have been published. Yet when reviewing the metric in Explore, the formula is the same.

    Should it not be

    IF [Publishing event type - Unsorted]="Article published" THEN [Event article ID] ENDIF

    and then a second metric for Translations published?

    Or maybe I am misunderstanding this. Could someone please enlighten me on this?

    Thank you in advance!

    1
  • CJ

    Laura Yep, you are 100% correct, it makes no sense. It's been broken for over a year, I've had a ticket open and they know and don't consider it a priority to fix or even publicly post information that it's broken. It's honestly shocking. There's other bad formulas too and they just don't care. Chat Wait time has been broken equally long, and Chat Concurrency AVG has never worked. Zendesk has made it very clear that functional, accurate metrics are not a priority. 

    0
  • Laura

    Hello, again community. I could use your help.

    I am trying to create some custom reports from the Knowledge Base dataset, but to do so, I think I need a better understanding of the metric 'Articles Viewed'. This is precisely where I fall over, as there are a few items that don't appear logical to me.

    Metric: Articles viewed - formula: [Views ID] + [Views locale]

    1. the formula uses the aggregator D_COUNT. Does this mean that the formula calculates the number of values of the attribute 'Views ID' plus the number of values of the attribute 'Views locale'?
    2. Views locale means 'the ZD locale setting of the article viewer'. Our KB has 10 different locales. Will the D_Count value of 'Views locale' never be higher than 10?
    3. I pulled both attributes used in the metric separately: D_COUNT of 'Views ID' (=490) and D_COUNT of 'Views locale' (=10). Their total (=500) is a lot lower than the result of Articles Viewed (=2298).
      How is the metric adjoining both attributes calculated? It cannot be a simple summation of two D_COUNT(Attribute) Values.

    I get the feeling that there is a very basic understanding of the formulas that I am completely missing here, but as much as I try to wrap my head around it, it doesn't make sense to me.

    Could anyone out there help me with this?

    Thank you very much in advance.

    0
  • Dane
    Zendesk Engineering
    Hi Laura,
     
    You can check if you have any other attributes included in the query that you have created. I have tried the same approach and it gave me the individual values correctly. Just in case it still has the same behavior, please contact our support directly to look into it further. 
     

    0
  • Laura

    Hello Dane,

    Thanks for your feedback.

    When working with the Guide dataset, I often get the feeling that there is a part I don't get, so you can imagine that I'm relieved to read that there seems to be an issue with the results rendered!  I'll check this right away.

    0
  • Camila

    Hi, 

    I have a question regarding the metric clicks by query, I know it is the amount of clicks after the user searched, wondering if is the number is an avg of users that click after searching for a certain word, example: "bug" or can it be the same user that's searching the same word and then clicking on many places? 

    0
  • Elizabeth Brown

    Hi Zendesk,

    I've set up a report of the top 200 searches of Guide with no results, to deliver to me monthly.

    In my first delivered result, I have a lot of entries that have 0 results reported, and also entries with no number indicating how many times folks searched for it.

    I can make sense of someone searching for the same term multiple times w/ no result - that generates a number in this report.

    What does 0 results reported, OR a blank result, mean? Did folks search for this term or not?

    I'm guessing they did, otherwise Zendesk wouldn't report it at all. But why is it shown w/ 0 or null result? Can you explain please?

    Appreciate being able to view more than the top 5 "searches with no result" through the report. Failed searches are vital to improving the content in Guide so an important feedback mechanism.

    Cheers

    E. A. Brown 

    1

Please sign in to leave a comment.

Powered by Zendesk