Hey,
So Contacts is an outbound campaign metric, you won't find this for inbound interactions.
From an API perspective it is the nConnected metric or maybe nOutboundConnected


Here is a preview campaign example, pulling all metrics available from https://api.mypurecloud.com.au/api/v2/analytics/conversations/aggregates/query
"metrics": [
{
"metric": "nConnected",
"stats": {
"count": 2
}
},
{
"metric": "nOutboundAttempted",
"stats": {
"count": 3
}
},
{
"metric": "nOutboundConnected",
"stats": {
"count": 2
}
},
{
"metric": "tAcw",
"stats": {
"max": 90159,
"min": 4784,
"count": 3,
"sum": 173632
}
},
{
"metric": "tHandle",
"stats": {
"max": 174640,
"min": 59010,
"count": 3,
"sum": 385653
}
},
{
"metric": "tTalkComplete",
"stats": {
"max": 85517,
"min": 27316,
"count": 2,
"sum": 112833
}
}
]
First note, there is not tAnswered metric at all.
In this example we have 3 dialing attempts made, 2 contacts, one of those dialing attempts was was a busy/disconnected tone.
So 3 attempts, 2 contacts. 3 handles, 2 Talktimes, 3 Acws, which all makes sense.
------------------------------
Anton Vroon
------------------------------