Report is represented as simple flat JSON objects with the following keys:
Name | Type | Description |
---|---|---|
total |
object | A key-value dictionary based on query, the keys is comes from cube query entity's fields |
series |
object[] | A array of dictionary based on query, the data of this array is obtained by dividing all the data according to the row group. For example, the value in the row group is department, then each item of data in this array is obtained according to a different department |
POST reportingquery/reports/query
Name | Type | Required | Description |
---|---|---|---|
cubeEntities |
cubeQueryModel[] | yes | Reference to Cube Query Entity |
mergeType |
string | yes | Allowed values are "column", "row", "rowToColumn" |
timezone |
double | yes | Offset of the time, Based on UTC |
Cube Query Entity JSON Format:
Name | Type | Description |
---|---|---|
name |
string | Name of the cube query |
fields |
fieldModel[] | Reference to Field |
rowGroups |
rowGroupModel[] | Reference to Row Group |
filters |
filterModel[] | Reference to Filter |
timezone |
string | Offset of the time, Based on UTC |
Field JSON Format:
Name | Type | Description |
---|---|---|
name |
string | Name of the field |
calculationType |
string | Allowed values are "count", "max", "average", "sum", "expression", "originalValue", "uniqueCount" |
valueType |
string | Allowed values are "int", "decimal", "percent", "timespan", "string" |
expression |
string | For some fields that need to be calculated using other fields, we can configure the evaluation expression. We can use "+-*/" and "()" |
fieldName |
string | Corresponding to the field name in cube entity |
conditionExpression |
string | For more complex query conditions, we can configure condition expression that refer to the name of the above condition. Here we can use logical operators such as "()", "&", "|" |
conditions |
fieldConditionModel[] | Reference to Field Condition |
Field Condition JSON Format:
Name | Type | Description |
---|---|---|
name |
string | Name of the field condition |
fieldName |
string | Name of the field, point to the field used for get data based on condition, only data that meets the conditions will be counted in the results |
operate |
string | Allowed values are "equals", "notEquals" |
values |
string[] | Array of values used as conditions |
Row Group JSON Format:
Name | Type | Description |
---|---|---|
name |
string | Name of the row group |
fieldName |
string | Name of the field, point to the field used for group data |
isFull |
bool | The field corresponding to fieldName, if its type is reference, decide whether to return all possible values of that field according to the value of isFull, regardless of whether the group corresponding to that value has data |
timeDisplayType |
string | Allowed values are "hour", "day", "week", "month", "_24x7", "halfHour" |
Filter JSON Format:
Name | Type | Description |
---|---|---|
fieldName |
string | Name of the field, point to the field used for filter data, used to obtain part of the data according to specific conditions, such as a certain agent, a certain department, a certain period of time data |
matchType |
string | Allowed values are "equals", "notEquals", "between", "lessThan", "greaterThan" |
value |
string[] | Array of values to filter data |
An array of Report
Provides the number of visits and chats (including refused and missed chats) within a specific time period.
Sample Request :
Response:
HTTP/1.1 200 OK
Real time details.
Sample Request :
Response:
HTTP/1.1 200 OK
Volume details by day.
Sample Request :
Response:
HTTP/1.1 200 OK
Channel details by day.
Sample Request :
Response:
HTTP/1.1 200 OK
Efficiency details by day.
Sample Request :
Response:
HTTP/1.1 200 OK
SLA Policies details.
Sample Request :
Response:
HTTP/1.1 200 OK
Availability details by Month.
Sample Request :
Response:
HTTP/1.1 200 OK
Canned Messages details by site.
Sample Request :
Response:
HTTP/1.1 200 OK
Provides the number of chats initiated by visitors, by agents, or by predefined rules as well as the request page of those chats.
Sample Request :
Response:
HTTP/1.1 200 OK
Shows the number of visitors who waited in the queue, abandoned the queue, switched to offline message or were refused by agents.
Sample Request :
Response:
HTTP/1.1 200 OK
Provides the details on visitors' average and the longest wait times within a specific time range.
Sample Request :
Response:
HTTP/1.1 200 OK
Provides a clear picture on the number of chats being transferred between agents and departments.
Sample Request :
Response:
HTTP/1.1 200 OK
Provides data regarding agents' overall performance in terms of chat time and wait time within a specific time period.
Sample Request :
Response:
HTTP/1.1 200 OK
Gives a comprehensive view on the agent workload by providings data regarding agents' chat time and number of chats handled.
Sample Request :
Response:
HTTP/1.1 200 OK
Provides data regarding the agents' responsiveness, total chat time and visitor wait time.
Sample Request :
Response:
HTTP/1.1 200 OK
Provides insights on customer satisfaction by showsing rating scores of individual agents and departments.
Sample Request :
Response:
HTTP/1.1 200 OK
Provides insight on how visitors felt about agents' professionalism, responsiveness, and helpfulness.
Sample Request :
Response:
HTTP/1.1 200 OK
Provides insight on visitor data collected from pre-chat surveys.
Sample Request :
Response:
HTTP/1.1 200 OK
Shows the categorization details of the chats as well as the wrap-up completion rate according to the wrap-up survey.
Sample Request :
Response:
HTTP/1.1 200 OK
Shows all achieved conversions, total conversion value and the conversion rate.
Sample Request :
Response:
HTTP/1.1 200 OK
Shows the number of invitations sent manually by agents as well as the acceptance rate.
Sample Request :
Response:
HTTP/1.1 200 OK
Shows the number of invitations triggered by predefined rules as well as the acceptance rate.
Sample Request :
Response:
HTTP/1.1 200 OK
Provides details on the number of offline messages left by the visitos as well as their source.
Sample Request :
Response:
HTTP/1.1 200 OK