Why do I see discrepancies between Insights and Explore?
There are several reasons why you may see slightly different numbers in Insights and Explore. The most common reasons are:
- Time zones. Explore uses user profile time zone but Insights uses the account's default time zone. Because of this, you may see different results in reports that use dates. See Which time zone does Explore use? and Which time zone does Insights use? articles for more details.
- Sync Times. Neither Explore nor Insights are real-time reporting platforms. In Insights, data syncs every 24 hours for Professional plans, and one hour after the last sync ended for Enterprise plans. In Explore, data syncs hourly for Professional plans and every 24 hours for Lite plans. The platform that performed a sync more recently will contain more recent data.
- Date ranges used. Equivalent Explore and Insights 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 Insights, a similar metric looks at the seven days starting from today.
- Backlog dataset date. In Insights, the backlog data is collected once a day at the last data sync of the day and is shown as the backlog for the next day. In Explore, the backlog data is synced every hour, which allows seeing the unsolved tickets backlog of the last sync of the current day and it corresponds to the date at which it was collected. When comparing backlog data by date, you will see that dates in Insights are shifted forward by one day compared to Explore.
- 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 Insights records all changes of the field, which is normally not necessary. 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 Insights 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 because the Solved status was an intermediary change that was corrected by the trigger.