Skip to main content

Verwendung zusätzlicher 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.

Darüber hinaus gibt es zwei weitere Parameter, die im Wesentlichen genau dasselbe sind wie "sub" insgesamt: "sub2" und "sub3".

Beispiele

Asynchrone Werbezonen: Banner, Sticky Banners, Instant Messages, Outstream Ads und Multi-Formate

Hinzufügen von "data-sub" = XXXXXX, "data-sub2" = XXXXXX und "data-sub3" = XXXXXX

<script async type="application/javascript" src="https://ads.examplesite.com/ad-provider.js"></script>
<ins class="adsbynetwork" data-zoneid="1234567" data-sub="XXXXXX" data-sub2="XXXXXX" data-sub3="XXXXXX"></ins>
<script>(AdProvider = window.AdProvider || []).push({"serve": {}});</script>

iFrames

Hinzufügen von &amp;sub= XXXXXX, &amp;sub2= XXXXXX und &amp;sub3= XXXXXX

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

Einheimische

Hinzugefügt als data-ad_sub= "XXXXXX"; data-ad_sub2 = "XXXXXX"; data-ad_sub3 = "XXXXXX";

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

Im Objekt "ext" als "&sub=XXXXXX, &sub2=XXXXXX, &sub3=XXXXXX" hinzugefügt




{
"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.

Hier sind zwei Beispiele dafür, wie die Anfrage aussehen sollte, um Daten von sub2 bzw. sub3 abzurufen:

Gruppierung nach sub2 und 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
}

Filterung und Gruppierung nach Teil 2 und Teil 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
}

Anmerkung: Es ist nur möglich, in zwei Dimensionen zu gruppieren. Wenn Sie nach "sub" gruppieren möchten, müssen Sie entweder "sub2" oder "sub3" entfernen. Andernfalls wird die Antwort einen Fehler erzeugen.



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