Differential conversation extracts from PureCloud

[Lloyd]

Looking for some guidance with a bit of an issue we have in our efforts to do incremental PureCloud data loads to our data warehouse.

At the moment we have configured a daily extract using the following API:

api/v2/analytics/conversations/details/query

We pass a date range interval to cover the rage we want to extract, for example this is what we would pass to get yesterday’s data (NOTE: the range is converted to a UTC date):

‘2021-06-29T12:00:00.000Z/2021-06-30T12:00:00.000Z’

The extract is running fine but we are having an issue were additional interactions are added to the data after we have run the extract. It looks like the date range that is passed is only in reference to the conversation start date:

This means that if for example an email is added to an interaction a few days later we simply miss that update under our current implementation.

In a perfect world I think we would like to be able to change that API to use something like a ‘conversation updated at’ date rather than the ‘conversation start date’ but I cant find anything like that in the documentation.

Wondering if there was something I've missed, or an alternative way I had considered?

Thanks

[anon11147534]

Hi Lloyd,

This is the standard behaviour of the API. Interactions can span several days so it's possible that items can be added a few days after the initial request.

The presence of conversationEnd time is an indication that the conversation has finished. If a conversation doesn't have this property then consider the conversation to be "live" and there may be further updates to it in future. Your implementation will have to be adjusted to take this into account.

[Lloyd]

Cool - Thanks for clarifying/confirming that Ronan