Genesys Cloud - Main

Hello!

I'm responsible for building out reporting for our Genesys Cloud implementation, and I'm finding that in the last week or two we have Session_IDs within the Particpant Session data that are repeats. The Conversation IDs are different, participant data....That's led me to believe I have a bug since when compared to the grand total of call volume, these duplicated Session IDs represent less than 1%, but when I brought it up to someone they informed me that Session IDs are not globally unique, and are only unique per Conversation ID. My world has been turned upside down, and I can't find in documents to confirm one way or the other. 

Hey Daniel,

I was able to find an older migrated post from the Dev forum that has some additional info, including this useful diagram with some primary / foreign key relations.

I hope this was helpful.

Hello!

I'm responsible for building out reporting for our Genesys Cloud implementation, and I'm finding that in the last week or two we have Session_IDs within the Particpant Session data that are repeats. The Conversation IDs are different, participant data....That's led me to believe I have a bug since when compared to the grand total of call volume, these duplicated Session IDs represent less than 1%, but when I brought it up to someone they informed me that Session IDs are not globally unique, and are only unique per Conversation ID. My world has been turned upside down, and I can't find in documents to confirm one way or the other. 

Thank you. I was afraid this was the case, but at least I now know. We've been building our database out with assumption of Session ID being unique, and joining tables using only that. It sounds like we need to make a new key that is a combination of Conversation ID + Session ID. 

Hey Daniel,

I was able to find an older migrated post from the Dev forum that has some additional info, including this useful diagram with some primary / foreign key relations.

I hope this was helpful.

Hello!

I'm responsible for building out reporting for our Genesys Cloud implementation, and I'm finding that in the last week or two we have Session_IDs within the Particpant Session data that are repeats. The Conversation IDs are different, participant data....That's led me to believe I have a bug since when compared to the grand total of call volume, these duplicated Session IDs represent less than 1%, but when I brought it up to someone they informed me that Session IDs are not globally unique, and are only unique per Conversation ID. My world has been turned upside down, and I can't find in documents to confirm one way or the other. 

Yeah. ConversationID will be a unique primary key, with session_ID being another key that you can use to associate with an interaction. I'd love to hear back from you once you've been able to successfully set up your own data system!

Thank you. I was afraid this was the case, but at least I now know. We've been building our database out with assumption of Session ID being unique, and joining tables using only that. It sounds like we need to make a new key that is a combination of Conversation ID + Session ID. 

Hey Daniel,

I was able to find an older migrated post from the Dev forum that has some additional info, including this useful diagram with some primary / foreign key relations.

I hope this was helpful.

Hello!

I'm responsible for building out reporting for our Genesys Cloud implementation, and I'm finding that in the last week or two we have Session_IDs within the Particpant Session data that are repeats. The Conversation IDs are different, participant data....That's led me to believe I have a bug since when compared to the grand total of call volume, these duplicated Session IDs represent less than 1%, but when I brought it up to someone they informed me that Session IDs are not globally unique, and are only unique per Conversation ID. My world has been turned upside down, and I can't find in documents to confirm one way or the other. 

We found the same "problem" (session id not unique), unfortunately after we had filled the database with lots of data. We have to changed our database schema and plan to use participant_id + session_id as the primary key. My question: Is the participant_id unique over the org or do we need the conversation_id to create the primary key? 

------------------------------
---------------------------------------------
Hans-Gerd Sandhagen
Software Developer
Fiebig GmbH
---------------------------------------------

Original Message:
Sent: 08-20-2025 14:40
From: Jason Kleitz
Subject: Session ID - Globally Unique?

Yeah. ConversationID will be a unique primary key, with session_ID being another key that you can use to associate with an interaction. I'd love to hear back from you once you've been able to successfully set up your own data system!

------------------------------
Jason Kleitz
Online Community Manager/Moderator

Original Message:
Sent: 08-20-2025 09:39
From: Daniel Pisani
Subject: Session ID - Globally Unique?

Thank you. I was afraid this was the case, but at least I now know. We've been building our database out with assumption of Session ID being unique, and joining tables using only that. It sounds like we need to make a new key that is a combination of Conversation ID + Session ID. 

------------------------------
Daniel Pisani

Original Message:
Sent: 08-19-2025 16:55
From: Jason Kleitz
Subject: Session ID - Globally Unique?

Hey Daniel,

I was able to find an older migrated post from the Dev forum that has some additional info, including this useful diagram with some primary / foreign key relations.

I hope this was helpful.

------------------------------
Jason Kleitz
Online Community Manager/Moderator

Original Message:
Sent: 08-19-2025 15:23
From: Daniel Pisani
Subject: Session ID - Globally Unique?

Hello!

I'm responsible for building out reporting for our Genesys Cloud implementation, and I'm finding that in the last week or two we have Session_IDs within the Particpant Session data that are repeats. The Conversation IDs are different, participant data....That's led me to believe I have a bug since when compared to the grand total of call volume, these duplicated Session IDs represent less than 1%, but when I brought it up to someone they informed me that Session IDs are not globally unique, and are only unique per Conversation ID. My world has been turned upside down, and I can't find in documents to confirm one way or the other. 

#Reporting/Analytics

------------------------------
Daniel Pisani
------------------------------

Interesting! Since I haven't yet fixed ours----is there a reason you chose Participant ID + Session ID instead of Conversation ID + Session ID? We were going to do the latter, but if Participant ID + Session ID is better....I want to make sure I don't set something up I need to re-adjust all over again. 

*Oop. Now I see that you were also asking this same question. Yeah, I'm very curious on this now too. 

------------------------------
Daniel Pisani

Original Message:
Sent: 08-21-2025 01:02
From: Hans-Gerd Sandhagen
Subject: Session ID - Globally Unique?

We found the same "problem" (session id not unique), unfortunately after we had filled the database with lots of data. We have to changed our database schema and plan to use participant_id + session_id as the primary key. My question: Is the participant_id unique over the org or do we need the conversation_id to create the primary key? 

------------------------------
---------------------------------------------
Hans-Gerd Sandhagen
Software Developer
Fiebig GmbH

Original Message:
Sent: 08-20-2025 14:40
From: Jason Kleitz
Subject: Session ID - Globally Unique?

Yeah. ConversationID will be a unique primary key, with session_ID being another key that you can use to associate with an interaction. I'd love to hear back from you once you've been able to successfully set up your own data system!

------------------------------
Jason Kleitz
Online Community Manager/Moderator

Original Message:
Sent: 08-20-2025 09:39
From: Daniel Pisani
Subject: Session ID - Globally Unique?

Thank you. I was afraid this was the case, but at least I now know. We've been building our database out with assumption of Session ID being unique, and joining tables using only that. It sounds like we need to make a new key that is a combination of Conversation ID + Session ID. 

------------------------------
Daniel Pisani

Original Message:
Sent: 08-19-2025 16:55
From: Jason Kleitz
Subject: Session ID - Globally Unique?

Hey Daniel,

I was able to find an older migrated post from the Dev forum that has some additional info, including this useful diagram with some primary / foreign key relations.

I hope this was helpful.

------------------------------
Jason Kleitz
Online Community Manager/Moderator

Original Message:
Sent: 08-19-2025 15:23
From: Daniel Pisani
Subject: Session ID - Globally Unique?

Hello!

I'm responsible for building out reporting for our Genesys Cloud implementation, and I'm finding that in the last week or two we have Session_IDs within the Particpant Session data that are repeats. The Conversation IDs are different, participant data....That's led me to believe I have a bug since when compared to the grand total of call volume, these duplicated Session IDs represent less than 1%, but when I brought it up to someone they informed me that Session IDs are not globally unique, and are only unique per Conversation ID. My world has been turned upside down, and I can't find in documents to confirm one way or the other. 

#Reporting/Analytics

------------------------------
Daniel Pisani
------------------------------