> For the complete documentation index, see [llms.txt](https://docs.exads.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exads.com/rtb/advertisers/rtb-demand.md).

# Advertisers RTB Overview

## RTB Integration

Find out about integration with Open RTB and EXADS RTB here:

* [Open RTB Integration](/rtb/publishers/open-rtb/open-rtb-publishers.md)
* [EXADS RTB Integration](/rtb/advertisers/exads-rtb/exads-rtb-advertisers.md)

## Bid Request/Response Specifications <a href="#bid-requestresponse-specifications" id="bid-requestresponse-specifications"></a>

Bid Request/Response Specifications and Examples are here:

* [Open RTB Bid Request](/rtb/advertisers/open-rtb/open-rtb-advertisers-request.md)
* [Open RTB Bid Response](/rtb/advertisers/open-rtb/open-rtb-advertisers-response.md)
* [EXADS RTB Bid Request](/rtb/advertisers/exads-rtb/exads-rtb-advertisers-request.md)
* [EXADS RTB Bid Response](/rtb/advertisers/exads-rtb/exads-rtb-advertisers-response.md)

The IP networks used by EXADS RTB are detailed here:

* [IP Networks](/rtb/ip-networks.md)

## Key Points <a href="#key-points" id="key-points"></a>

Open RTB version 2.4 is supported. However, the ADM is different from the standards. If the client supports Open RTB, they should ensure that they adapt their ADM to EXADS'.

If the client supports XML, they need to provide EXADS with their RTB specifications and they will need to adapt their system to EXADS'.

* There are two servers located in New York and the Netherlands. Normally, the requests of a certain geo will be sent from the nearest server, but not always. The system distributes the requests from one server to another depending on the workload of the server at any given moment. For this reason, if the client asks to only be sent requests from the US server, it is not possible to do this.
* The 'tmax' (the maximum time in milliseconds that SSP allows for bids to be received to avoid timeout) is 300ms. This information is not passed at the request as it's always the same.
* Currency is not passed either at the requests with RTB Floor CPM 0, as the currency is set up at the account level. If the advertiser requests the currency to be passed at the request, a very low RTB Floor CPM should be set.

The total amount of requests will depend on the format, geo, categories selected and 'RTB Manual Throttle' set up. Publishers will have an RTB Automatic throttle switch on the zone level to reduce queries and thus server cost. This is mostly enabled on zones which are not generating revenue in certain geos. In this case, the automatic throttle will temporarily reduce the requests to 1%. When the Revenue raises and zone starts generating profit again on those Geo, the throttle will be automatically increased.

<br>


---

# 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.exads.com/rtb/advertisers/rtb-demand.md?ask=<question>&goal=<user_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.