Hello everyone,

We have recently identified an information gap between the "conversation" and "job" APIs of Genesys and we would like to know if other customers have encountered the same problem. Have you noticed any discrepancies in the data provided by different Genesys APIs? If so, have you found a workaround to ensure data consistency?

Thank you in advance for sharing your information.

Hey Lionlel,

Do you have any examples of your own? That may help other in the community help with sharing their workarounds.

Hello everyone,

We have recently identified an information gap between the "conversation" and "job" APIs of Genesys and we would like to know if other customers have encountered the same problem. Have you noticed any discrepancies in the data provided by different Genesys APIs? If so, have you found a workaround to ensure data consistency?

Thank you in advance for sharing your information.

Hey Lionlel,

Do you have any examples of your own? That may help other in the community help with sharing their workarounds.

Hello everyone,

We have recently identified an information gap between the "conversation" and "job" APIs of Genesys and we would like to know if other customers have encountered the same problem. Have you noticed any discrepancies in the data provided by different Genesys APIs? If so, have you found a workaround to ensure data consistency?

Thank you in advance for sharing your information.

Your example is expected and documented here:  https://developer.genesys.cloud/analyticsdatamanagement/analytics/jobs/conversation-details-job#differences-to-conversation-detail-queries

The more real time details endpoint does not contain custom participant attribute data.

Hey Lionlel,

Do you have any examples of your own? That may help other in the community help with sharing their workarounds.

Hello everyone,

We have recently identified an information gap between the "conversation" and "job" APIs of Genesys and we would like to know if other customers have encountered the same problem. Have you noticed any discrepancies in the data provided by different Genesys APIs? If so, have you found a workaround to ensure data consistency?

Thank you in advance for sharing your information.

Hello Ryan,

To sum up: if I need information quickly it's better to use API/Conversation, if I need a lot of data and I'm not in a hurry I should use API/Job. The limit is that API/Conversation may not be complete, whereas API/Job will be if my data interval is earlier than D-1.

Your example is expected and documented here:  https://developer.genesys.cloud/analyticsdatamanagement/analytics/jobs/conversation-details-job#differences-to-conversation-detail-queries

The more real time details endpoint does not contain custom participant attribute data.

Hey Lionlel,

Do you have any examples of your own? That may help other in the community help with sharing their workarounds.

Hello everyone,

We have recently identified an information gap between the "conversation" and "job" APIs of Genesys and we would like to know if other customers have encountered the same problem. Have you noticed any discrepancies in the data provided by different Genesys APIs? If so, have you found a workaround to ensure data consistency?

Thank you in advance for sharing your information.

The way I would subdivide the different options:

• EventBridge
  • Individual events for data updates that stream in as they happen.  Ideal for high volume and requires timely data delivery.
  • https://developer.genesys.cloud/analyticsdatamanagement/analytics/detail/analytics-detail-events
• Conversation detail query
  • Updates in near real-time and ideal for searching for conversations.  Can be used to gather data in realtime for mid to low volume customers.
  • https://developer.genesys.cloud/analyticsdatamanagement/analytics/detail/conversation-query
• Conversation detail job
  • Batch job that updates nightly.  Large bulk download support.  Ideal for loading historical data sources that can be tolerant to 24-48 hour delays.
  • https://developer.genesys.cloud/analyticsdatamanagement/analytics/jobs/conversation-details-job

Hello Ryan,

To sum up: if I need information quickly it's better to use API/Conversation, if I need a lot of data and I'm not in a hurry I should use API/Job. The limit is that API/Conversation may not be complete, whereas API/Job will be if my data interval is earlier than D-1.

Your example is expected and documented here:  https://developer.genesys.cloud/analyticsdatamanagement/analytics/jobs/conversation-details-job#differences-to-conversation-detail-queries

The more real time details endpoint does not contain custom participant attribute data.

Hey Lionlel,

Do you have any examples of your own? That may help other in the community help with sharing their workarounds.

Hello everyone,

We have recently identified an information gap between the "conversation" and "job" APIs of Genesys and we would like to know if other customers have encountered the same problem. Have you noticed any discrepancies in the data provided by different Genesys APIs? If so, have you found a workaround to ensure data consistency?

Thank you in advance for sharing your information.

The way I would subdivide the different options:

• EventBridge
  • Individual events for data updates that stream in as they happen.  Ideal for high volume and requires timely data delivery.
  • https://developer.genesys.cloud/analyticsdatamanagement/analytics/detail/analytics-detail-events
• Conversation detail query
  • Updates in near real-time and ideal for searching for conversations.  Can be used to gather data in realtime for mid to low volume customers.
  • https://developer.genesys.cloud/analyticsdatamanagement/analytics/detail/conversation-query
• Conversation detail job
  • Batch job that updates nightly.  Large bulk download support.  Ideal for loading historical data sources that can be tolerant to 24-48 hour delays.
  • https://developer.genesys.cloud/analyticsdatamanagement/analytics/jobs/conversation-details-job

Hello Ryan,

To sum up: if I need information quickly it's better to use API/Conversation, if I need a lot of data and I'm not in a hurry I should use API/Job. The limit is that API/Conversation may not be complete, whereas API/Job will be if my data interval is earlier than D-1.

Your example is expected and documented here:  https://developer.genesys.cloud/analyticsdatamanagement/analytics/jobs/conversation-details-job#differences-to-conversation-detail-queries

The more real time details endpoint does not contain custom participant attribute data.

Hey Lionlel,

Do you have any examples of your own? That may help other in the community help with sharing their workarounds.

Hello everyone,

We have recently identified an information gap between the "conversation" and "job" APIs of Genesys and we would like to know if other customers have encountered the same problem. Have you noticed any discrepancies in the data provided by different Genesys APIs? If so, have you found a workaround to ensure data consistency?

Thank you in advance for sharing your information.

Hello Ryan,

Any news regarding this issue ?

Regards,

Lionel

The way I would subdivide the different options:

• EventBridge
  • Individual events for data updates that stream in as they happen.  Ideal for high volume and requires timely data delivery.
  • https://developer.genesys.cloud/analyticsdatamanagement/analytics/detail/analytics-detail-events
• Conversation detail query
  • Updates in near real-time and ideal for searching for conversations.  Can be used to gather data in realtime for mid to low volume customers.
  • https://developer.genesys.cloud/analyticsdatamanagement/analytics/detail/conversation-query
• Conversation detail job
  • Batch job that updates nightly.  Large bulk download support.  Ideal for loading historical data sources that can be tolerant to 24-48 hour delays.
  • https://developer.genesys.cloud/analyticsdatamanagement/analytics/jobs/conversation-details-job

Hello Ryan,

To sum up: if I need information quickly it's better to use API/Conversation, if I need a lot of data and I'm not in a hurry I should use API/Job. The limit is that API/Conversation may not be complete, whereas API/Job will be if my data interval is earlier than D-1.

Your example is expected and documented here:  https://developer.genesys.cloud/analyticsdatamanagement/analytics/jobs/conversation-details-job#differences-to-conversation-detail-queries

The more real time details endpoint does not contain custom participant attribute data.

Hey Lionlel,

Do you have any examples of your own? That may help other in the community help with sharing their workarounds.

Hello everyone,

We have recently identified an information gap between the "conversation" and "job" APIs of Genesys and we would like to know if other customers have encountered the same problem. Have you noticed any discrepancies in the data provided by different Genesys APIs? If so, have you found a workaround to ensure data consistency?

Thank you in advance for sharing your information.

The only known issue I can think of that you could be facing is if you are setting the participant attribute value after the participant you're attaching to has left the conversation.  We have an idea enhancement tracking that request here: https://genesyscloud.ideas.aha.io/ideas/ANLS-I-1293

The analytics stack we have is not built with the expectation that data can update after the participant has left the conversation.  If this happens, we'll ignore those events since they're being added to immutable participants. 

Alternatively, we have an EventBridge topic available to consume attribute updates in realtime.  https://developer.genesys.cloud/notificationsalerts/notifications/available-topics v2.detail.events.conversation.{id}.attributes

If you are updating the participant attribute while the session is active, then this would be worthwhile to dig further into with our support team.

Hello Ryan,

Any news regarding this issue ?

Regards,

Lionel

The way I would subdivide the different options:

• EventBridge
  • Individual events for data updates that stream in as they happen.  Ideal for high volume and requires timely data delivery.
  • https://developer.genesys.cloud/analyticsdatamanagement/analytics/detail/analytics-detail-events
• Conversation detail query
  • Updates in near real-time and ideal for searching for conversations.  Can be used to gather data in realtime for mid to low volume customers.
  • https://developer.genesys.cloud/analyticsdatamanagement/analytics/detail/conversation-query
• Conversation detail job
  • Batch job that updates nightly.  Large bulk download support.  Ideal for loading historical data sources that can be tolerant to 24-48 hour delays.
  • https://developer.genesys.cloud/analyticsdatamanagement/analytics/jobs/conversation-details-job

Hello Ryan,

To sum up: if I need information quickly it's better to use API/Conversation, if I need a lot of data and I'm not in a hurry I should use API/Job. The limit is that API/Conversation may not be complete, whereas API/Job will be if my data interval is earlier than D-1.

Your example is expected and documented here:  https://developer.genesys.cloud/analyticsdatamanagement/analytics/jobs/conversation-details-job#differences-to-conversation-detail-queries

The more real time details endpoint does not contain custom participant attribute data.

Hey Lionlel,

Do you have any examples of your own? That may help other in the community help with sharing their workarounds.

Hello everyone,

We have recently identified an information gap between the "conversation" and "job" APIs of Genesys and we would like to know if other customers have encountered the same problem. Have you noticed any discrepancies in the data provided by different Genesys APIs? If so, have you found a workaround to ensure data consistency?

Thank you in advance for sharing your information.

Hello Ryan,

To sum up: if I need information quickly it's better to use API/Conversation, if I need a lot of data and I'm not in a hurry I should use API/Job. The limit is that API/Conversation may not be complete, whereas API/Job will be if my data interval is earlier than D-1.

Your example is expected and documented here:  https://developer.genesys.cloud/analyticsdatamanagement/analytics/jobs/conversation-details-job#differences-to-conversation-detail-queries

The more real time details endpoint does not contain custom participant attribute data.

Hey Lionlel,

Do you have any examples of your own? That may help other in the community help with sharing their workarounds.

Hello everyone,

We have recently identified an information gap between the "conversation" and "job" APIs of Genesys and we would like to know if other customers have encountered the same problem. Have you noticed any discrepancies in the data provided by different Genesys APIs? If so, have you found a workaround to ensure data consistency?

Thank you in advance for sharing your information.