Returns a customized report of your Activities analytics event data. The data returned from the API is as a table with columns for the requested dimensions and metrics. Metrics are individual measurements of UserActivity, such as active users or sessions count. Dimensions break down metrics across some common criteria, such as day or channel.
Returns a customized report of your Collection volumes. The data returned from the API is as a table with columns for the requested dimensions and metrics. Metrics are individual measurements of UserActivity, such as active users or sessions count. Dimensions break down metrics across some common criteria, such as date or collection.
Retrieve the data in the specified date range. Mandatory. The data is only queryable for the last 4 months. Only one range is allowed, but the API is prepared to accept multiple ranges in the future.
The list of metrics. Mandatory, but can be an empty array.
Metrics without dimensions will calculate the metric for the whole data in the date ranges. Metrics with dimensions will calculate the metric for each dimension value.
You usually use dimensions without metrics to retrieve the possible values of a dimension.
DateRange
A contiguous set of days.
start_datestring
The inclusive start date for the query in the format YYYY-MM-DDTHH:mm:ss.
end_datestring
The inclusive end date for the query in the format YYYY-MM-DDTHH:mm:ss.
Dimension
Dimensions are attributes of your data. For example, the dimension channel_id indicates the channel on which activities are recorded.
For a list of all available dimensions, see the documentation specific to the data cube you are using.
Metric
The quantitative measurements of a report. For example, the metric sessions is the total number of sessions.
For a list of all available metrics, see the documentation specific to the data cube you are using.
// TYPE should be DISPLAY_AD
{
"dimension_name": "TYPE",
"not": false,
"operator": "EXACT",
"expressions": [
"DISPLAY_AD"
]
}
// TYPE should contain SITE
// SITE_VISIT activities will be used
{
"dimension_name": "TYPE",
"not": false,
"operator": "LIKE",
"expressions": [
"SITE"
]
}
// TYPE should not contain SITE
{
"dimension_name": "TYPE",
"not": true,
"operator": "LIKE",
"expressions": [
"SITE"
]
}
// CHANNEL_ID should be either 8888 or 6666
{
"dimension_name": "CHANNEL_ID",
"not": false,
"operator": "IN_LIST",
"expressions": [
"8888",
"6666"
]
}