{"id":129,"date":"2024-04-03T23:02:57","date_gmt":"2024-04-03T23:02:57","guid":{"rendered":"https:\/\/adtransfer.org\/documentation\/?p=129"},"modified":"2025-01-23T13:41:39","modified_gmt":"2025-01-23T13:41:39","slug":"interface-explained","status":"publish","type":"post","link":"https:\/\/adtransfer.org\/documentation\/index.php\/2024\/04\/03\/interface-explained\/","title":{"rendered":"Interface explained"},"content":{"rendered":"\n

In this section we’ll cover most of the features available within the administrative interface.<\/p>\n\n\n\n

GENERAL<\/h4>\n\n\n\n

Dashboard<\/h3>\n\n\n\n

We’ll split the dashboard in more sections to help ease out explaining each of them.<\/p>\n\n\n\n

    \n
  1. Information about the platform subscription, infrastructure and properties
    \"\"<\/strong><\/li>\n
  2. Information about the gains, spendings and profit for the ongoing day, previous day, last 7 days, ongoing month and previous month
    \"\"<\/strong><\/li>\n
  3. General information about the platform’s members, including their balances
    \"\"
    <\/strong><\/li>\n
  4. Cumulative information regarding the payments received, payments sent and users total funds
    \"\"<\/strong><\/li>\n
  5. Activity log of the most recent actions within the platform. Includes a link to a page which contains the complete activity log
    \"\"<\/strong><\/li>\n
  6. Gains, spendings and profit for the last 30 days, ongoing month and previous month
    \"\"<\/strong><\/li>\n
  7. QPS distribution by format as well as the combined QPS for all formats
    \"\"<\/strong><\/li>\n
  8. QPS distribution by supply endpoint
    \"\"<\/strong><\/li>\n
  9. Infrastructure information which include resources used and server load
    \"\"<\/strong><\/li>\n<\/ol>\n

     <\/p>\n

    .<\/span><\/p>\n

     <\/p>\n\n\n\n

    STATISTICS<\/h5>\n\n\n\n

    Traffic reports<\/h3>\n\n\n\n

    The traffic reports are responsible for displaying information regarding all the platform’s traffic and are divided into 3 sections as it follows:<\/p>\n

      \n
    1. The filters
      \"\"

      <\/strong><\/span><\/li>\n
    2. Report grouping
      \"\"

      <\/strong><\/span><\/li>\n
    3. The report data<\/strong><\/span>
      \"\"<\/li>\n<\/ol>\n

      TABLE DATA TERMINOLOGY<\/strong><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
      Term<\/th>\nDescription<\/th>\n<\/tr>\n
      \n

      REQUESTS IN<\/span><\/p>\n<\/td>\n

      		\n

      The number of requests received from supply endpoints.<\/p>\n<\/td>\n<\/tr>\n

      \n

      REQUESTS OUT<\/span><\/p>\n<\/td>\n

      		The number of requests made to demand endpoints. Should be higher than the requests in because for each request made by a supply endpoint, 1 or more demand endpoints are interrogated.<\/td>\n<\/tr>\n
      \n

      IMPRESSIONS<\/span><\/p>\n<\/td>\n

      		The number of impressions.<\/td>\n<\/tr>\n
      \n

      CLICKS<\/span><\/p>\n<\/td>\n

      		The number of clicks.<\/td>\n<\/tr>\n
      \n

      eCPM<\/span><\/p>\n<\/td>\n

      		The eCPM calculated based on the gains. Formula : (gains \u00d7 1000 \/ impressions)<\/td>\n<\/tr>\n
      \n

      eCPM<\/span><\/p>\n<\/td>\n

      		The eCPM calculated based on the spendings. Should be lower than the eCPM of gains. Formula : (spendings \u00d7 1000 \/ impressions)<\/td>\n<\/tr>\n
      \n

      CTR<\/span><\/p>\n<\/td>\n

      		The click through rate. Formula : (clicks \u00d7 100 \/ impressions)<\/td>\n<\/tr>\n
      \n

      WIN RATE<\/span><\/p>\n<\/td>\n

      		The percentage of wins compared to the total requests. Formula : (impressions \u00d7 100 \/ requests)<\/td>\n<\/tr>\n
      \n

      GAINS<\/span><\/p>\n<\/td>\n

      		Estimation of your earned income from your demand endpoints.<\/td>\n<\/tr>\n
      \n

      SPENDINGS<\/span><\/p>\n<\/td>\n

      		Estimation of your spendings. This amount is what the users actually receive.<\/td>\n<\/tr>\n
      \n

      PROFIT<\/span><\/p>\n<\/td>\n

      		Estimation of your profit. Formula : (GAINS – SPENDINGS)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n

      <\/p>\n\n\n\n

       <\/p>\n\n\n\n

      .<\/p>\n\n\n\n

      <\/p>\n\n\n\n

      <\/p>\n\n\n\n

      Filtered traffic<\/h3>\n\n\n\n

      Also known as the “Error log”, this page displays reports of the redirect-level traffic that was filtered.<\/p>\n\n\n\n

      In terms of page structure, it shares the same structure as the Traffic reports<\/strong> and has sections for results limiting, filters, grouping, chart data and table data<\/strong>, with the difference that its main focus is reporting the errors logged per inbound traffic. The available error codes can be seen in the table below.<\/p>\n\n\n\n

      The filtered traffic<\/strong> page also points to a detailed error log<\/strong> which contains the ongoing day data.<\/p>\n\n\n\n

      ERROR TYPES<\/h6>\n\n\n\n
      Error<\/th>Description<\/th><\/tr><\/thead>
      Invalid click ID<\/code><\/td>This error refers to clicks and \/ or visits that were rejected because they were sent to an invalid click ID. The click ID is an unique identifier given to each request and it can only be used once.<\/td><\/tr>
      Click ID reused<\/code><\/td>This error refers to clicks and \/ or visits that were triggered more than once for a previously used click ID.<\/td><\/tr>
      IP mismatch<\/code><\/td>This error refers to clicks and \/ or visits in which the IP address used in the request is different than the one used when the redirect takes place.<\/td><\/tr>
      Invalid screen size<\/code><\/td>This error refers to clicks and \/ or visits in which visitor’s screen width is lower than 300px or the screen height is lower than 400px.<\/td><\/tr>
      Connection speed < 3G<\/code><\/td>This error refers to clicks and \/ or visits in which visitor’s connection speed is slower than 3G.<\/td><\/tr>
      Device RAM < 1GB<\/code><\/td>This error refers to clicks and \/ or visits in which the RAM memory of the device of the visitor is below 1GB.<\/td><\/tr>
      Invalid navigator platform<\/code><\/td>This error refers to clicks and \/ or visits in which the navigator platform of the visitors’ browser could not be retrieved.<\/td><\/tr>
      Webdriver enabled<\/code><\/td>This error refers to clicks and \/ or visits in which the vistor’s browser runs a webdriver.<\/td><\/tr>
      Invalid navigator geolocation<\/code><\/td>This error refers to clicks and \/ or visits in which the geolocation of the vistor’s browser can not be retrieved or is invalid.<\/td><\/tr>
      Localstorage unavailable<\/code><\/td>This error refers to clicks and \/ or visits in which the localstorage of the vistor’s browser can not be retrieved or is invalid.<\/td><\/tr>
      Browser cookies unavailable<\/code><\/td>This error refers to clicks and \/ or visits in which the cookies of the vistor’s browser are not enabled or are unavailable.<\/td><\/tr>
      Browser JavaScript unavailable<\/code><\/td>This error refers to clicks and \/ or visits in which the JavaScript of the vistor’s browser is not enabled or unavailable.<\/td><\/tr>
      Window history unavailable<\/code><\/td>This error refers to clicks and \/ or visits in which there is no window history for the visitor’s browser and \/ or the visit comes with no previous referrer.<\/td><\/tr>
      In-app visit<\/code><\/td>This error refers to clicks and \/ or visits in which were triggered inside a mobile app.<\/td><\/tr>
      No pixel \/ Fast click<\/code><\/td>This error refers to clicks specific to banner, native and push ads that were triggered without displaying the image of the banner, native ad or push ad respectively, or the click was fired less than 1 second after the image was displayed.<\/td><\/tr>
      Filtered by 3rd party<\/code><\/td>This error refers to clicks and \/ or visits that were filtered by a 3rd party filter.<\/td><\/tr>
      Iframe visit<\/code><\/td>This error refers to clicks and \/ or visits that were displayed inside an iframe.<\/td><\/tr>
      Other<\/code><\/td>This error refers to clicks and \/ or visits for other reasons than the ones listed above.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      .<\/p>\n\n\n\n

      Request log<\/h3>\n\n\n\n

      The request log is an utility page which helps you detect flawed calls from your supply endpoints and allows you to remediate them by communicating instructions to your traffic suppliers or publishers.<\/p>\n\n\n\n

      Due to performance issues, the request log is disabled by default can be enabled when needed for a limited period. The feature was developed this way to prevent high stress on your database.<\/p>\n\n\n\n

      Enabling the request log can be done for a predetermined period of 1 minute, by accessing the status button on the top right side of the page.<\/p>\n\n\n\n

      \"\"<\/figure>\n\n\n\n

      The actual request list contains the following information:<\/p>\n\n\n\n