> 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/pt/sites-e-zonas/additional-subids.md).
# Usar Sub IDs adicionais
Conforme explicado na [documentação sobre a utilização de Sub IDs](/publishers/pt/sites-e-zonas/subids.md), os Sub IDs são usados pelos Publishers para segmentar o tráfego. Por exemplo, podem fazê-lo por origem de tráfego. Esta informação será então apresentada no **Estatísticas** separador, no **Sub IDs** subseparador.
Além disso, existem mais dois parâmetros que são essencialmente exatamente iguais a `sub` no geral: `sub2` e `sub3`.
## Exemplos
### Zonas de anúncios assíncronas: Banners, Banners fixos, Mensagens instantâneas, Anúncios Outstream e Multi-formatos
Adicionado `data-sub` = XXXXXX, `data-sub2` = XXXXXX e `data-sub3` = XXXXXX
```html
```
### iFrames
Adicionado `&sub`= XXXXXX, `&sub2`= XXXXXX e `&sub`3= XXXXXX
```html
```
### Nativo
Adicionado como `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
Adicionado em `ext` objeto como `&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
}
}
```
Estes parâmetros podem ser usados para segmentar ainda mais o tráfego. No entanto, ao contrário de sub, isto não será exibido no **Sub IDs** subseparador da **Estatísticas** separador. No entanto, nós registamo-los internamente. A única forma de obter os dados para estas métricas é através da [API Global Routes para Publishers](https://api.exoclick.com/v2/docs/#!/47statistics/post_statistics_publisher_global).
Aqui estão dois exemplos de como o pedido deve ficar para obter dados de sub2 e sub3, respetivamente:
### Agrupamento por sub2 e 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
}
```
### Filtragem e agrupamento por sub2 e sub 3
```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
}
```
**Nota**: Só é possível agrupar em duas dimensões. Se quiser agrupar por `sub`, terá de remover uma das `sub2` ou `sub3`. Caso contrário, a resposta gerará um erro.
```json
{
"message": "Os dados `group_by` do pedido são inválidos."
}
```
---
# 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/pt/sites-e-zonas/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.