GET Traffic Report (deprecated)
GET Traffic Report Exports (deprecated, use live report builder API instead)
Returns data from the interface’s reports
Resource URL: GET /{version}/measure/reporttrafic/{id_type_rapport}?site=XXXX&token=YYYY&date_start=YYYY-MM-DD&date_end=YYYY-MM-DD&attrib=A,B,C&kpis=Q,S,D&segment=UUUU&breakdown=TTTT&format=ZZZZ
Parameters:
URI PARAMETER | TYPE | MANDATORY | DESCRIPTION |
version | Alphanum | Yes | Call API version |
id_type_rapport | Integer | Yes | Report type identifier |
URL PARAMETER | TYPE | MANDATORY | DESCRIPTION |
site | Integer | Yes | Client site identifier |
token | Alphanum | Yes | Caller security identifier |
date_start | Date | Yes | Data recovery start date (YYYY-MM-DD format) |
date_end | Date | Yes | Data recovery end date (YYYY-MM-DD format) |
attrib | Alphanum | Yes | Attribution models identifier |
kpis | Alphanum | Yes | KPIs identifier’s list |
segment | Alphanum | Yes | Identifier of the segment that will be used to recover data |
breakdown | String | No | Desired breakdown of aggregated data (none, day, week, month) – “none” is selected by default, nothing will be split |
format | String | No | Response format (XML or JSON) – JSON is selected by default |
Return codes:
HTTP CODE | MESSAGE | DESCRIPTION |
200 | OK | The request went through, the result is in the answer’s body |
400 | Bad Request | The parameters are not ok or mandatory parameters are missing |
401 | Unauthorized | The security token does not match the site_id |
500 | Internal Server Error | Internal server erros |
Response Format The response is in a JSON or XML format.
FIELD | TYPE | IS ALWAYS PRESENT? | DESCRIPTION |
site | Integer | Yes | Site identifier |
idReport | Integer | Yes | Custom report identifier |
dateStart | Date | Yes | Data recovery start date (YYYY-MM-DD format) |
dateEnd | Date | Yes | Data recovery end date (YYYY-MM-DD format) |
attrib | Alphanum | Yes | Attribution models list identifier |
kpis | Alphanum | Yes | KPIs list identifier |
segment | Integer | Yes | Identifier of the segment that will be used to recover data |
breakdown | String | No | Desired breakdown for aggregated data |
datas | Array | Yes | Table containing data |
datas/date | String | No | Time and date of data according to selected breakdown |
datas/level1 | String | Yes | Level 1 – Channel (in general) |
datas/level2 | String | No | Level 2 – Source (in general) |
datas/level3 | String | No | Level 3 |
datas/kpis | Array | Yes | Table containing the KPIs |
datas/kpis/id | Integer | Yes | KPIs technical identifier |
datas/kpis/label | String | Yes | KPI Label |
datas/kpis/value | Numeric | Yes | KPI Value |
Response example in JSON and XML formats:
Last updated