Understanding analytics exports
Analytics exports represent activity within your business hours. As a reminder, Front lets you define business hours: the time when your team is expected to reply to customers. Reaction time, response time and resolution time that happen outside of your business hours are counted as 0. Business hours are always defined according to your current time zone.
Like integrations, you need to be an admin in order to create analytics exports.
Front can generate CSV exports of your data from the Analytics dashboard.
Go into your Analytics, and select Export.Step 2
This popup window is where you can tell Front what report type you want exported. You can choose from three types of reports - Messages export, Full events export, and Daily volume export. You can also specify what columns of information you want to include in the export; by default, all columns will be selected.
When you're ready, click Request export. The file will begin preparing, and you will click the download button when it's done preparing. The export will always be generated in your timezone.
About the Message Export CSV
The exported file will contain one line per message received in the time period you selected. Below is an explanation of each column in your CSV.
- Message ID: internal Front ID of the message
- Conversation ID: internal Front ID of the conversation
- Segment: segment of the conversation (see below)
- Direction: inbound or outbound
- Status of the conversation: references the action done by the assignee archived or open
- Inbox: address of the inbox. If you export multiple inboxes and the message appears in several inboxes, it will be listed once for each inbox
- Message date: formatted as YYYY-MM-DD HH:mm:ss, in the requested users timezone
- Reaction time: time (in seconds) taken to respond or reassign a conversation
- Resolution time: sum of the response times (in seconds)
- Response time: amount of time (in seconds) it took for a reply to be sent to an inbound message
- Attributed to: username of the teammate involved, if any (if the teammate archived the conversation but didn't reply)
- Author: username of the teammate who replied to the email
- Contact name: contact's first & last name
- Contact handle: contact's email address, twitter handle, or phone number - depending on the source of the message
- To: email address of the recipient
- CC: email address of those CC'ed on the email
- BCC: email address of those BCC'ed on the email
- Extract: sample of the message body (200 character limit)
- Tags: tags attached to the conversation
- Message API ID: external Front ID of the message
- Conversation API ID: external Front ID of the conversation
- New conversation: indicates whether this message is the first of a new conversation or segment - 1 stands for yes, 0 stands for no
- First response: indicates whether this message is the first reply to a new inbound conversation or segment - 1 stands for yes, 0 stands for no
- Replies to resolve: number of replies to inbound messages that exist in a resolved segment. Multiple outbound replies sent in a row will only count once as a reply
- Business hours: indicates whether the message occurred within business hours - 1 stands for yes, 0 stands for no. This column is accurate as of 9/25/18, when it was implemented
Some channels (like chat or SMS) do not have a real notion of conversations. Customers will always be replying in the same conversation, even if they want to talk about something new. Front solves this by tracking inactive conversations - when a conversation stops receiving messages for a while, we consider it to be inactive.
If you then receive a new message, we will create a new segment. Nothing will happen in the app; the new message will appear as expected and the conversation will be unarchived. However, in the analytics, it will be treated as a new conversation.
The exported file contains the segment sequence. You will see the sequence increase every time the conversation becomes inactive and then active again.
If you export multiple inboxes, it is possible that some messages appear in several of these inboxes. In this case, they will be listed once per inbox.
Move/tag or delete conversations
If you modify a conversation, it will be reflected in the export as expected. Deleted conversations will be ignored if:
- You receive a message and 1 hour later tag the conversation, the export will list the message as having the tag.
- You move the conversation to a different inbox, the export will list the message as part of this new inbox.
However, after a conversation becomes inactive, the previous segments stop being modified. For example:
- A customer sends you a text message about a delivery issue.
- You tag the conversation with #delivery and handle the problem.
- Two weeks later, the same customer reports a billing issue.
- You remove the #delivery tag and add the #billing tag.
If you then export both messages, the first one will still have #delivery, while the second will have #billing.
I haven't found a better place to write this message and I think it will be relevant here. Have you thought of integrating with Segment.com ?
We need Front to communicate with clients while keeping analytics. We need to set Front as a "source" in Segment, so that we can aggregate those analytics with our other systems.Reply