Zingtree Tags: reporting

Updates: Reporting Enhancements, API Tweaks

updates-blog

Being able to see how much time and money you are saving with Zingtree makes us all feel good and useful. So this past week we’ve been working with some of our customers to make reporting cleaner.

Here’s what’s new with reporting:

  • Fix: All Tree Stats, Clicks and Usage and Popular Nodes now using same measurement techniques for engagement (Olivier).
  • Fix: Session Detail report now shows duration from first click (Jane A.).
  • Update: Added Agent Details to All Agents report.

Our APIs and integrations also needed a few tweaks to help solve some business problems for our customers. Here’s what’s new on the API side:

  • Fix: Zendesk session ID stuffer leaves existing session IDs in place in case of error submitting ticket form (Iggy).
  • Fix: Back button keeps data entry field values. (Chrispy).
  • Update for Zendesk tag matching (Jorge).
  • Update: /api/tree-tag-search.php now takes a minimum number of tags to match (Jorge).
  • Update: Zendesk API now returns a blank instead of “false” if no session IDs present (Bryan M.).
  • Fix: API for tree tag matching strips trailing commas from search string.
  • Update: Tree tag matching now returns results in alphabetical order.

Got any great ideas? Chat us up!

Decision Tree Analytics: About Results Reports

Zingtree has powerful built-in analytics. In this series, we’re taking a closer look at some of these in-depth reports and how they help you learn even more about how customers use your trees. 


Results Reports

The Results Report allows you to quickly and easily measure the overall performance of your decision trees, based on the last node visited during a session. With a powerful labelling system, you can tag your nodes as a “success,” “failure,” or an “unknown result” to generate the report.

Before getting started, go here to learn how to label your nodes:

http://blog.zingtree.com/how-to-measure-results-of-your-decision-trees/

To access this report, go to Overview > Reports and select Results from the dropdown menu. You can specify an exact date range to pull the stats from before clicking “Show Report.”

The report will generate immediately, showing you a complete overview of your results in a pie chart. Hover over each section to see the statistics for each success, failure, and incomplete or unknown result.

You’ll also find a breakdown of the engagements, sessions started, and sessions with button clicks within that given date range. Please note that changing the category of any node — for example, from “success” to “failure” — will automatically update the report.


Learn more about our powerful reports and analytics:

Reach out to us any time with questions!

Updates: New Button Click Traffic Report, Designer Enhancements and More

updates-blog-image

This latest Zingtree update is once again powered by our clever customers. We just take the ball and run with it.

Here’s what’s new this week:

New Traffic (Button Clicks) Report

For each node, you can see how often each button is clicked for any date range.  Also, you can walk through your tree and see clicks for the next node. Thanks to Elise M. and Matthew S. for the suggestion.

Designer Updates

We’ve made the color palette better, and the root node is now a unique dark shade of green.  Thanks to Corey D. for the inspiration.

Also New and Notable

  • Fix: Mobile output looks better due to a meta tag scaling fix
  • Update: Reports list ordered by popularity
  • Fix: Super user status not always recognized in My Trees (h/t Trey H.)
  • Update: Added content-question and content-answer classes to tree output for more CSS control over question and content areas. (h/t Kolja W.)
  • Fix: Breadcrumbs links went back one step too far. Fixed. (Cris M.)
  • Update: Session Notes now turn red if there’s a previous note, shows previous note. Also appears in Session List, Session Data reports. (h/t Florent N.).
  • Update: Added API for Session Notes extraction
  • New: Settings now has a Language option to ensure Back button and Email Node fields are localized properly (h/t Mike H.)

Got a great idea? Send it to us, and watch it magically appear in the next update!