> 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/publishers/publishing-supply.md).
# Integrating Publishing Supply
This step-by-step guide covers how to integrate publishing supply with a partner from another network that is powered by EXADS.
## Step 1: Setting up an Account
Create a Publisher account on your network. Enable RTB for this new account (in the Admin configuration).
## Step 2: Creating an RTB Ad Zone
Go to Sites & Zones and [create a New Zone](/publishers/sites-and-zones/create-zone.md) (you’ll need to [create a new site](/publishers/sites-and-zones/create-site.md) if you still haven’t done so already).
You see a section for RTB, where you can find all available Supply ad zones.
This example uses RTB Banner Supply.
This example uses RTB Banner Supply.
Fill out all the required information.
On the "Select a Partner" dropdown menu, you can select from a variety of exchange partners available to you:
* [OpenRTB v2.4](/rtb/publishers/open-rtb/open-rtb-publishers.md) and [OpenRTB v2.5](/rtb/publishers/open-rtb/open-rtb-publishers-request-2p5.md): For clients that support OpenRTB integration.
* [EXADS RTB](/rtb/publishers/exads-rtb/exads-rtb-publishers.md): For clients that support EXADS RTB integration.
* [Prebid Server](/rtb/publishers/open-rtb/open-rtb-2p5-pub-request.md): For clients that use Prebid Server.
* **ExoClick**, **Traffic Junky**, **TrafficStars** and **TwinRed**: partner-named templates for these frequently requested integrations. Selecting the partner by name applies the correct OpenRTB configuration automatically, so you do not need to know which version they support. See [Ad Exchange Partners](/rtb/publishers/ad-exchange-partners-publishers.md) for the base template each one uses.
* The specific [Ad Exchange Partner name](/rtb/publishers/ad-exchange-partners-publishers.md) if it has been configured on your Ad Server.
## Step 3: RTB URL
Copy this endpoint and share it with the third-party providers you wish to connect with.
Once a site / zone is active, it is available for targeting on all advertiser campaigns relevant to that Ad Format. You can check Real Time Bidding stats that help you control and monitor the activity.
* **Average Bid:** The average bid registered.
* **Average Time:** The average time to respond to requests registered.
* **Errors:** Requests that your platform received and was unable to parse or validate.
* **Errors Ratio:** The percentage of errors registered.
* **No bid:** Requests that your platform doesn’t respond to due to lack of demand.
* **No Bid Ratio:** The percentage of requests not responded to due to lack of demand.
* **Queries:** Requests sent to your platform.
* **Response Ratio:** The percentage of requests responded to.
* **Skipped:** Requests skipped by your platform.
* **Skipped Ratio:** The percentage of skipped requests.
* **Success:** Requests that your platform successfully validated and answered back to.
* **Timeouts:** The number of timeouts registered.
* **Timeouts Ratio:** The percentage of timeouts registered.
* **Win Ratio:** The percentage of wins by your platform.
* **Wins:** Requests that your platform wins.
You should try to keep the Errors / Error ratio and Timeouts / Timeouts ratio as low as possible to avoid significantly impacting the performance of your platform. To view these metrics please do the following:
***
{% hint style="info" %}
**Tip:**If the requests are coming but you still don't see impressions, check Bid Response Ratio, Timeouts Ratio and Error Ratio metrics.
{% endhint %}
***
***
{% hint style="info" %}
**Note:** If the Bid Response Ratio is 0%, this means you are getting requests but not bidding on them. If the Timeout Ratio is higher than 1%, this means there is a late response. If the Error Ratio is higher than 1%, this means that when you were validating the response something went wrong.
{% endhint %}
***
## Reducing measurement discrepancies
RTB discrepancies - the gap between what one side counts and what the other counts or bills are largely driven by how impressions and clicks are tracked on the client side. To keep them low when integrating supply:
* **Prefer server-to-server (S2S) counting** over browser-based redirect chaining. Browsers can collapse intermediate redirect hops, especially Chrome on Android. So an event that rendered may never be logged. This is the biggest single driver of click discrepancies.
* **Use a header (`302`) redirect rather than a meta-refresh redirect** it's more reliable for firing tracking calls.
* **Fire the BURL and impression calls correctly**, so billable and rendered events are both recorded. See [Billable Event Counting (BURL)](/rtb/publishers/billable-event-counting-burl.md) for how billable-event counting works and how to reconcile it against "Served" metrics.
* **Reconcile clicks like-for-like.** Each side applies its own invalid-click and multiclick filtering, so compare totals on the same basis (valid + invalid together) before treating a gap as an error.
* **Be aware that some segments run higher on discrepancy** notably Android + Chrome traffic, video formats, and client-side measurement methods such as Client Hints collection, `sendBeacon`, and browser "heavy ad" interventions.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.exads.com/rtb/publishers/publishing-supply.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.