We are doing the BULK exports. For that we querry conversations via analytics API with the interval. Eventually we get to the point where we need to process attributes for the conversations obtained -> hence we fetch conversations individually via ConversationAPI-> get conversation(ID)
Question:
If I search the same conversation via
ConversationAPI -> get conversation (id)
analyticsApi -> get conversation (id) / or interval quering with filter on convId
not only there is a diff in presence of attributes but the participants' purpose changes. In some cases where we used the analytics query, for participants, the purpose changes from "outbound" to "dialer.system" when same conv is obtained via conversaion API
How can it be so and what is the difference ?
I am not sure whether this change has always been so or this is smth new.
Thank you in advance
Please open a case with Genesys Cloud Care to investigate the data discrepancies in your org. Customer data cannot be investigated in this public setting. Care will need the specific request and response bodies along with correlation IDs and approximate timestamps for the requests that demonstrate the discrepancy.
I can generically say that Genesys Cloud provides data as a service, meaning that it should be correct and accurate at the time it is received. If further events happen in the system, the data will be updated accordingly and will be different when retrieved again, but still correct at the time it is retrieved. This scenario is particularly common when retrieving conversations that are in-progress and then re-fetching the data again after the conversation has ended and wrap-up codes are applied, for example.
thank you for your reply
This question is of General thread. many of our clients have this.
I am positive that data integration is not a question here Either.
I am fetching data that is 1+ month prior to today so the recount and indexation should definitely be correct
The same conversations ( there are many) through the different API listed show changes
The purpose is not smth that should change in theory so why is this the case when conversation has been closed long ago. It does not seem like a data update either. Analytics can state the purpose as "outbound" while conversationAPI shows it as "system" or"dialer.system"