Discrepancies between Zendesk Explore and Geckoboard

Important Note

If you're comparing the data on Geckoboard against a report in Zendesk Explore and it doesn't match up, first of all, make sure your dashboard's timezone is set to your Zendesk's profile time zone. Explore uses user profile time zone and Geckoboard uses the dashboard's time zone. Because of this, you may see different results in reports that use dates.

Other common reasons for discrepancies are:

Sync times

Unlike Geckoboard, Explore isn't a real-time reporting platform. In Explore, data syncs hourly for Professional plans and every 24 hours for Lite plans. Explore's new Enterprise plan has a Live dashboard that's closer to Geckoboard as its data syncs faster than every hour and all other dashboard's data sync hourly.

Geckoboard, on the other hand, syncs data every 10 minutes.

Date ranges used

Equivalent Explore and Geckoboard queries and metrics might be filtered by slightly different time ranges. For example, the default "Ticket created - Last 7 days" Explore metric looks at the last seven days starting from yesterday. This ensures that it always returns data for seven full days.

In Geckoboard, a similar metric looks at the seven days starting from today to ensure the data on your dashboard is up-to-the-minute fresh.

Field value changes reporting

Each ticket update consists of multiple field changes which are submitted by agents or automated by the system.  Explore records only one field change per update per field but Geckoboard records all changes of the field. For example, a ticket status was changed from Pending to Solved by the agent and during the same update, a trigger changed the status to Open.

In Geckoboard this ticket is considered as reopened because one of the status changes was Solved to Open. However, in Explore this ticket will not be counted towards the Tickets reopened metric as it considers the Solved status an intermediary change corrected by the trigger.

Time-period attribute filters

Some metrics in Explore allow you to pick specific time attributes for example, for First Reply Time in Explore you can pick if you want the metric filtered on Ticket updated_at date, Ticket solved_at date, etc.

In Geckoboard, time period filters are predefined for each metric. For First Reply Time we use Ticket created_at date as the question the FRT metric commonly answers is “How long does it typically take for an agent to respond to a ticket after it’s first created?” and filtering on solved_at or any other time attribute would not answer that.

SLA policies

Geckoboard calculates SLA metrics using fulfill events on the ticket metrics endpoint this differs from how Explorer calculates SLA metrics. We are currently working on matching our formula to Explore's

Was this article helpful?

Awesome! 👍 Thanks so much for your feedback!

Sorry about that! Start a conversation now.

We're ready to help, 24 hours a day, 5 days a week

Get support
  • Fernanda Customer Success Avatar


  • Hariharan Customer Success Avatar


  • Fernanda Customer Success Avatar


  • Luis Customer Success Avatar


  • Richard Customer Success Avatar


  • Fernanda Customer Success Avatar


  • Heather Customer Success Avatar