Analytics - helpful to know


We try to make the metrics we present in the analytics dashboard as straightforward as possible, but they still depend on details that may be helpful for you to know. Here are a few things you should be aware of if you try to understand exactly how we come up with a certain number and the behavior of the dashboard.

There are many things that can cause the analytics results to change, even in the past. For example, if a customer replies before the inactivity time ends to a conversation that was marked as resolved, the conversation will become unresolved. 

For performance reasons, all analytics results are kept in cache for 1 hour: if you request the same metrics, you will get the same results. If you load analytics at 12:34, the same analytics will be valid until 1:34. After that, we will recompute them, and they will stay in cache for another hour.

Analytics are not fixed

Metrics displayed are not fixed, meaning that the analytics can change from one time to another due to the granularity of the segments (duration). So for example, if the inactivity period is set to 5 days and you are watching analytics for the current week, the analytics are going to fluctuate until the selected period is at least past by 5 days.

For example, in the Conversations tab, if you tagged a conversation after a selected time frame of the report, the time frame selected will still reflect the tag in the tag table.

The analytics track each teammate who replies in a conversation, regardless of the official assignee of the conversation. If a conversation is assigned to Mary, but Sophia responds because she is unavailable, Sophia will get a reaction and a response time.

If you modify a conversation, it will usually affect the analytics as expected: deleted conversations will not show in analytics; moving or tagging a conversation will affect views filtering on these inboxes. However, there are 2 exceptions:

  • As stated earlier, it may take up to 1h for the results to be updated.
  • If the conversation has become inactive, only the latest segment will be updated.

For example:

  • Paul (customer) chats with you to report a problem. You tag the conversation as #support.

  • A month later, Paul chats with you again: he is so in love with your product that he would now like to apply for a job. You tag with #job.

In this case, analytics from the previous month will not be modified.

Time range

Let's say you reply on Tuesday to a customer email received the previous Friday. If you later check the analytics for this week, we will correctly report the response time, even though the original message is outside of your requested time range.

Auto-replies are ignored by the analytics: they do not count as a reply and do not generate a response time.

When sending a sequence out of Front using a team email address, analytics will count each individual outbound message towards the team inbox's New Conversations metric, which also rolls up into the Total Conversations metric in the conversations view. 


Items that are marked as spam in Front or arrive to Front marked as spam (which gets sent automatically to trash) are excluded from analytics. 

Reply Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
Like Follow
  • 4 days agoLast active
  • 161Views
  • 1 Following

Welcome to the Front community!

The Front community is your place to come together and discuss the product, register for webinars, and get support from our help center.


New to Front or need to refresh your skills? Join us for live training sessions every week! Check them all out here.

If at any point you need assistance, please don't hesitate to email us: