Premium Analytics
Overview
Tonos receives analytics about its premium content through API calls that break down content by:
- Offers
- Subscriptions
Tonos can choose to receive these analytics in three ways: in JSON format in Tonos's Swagger, as a CSV file which is downloaded as a .zip, or as JSON file.
Break down premium content by offer
Method: GET
Endpoints:
/content/breakdown/by/offer
/content/breakdown/by/offer/csv
/content/breakdown/by/offer/json
The headers these endpoints require are as follows:
Header | Description |
---|---|
sd | The start date |
ed | The end date |
sp | The subscription plan |
device | The device |
authorization / x-api-key | A form of identification |
appId | The application ID |
The JSON code that Swagger sends back looks something like this:
JSON
{
"data": [
{
"offer": "string",
"exposures": 0,
"unique_exposures": 0,
"conversions": 0,
"conversion_rate(%)": "string",
"gross_revenue": 0,
"net_revenue": 0,
"refunds": 0,
"country": "string",
"device": "string",
"browser": "string",
"date": "string"
}
],
"errors": ["string"],
"message": "string",
"statusCode": 0,
"success": true
}
Break down premium content by subscription plan
Method: GET
Endpoints:
/content/breakdown/by/subscription-plan
/content/breakdown/by/subscription-plan/csv
/content/breakdown/by/subscription-plan/json
The headers these endpoints require are as follows:
Header | Description |
---|---|
sd | The start date |
ed | The end date |
sp | The subscription plan |
device | The device |
authorization / x-api-key | A form of identification |
appId | The application ID |
The JSON code that Swagger sends back looks something like this:
JSON
{
"data": [
{
"subscription_plan": "string",
"exposures": 0,
"unique_exposures": 0,
"conversions": 0,
"conversion_rate(%)": "string",
"gross_revenue": 0,
"net_revenue": 0,
"refunds": 0,
"country": "string",
"device": "string",
"browser": "string",
"date": "string"
}
],
"errors": ["string"],
"message": "string",
"statusCode": 0,
"success": true
}