> For the complete documentation index, see [llms.txt](https://docs.exoclick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exoclick.com/publishers/ja/saitotozn/additional-subids.md).
# 追加のサブIDの使用
で説明したとおり [Sub Idsのドキュメントを使用する](/publishers/ja/saitotozn/subids.md)、Sub Idsは出版社がトラフィックをセグメント化するために使用します。たとえば、トラフィックソース別にこれを行うことがあります。この情報は次に、 **統計** タブの **サブID** サブタブに表示されます。
これに加えて、本質的に `sub` とまったく同じ、さらに2つのパラメータがあります: `sub2` と `sub3`.
## 例
### 非同期広告ゾーン: バナー、スティッキーバナー、インスタントメッセージ、アウトストリーム広告、マルチフォーマット
追加された `data-sub` = XXXXXX, `data-sub2` = XXXXXX および `data-sub3` = XXXXXX
```html
```
### iFrame
追加された `&sub`= XXXXXX, `&sub2`= XXXXXX および `&sub`3= XXXXXX
```html
```
### ネイティブ
として追加 `data-ad_sub= "XXXXXX"; data-ad_sub2 = "XXXXXX"; data-ad_sub3 = "XXXXXX";`
```
data-ad_sub= "XXXXXX";
data-ad_sub2 = "XXXXXX";
data-ad_sub3 = "XXXXXX";
```
### RTB
で追加 `ext` オブジェクトとして `&sub=XXXXXX, &sub2=XXXXXX, &sub3=XXXXXX`
```json
{
"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
}
}
```
これらのパラメータを使用すると、トラフィックをさらに細かくセグメント化できます。ただし、subとは異なり、これは **サブID** のサブタブには表示されません **統計** タブ。ただし、これらは内部では記録しています。これらの指標のデータを取得する唯一の方法は、 [パブリッシャー向けAPI Global Routes](https://api.exoclick.com/v2/docs/#!/47statistics/post_statistics_publisher_global).
sub2とsub3からそれぞれデータを取得するためのリクエストの例を2つ示します:
### sub2とsub3によるグループ化
```json
{
"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
}
```
### sub2とsub3でのフィルタリングとグループ化
```json
{
"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
}
```
**注**: 2次元でのみグループ化できます。もし `sub`でグループ化したい場合は、どちらか一方を削除する必要があります `sub2` または `sub3`。そうしないと、レスポンスでエラーが生成されます。
```json
{
"message": "Request `group_by` data is invalid."
}
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.exoclick.com/publishers/ja/saitotozn/additional-subids.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.