Sackellares_Tracy | 2023-09-21 18:09:18 UTC | #1
We are trying to create an on prem call history. We were told by Genesys that a SessionId is unique to a single ConversationId. The diagram found on the Developers Forum appears to support that statement. https://developer.genesys.cloud/blueprints/conversation-model-to-sql-blueprint/
In the data we have pulled from the API's for our dialer campaign, we have many SessionId's that have many ConversationId's. However, when we pull up examples in the PureCloud Interactions report, it shows only one ConversationId.
We need to understand how PureCloud Interactions is connecting the ConversationId and SessionId to produce a unique join. Thank you.
jaguilera | 2023-09-27 19:57:23 UTC | #2
Tracy
Conversation Detail - Duplicate Session IDs
Sackellares_Tracy | 2023-10-11 14:28:30 UTC | #3
I am familiar with the thread you referenced. It is a user that provided the feedback 'Depending on the dialing algorithm, the system will batch up several outbound call requests into a single request, as a result we get the same session id. Session Ids are not always unique to a conversation id.'
In the Pure Cloud Interaction report, it presents one conversation for session id's where we have multiple conversation id's in data. We need to know how that report is generating only one record/wrap up.
system | 2023-11-11 14:26:09 UTC | #4
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 22072