Jeroen | 2017-05-18 12:38:31 UTC | #1
Hello,
is it somehow possible to add the participant attributes to the analytics/conversations Query? It only seems possible to get that data from the conversations/call endpoint, but that would mean we need to make an additional call.
Thanks, Jeroen
tim.smith | 2017-05-18 13:23:22 UTC | #2
You are correct that analytics data does not contain participant attribute data. You will need to make a request to the conversation resource for each conversation to get participant data.
anon28066628 | 2017-05-22 14:37:35 UTC | #3
Hi Jeroen, one approach you can use is adding analytics data to conversation segments with this endpoint:
POST /api/v2/analytics/conversations/{conversationId}/details/properties
These segment properties are contained in analytics and can be used for filtering. There aren't any features in PureCloud (as far as I know) that will add these from Architect or Scripter though. An example approach to using these is downloading records from the Conversations API at the end of each day and re-tagging the data as these segment properties. You'd still need to download each conversation at least once to re-tag the data.
Jeroen | 2017-05-23 15:36:49 UTC | #4
Thanks for the suggestion, but we'll pull everything into a data warehouse, so we'll probably add the attributes to those records.
andygunther | 2017-06-13 21:21:39 UTC | #5
Can you elaborate on this? I have the json for the following objects where I know attribute data should exist from Architect:
AnalyticsConversation AnalyticsParticipant AnalyticsSession AnalyticsConversationSegment
Where is it I should be able to grab Participant Data set in Architect?
tim.smith | 2017-06-13 21:37:29 UTC | #6
andygunther, post:5, topic:1306
Where is it I should be able to grab Participant Data set in Architect?
Analytics results won't show participant data. You'll need to retrieve it using GET /api/v2/conversations/{conversationId}, or any of the other conversation resources that will return the conversation object (e.g. the call or email endpoints).
system | 2017-08-28 19:34:33 UTC | #7
This post was migrated from the old Developer Forum.
ref: 1306