Content Analytics

Overview

---

Tonos receives analytics about its content through API calls that break down content by:

• Author
• Page
• Page targeting

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 content by author

Method: GET

Endpoints:

/content/breakdown/by/author

/content/breakdown/by/author/csv

/content/breakdown/by/author/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": [
    {
      "author": "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 content by page

Method: GET

Endpoints:

/content/breakdown/by/page

/content/breakdown/by/page/csv

/content/breakdown/by/page/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": [
    {
      "url": "string",
      "offers": {
        "offer_name": "string",
        "subscription_plans": [
          {
            "subscription_plan_name": "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 content by page targeting

Method: GET

Endpoints:

/content/breakdown/by/page-targeting

/content/breakdown/by/page-targeting/csv

/content/breakdown/by/page-targeting/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": [
    {
      "page_targeting": "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
}