Full Events Export

Term: Full Events Export
Meaning

One of three report options when exporting data. Organized by each activity that occurred and its corresponding details for the selected date range.

 

Full events exports include the following activity: 

  • Inbound
  • Outbound
  • Out Reply (outbound message that is a reply) 
  • Archive / Reopen
  • Reminder
  • Trash / Restore
  • Assign / Unassign
  • Tag / Untag
  • Move
  • Comment
  • Mention
  • Snooze
Location

Report Dashboard

Calculation The time measurement shown in the export is in seconds.
Example Export data to further analyze in Excel or a business intelligence tool
FAQ

The exported file will contain one line per event in the time period you selected. Below is an explanation of each column in your CSV.

  1. Activity ID*: Internal Front ID of the activity
  2. Type: Describes what activity occurred (see list above)
  3. Source: Where is the activity coming from
  4. Message ID*: Internal Front ID of the message
  5. Conversation ID*: Internal Front ID of the conversation
  6. Segment: Segment of the conversation
  7. Direction: Inbound or Outbound
  8. Status: Current status of the conversation: Archived or Open
  9. Status at activity time: Status of the conversation at the time the activity was recorded (eg., if a conversation was Archived, the status at activity time would have been Open).
  10. Inbox: Name of the inbox where the message currently lives. If the message appeared in multiple inboxes, the activity will appear one time for each inbox value.
  11. Inbox at activity time: Name of the inbox where the message lived at the time the activity was recorded. If the message appeared in multiple inboxes, the activity will appear one time for each inbox value.
  12. Message date: Formatted as YYYY-MM-DD HH:mm:ss, in the requested user's timezone
  13. Autoreply: Indicates whether this message is an automated reply, 1 is yes, 0 is no
  14. Reaction time: Time (in seconds) taken to assign/reassign an inbound message to another teammate (not to self), send a reply, or archive
  15. Resolution time: Duration (in seconds) that a contact was kept waiting for a reply from the team during a conversation segment
  16. Final resolution: Indicates whether this event is an the last resolution of a segment, 1 is yes, 0 is no. If the conversation receives a new inbound, a resolution can stop being the final resolution for this segment.
  17. Handle time: Duration (in seconds) between opening a conversation and sending a reply
  18. Response time: Duration (in seconds) between an inbound message and the next outbound message in the same conversation
  19. Attributed to: Username of the teammate involved, if any (if the teammate archived the conversation but didn't reply)
  20. Assignee: Username of the teammate who was the assignee for this conversation
  21. Author: Username of the teammate who replied to the email
  22. Contact name: Contact's first & last name
  23. Contact handle: Contact's email address, twitter handle, or phone number (depending on the source of the message)
  24. To: Email address of the recipient
  25. CC: Email address of those CC'ed on the email
  26. BCC: Email address of those BCC'ed on the email
  27. Extract: Sample of the message body (200 character limit)
  28. Tags: Tags currently attached to the conversation
  29. Tags at activity time: Tags attached to the conversation at the time the activity was recorded
  30. Activity API ID: External Front ID of the activity
  31. Message API ID: External Front ID of the message
  32. Comment API ID: External Front ID of the comment
  33. Conversation API ID: External Front ID of the conversation
  34. Message original ID: Message-id as defined in the email headers of a message (email only)
  35. New conversation: Indicates whether this event is the first of a new conversation or segment, 1 is yes, 0 is no
  36. First response: Indicates whether this message is the first reply to a new inbound conversation or segment, 1 is yes, 0 is no
  37. Business hours: Indicates whether the message occurred within business hours, 1 is yes, 0 is no
  38. Subject: Subject of the conversation

 

*These columns in the export may be phased out in the future, as they are the Front analytics system's internal identifiers and should pose no impact to customers.

Reply Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
Like Follow
  • 2 wk agoLast active
  • 541Views
  • 1 Following