Using Additional Sub IDs

As explained in the Using Sub Ids documentation, Sub Ids are used by Publishers to segment traffic. For example, they might do this by traffic source. This information will then be displayed in the Statistics tab, in the Sub IDs sub-tab.

As well as this, there are two more parameters that are essentially the exact same as 'sub' overall: 'sub2' and 'sub3'.

Examples

Banners, In-stream, Slider…

&sub=XXXXXX
&sub2=XXXXXX
&sub3=XXXXXX
<iframe src="http://a.examplesite.com/iframe.php?idzone=12345678&size=300x250&sub=123456&sub2=789101&sub3=1213141" width="300" height="250" scrolling="no" marginwidth="0" marginheight="0" frameborder="0"></iframe>

 

Popup and Banner

ad_sub = "XXXXXX"; 
ad_sub2 = "XXXXXX";
ad_sub3 = "XXXXXX"; 

<script type="text/javascript>
ad_idzone = "123";
ad_width = "300";
ad_height = "250";
ad_sub = "123456";
ad_sub2 = "789101";
ad_sub3 = "1213141";
</script>
<script type="text/javascript" src="https://a.examplesite.com/ads.js"></script>

<noscript><a href="http://main.examplesite.com/img-click.php?idzone=123&sub=123456" target="_blank"><img src="https://syndication.examplesite.com/ads-iframe-display.php?idzone=123&output=img&type=300x250&sub=12345" width="300" height="250"></a></noscript>

 

Native

data-ad_sub= "XXXXXX"; 
data-ad_sub2 = "XXXXXX";
data-ad_sub3 = "XXXXXX"; 

<script type="text/javascript" data-idzone="123" data-ad_sub="123456" data-ad_sub="789101" data-ad_sub="1213141" src="https://a.examplesite.com/nativeads.js"></script>

 

RTB

&sub=XXXXXX
&sub2=XXXXXX
&sub3=XXXXXX
{
   "id": "d4b5c697-41f3-4c1c-a3d5-5fd01b5ef2aa",
   "imp": [
       {
           "id": "974090632",
           "banner": {
               "w": 300,
               "h": 250
           }
       }
   ],
   "site": {
       "id": "12345",
       "domain": "sitedomain.com",
       "cat": ["IAB25-3"],
       "page": "https://sitedomain.com/page"
   },
   "device": {
       "ua": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.63 Safari/537.36",
       "ip": "131.34.123.159",
       "geo": {
           "country": "IRL"
       },
       "language": "en",
       "os": "Linux & UNIX",
       "js": 0,
       "ext": {
           "remote_addr": "131.34.123.159",
           "x_forwarded_for": "",
           "accept_language": "en-GB;q=0.8,pt-PT;q=0.6,en;q=0.4,en-US;q=0.2,de;q=0.2,es;q=0.2,fr;q=0.2"
       }
   },
   "user": {
       "id": "57592f333f8983.043587162282415065"
   },
   "ext": {
       "sub": 1221
       "sub2": 2222
       "sub3": 3333
   }
}

 

These parameters could be used to segment the traffic even more. However, unlike sub, this won’t be displayed in the Sub IDs sub-tab of the Statistics tab. However, we do register them internally. The only way to get the data for these metrics is through the API Global Routes for Publishers.

Here are two examples of how the request should look in order to pull data from sub2 and sub3 respectively:

 

Grouping by sub2 and sub3

{
  "count": 0,
  "detailed": 0,
  "timezone": "Europe/Dublin",
  "totals": 1,
  "filter": {
    "date_from": "2019-11-07",
    "date_to": "2019-11-07",
     "zone_id": [
      1234567
    ]
  },
  "group_by": [
    "sub2",
    "sub3"
  ],
  "order_by": [
    {
      "field": "impressions",
      "order": "desc"
    }
  ],
  "projection": [
    "base"
  ],
  "limit": 25,
  "offset": 0
}

 

Filtering and grouping by sub2 and sub 3

{
  "count": 0,
  "detailed": 0,
  "timezone": "Europe/Dublin",
  "totals": 1,
  "filter": {
    "date_from": "2019-11-07",
    "date_to": "2019-11-07",
    "sub": [
      10001
    ],
    "sub2":[
      10002
    ],
    "sub3":[
      10003
    ],
    "zone_id": [
      1234567
    ]
  },
  "group_by": [
    "sub2",
    "sub3"
  ],
  "order_by": [
    {
      "field": "impressions",
      "order": "desc"
    }
  ],
  "projection": [
    "base"
  ],
  "limit": 25,
  "offset": 0
}

 

---

Note: Only it’s possible to group by two dimensions so in case you want to add sub it is mandatory to remove one of the others, otherwise the response will generate an error.

---

 

{
  "message": "Request `group_by` data is invalid."
}