IMPORTANT

Breaking changes to the Analytics endpoint

  • 18 December 2023
  • 1 reply
  • 539 views

Userlevel 5
Badge +8

We are making a breaking change to the Create a new analytics export endpoint offered by our Core API. The endpoint will now require you to specify the columns that will be present in the export. Previously, the endpoint generated an export that included all available columns.

 

In addition, three columns will be deprecated from the export: Resolution timeReplies to resolve, and Final resolution. You should use Total reply time, Replies to resolution, and Stage resolution time instead.

 

Why are we making these changes?

We are making these changes for the following reasons:

  • By explicitly specifying the columns you need in the export, future additions to the available columns will not affect your export. This ensures backwards compatibility as we continue to enrich the Analytics data. 
  • Customers who need a subset of columns in their exports can benefit from faster exports and smaller response sizes.
  • The Resolution timeReplies to resolve, and Final resolution columns are being deprecated because Front launched a feature that splits conversations into stages, so the deprecated fields no longer make sense under the new model. Use Total reply time, Replies to resolution, and Stage resolution time instead.
     

 

What do I need to do to address these changes?

 

  • Starting today: Begin using the columns fields available to the to Create a new analytics export endpoint. Read more about implementing the columns field in the next section.
  • April 1st: Your requests to the endpoint will start returning a 400 error code if the columns parameter isn’t present.
     
  • April 1st: The columns “Resolution time”, “Replies to resolve”, and Final resolution” will be officially sunset.

 

How do I make use of the columns field?

Specify the list of columns as a list of strings in the request body. Depending on the export type, “Events” or “Messages”, the list of columns is different. The full list of supported columns is available in the reference topic for both export types (events and messages) if you expand any of the options below the columns description for each export type.

{

 "columns": [

   "Activity ID",

   "Type",

   "Source"
]

...

}

 

In the example above, the export would return the Activity ID, Type, and Source columns for an Event export.

 

New columns and deprecated columns

As previously mentioned, this change also introduces new columns and deprecates ones that are no longer relevant.

 

New columns:

  • “Total reply time” column (this replaces the current “Resolution time” column)
  • “Stage resolution time” (only available to exports of type Event)
  • “Replies to resolution” (only available to exports of type Event)

Columns flagged as deprecated and not supported anymore through the “columns” parameter:

  • Resolution Time”
  • “Final resolution”
  • ”Replies to resolve”

 

We thank you for adopting the usage of the columns parameter by April 1st.

 

If you have any questions, please feel free to reply to this post.

 


1 reply

Userlevel 5
Badge +8

Follow-up post based on questions we’ve received:

 

1. What are the types of the new columns added?

They are all number types:

Total reply time - number

Replies to resolution - number

Stage resolution time - number

 

2. Are you planning on backfilling the data for these new columns?

"Total reply time" should be backfilled. On the other hand, the "Replies to resolution" and "Stage resolution time" columns are tied to conversation stages. There won't be any backfilling for these columns because these are concepts tied to this new feature. These metrics will only be computed for inboxes with conversation stages enabled (same as in the UI for all new stage metrics). To enable this data, you'll need to configure conversation stages first.

 

3. How exactly are the deprecated columns and the new columns related in terms of what they mean to an end user?

We are replacing the previous "resolution" definition with the introduction of the conversation stages feature. Whereas before a conversation didn't have stages, now conversations are split into unresolved, resolved, and no action needed stages (in the future, these stages might become customizable).

 

Given these changes, there is now a difference between the time it takes to resolve the entire conversation and the time it takes to resolve a conversation from a given stage, so we had to rework the metrics and naming conventions. But note that the stage resolution metrics will not apply to your company if you don't have the conversation stages feature enabled.

 

In essence:

  • "Resolution time" has been replaced by "Total reply time". It's present for all conversations. This column changed because we went from measuring the time to reach one resolution to measuring the total reply time across all possible stages. But this column will be present regardless of whether you have conversation stages enabled.
  • "Stage resolution time" is a new column. It is the "time from the start of a conversation segment to the last resolution". It only exists if you've enabled conversation stages.
  • "Replies to resolve" and "Replies to resolution" share the same definition. Essentially "Replies to resolution" replaces "Replies to resolve", but it now only exists if you've enabled conversation stages.

 

We know these metrics can sound similar / be tricky to digest at first. Here are some helpful articles related to conversation stages that have more in-depth examples:

https://help.front.com/en/articles/2556

https://help.front.com/en/articles/2557

Reply