We’re seeing null values for wrapUpCode in the response of our analytics detail queries, even when the agents clearly selected a wrap-up code in the UI. We’re using the /api/v2/analytics/details/interactions endpoint with a simple filter for type:conversation and view:acd.
Here is the request body we are sending:
{
"view": "acd",
"dateFrom": "2023-10-01T00:00:00.000Z",
"dateTo": "2023-10-31T23:59:59.999Z",
"groupBy": ["wrapUpCode"],
"select": ["wrapUpCode", "duration"],
"filter": [
{
"field": "type",
"op": "equals",
"value": "conversation"
}
]
}
The response returns rows with wrapUpCode set to null for interactions that had valid codes. We’ve verified the data in the UI and the raw conversation logs, so the data exists. Is this a known limitation with the acd view not populating wrapUpCode in detail queries, or are we missing a specific filter or view parameter? We’ve tried view:agent as well, but the result is the same.
We need this data for our tracing pipeline to correlate wrap-up reasons with trace spans. Any insights on how to reliably fetch this field?