Analytics - helpful to know & FAQs
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. To learn more about analytics, see here.
Analytics refresh (Cache)
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.
Analytics are refreshed every hour or whenever a new query is run. For example:
1. If you go to analytics right now, it will pull the latest data
2. If you revisit the same report anytime within the next 1 hour, you will see the same cached data
3. If you revisit the same report anytime after 1 hour, the analytics report will be refreshed
4. If you revisit the same report but add a new criterion (ex. include this new channel), analytics will then recalculate
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.
Other reasons for metrics changing might be adding/removing a tag, unassigning, and archiving. 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.
Example 1 - Conversation tagged:
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.
Example 2 - Conversation moved between inboxes:
- A customer sends a message to the Support inbox. After 15 minutes, a support agent assigns it to themselves, then takes 1 minute to reply. The 16 minutes that passed between the customer's message and the agent's reply are attributed to the support agent as their response time, with a 1 minute handle time.
- Next, the agent needs to escalate the conversation, and moves it to the Engineering inbox. An engineer replies to the customer 10 minutes later, and took 2 minutes to write their response. That Engineering teammate will not have a response time, because there was no new inbound message between the Support reply and the Engineering reply, but the engineer will have a handle time of 2 minutes.
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 are excluded from analytics.
If you are out-of-office, any replies that customers send in conversations that are assigned to you will automatically be unassigned and return to the original shared inbox they came from. Thus, you will not personally accrue response or reaction times because the conversation is not assigned to you anymore.
However, teammates can still manually assign conversations to you while you're out-of-office, which does accrue response and reaction times.
Moves between Teams
When you move conversations from Team A to Team B, analytics are computed for the time that they were in a certain Team. In other words, all analytics are computed for Team A while the conversation is in Team A; and after the move to Team B, all analytics are computed for Team B.
When you delete/block a teammate their historical data will be preserved.
Making individual inbox analytics visible
By default, the analytics of an individual inbox is not exposed and cannot be incorporated into a team analytics report. An admin or the owner of the individual inbox can update the individual inbox settings to make it visible. Making an individual inbox visible in analytics will allow admins to track the performance of teammates who primarily work and communicate out of their own inboxes, rather than a shared team inbox.
Team reports use team contacts
In the Customers tab of a team analytics report, the list of customers is populated from the saved team contacts in your contact manager. See the Customers tab page for more details.
Do individual inboxes show up in the default Team Inbox report?
No, it does not. If you're looking to create a team report that includes individual inbox metrics, you'll want to first make sure that individual inbox has enable "Make inbox visible in the analytics". Second, you'll need to create a custom analytics report and select all the inboxes you want to have included.
Historical analytics available retroactively if you upgrade
If you upgrade from a plan that does not have analytics to a plan that does have analytics, the historical analytics data from the time you were on your previous plan will be available. Likewise, if you downgrade your plan and re-upgrade in the future, the analytics will still be available from when you had a non-analytics Front plan.
If you merge a conversation, the conversation is also merged in analytics. This means that metrics like response times could change following a merge.
Analytics does not include private tags
The Tags filter for Analytics reports offer team tags only, and not private tags. You currently are not able to run reports on your private tags.