<!-- https://docs.youtarget.com/rtb/en/ssp/checklist.html -->

# How to connect

> Steps to connect to Youtarget over OpenRTB or the JSON feed: from agreeing on terms with your account manager to full traffic volume, plus common errors at the start.

Steps for SSPs, exchanges and traffic sources that sell traffic to Youtarget over [OpenRTB](https://docs.youtarget.com/rtb/en/glossary/openrtb.md) or the JSON feed.

## Steps

1. **Agree with your account manager** on the protocol (OpenRTB 2.5, 2.6 or the JSON feed), formats, pricing model and currency, the impression counting event and the starting request limit. Send an example of your request. The manager will send you the integration URL.
2. **Send the first requests** at a low volume: there is no test mode, bids and impressions are live. Check the response codes: [OpenRTB](./openrtb.md#response-codes), [JSON feed](./json-feed.md#response-codes).
3. **Show the creative** of each enabled format and compare with the examples: [OpenRTB](./examples/banner.md), [JSON feed](./feed-examples/push.md).
4. **Set up notifications.** In OpenRTB, substitute `${AUCTION_PRICE}` with the price as a plain number. `nurl` and `burl` must return `200`: [Notifications](./openrtb.md#notifications), [impression counting in the feed](./json-feed.md#impression-counting-and-payouts).
5. **Set up cookie sync** if you need it: [Cookie sync](../common/cookie-sync.md).
6. **Reconcile statistics** for the first day or two on the agreed events: [Statistics reconciliation](../common/reconciliation.md).
7. **Increase the volume** gradually, as agreed with the manager. Add new formats one at a time, repeating steps 3 and 4.

## Common errors at the start

| Symptom | Cause | What to do |
| --- | --- | --- |
| `204` on all requests | The format is not enabled for the integration, or in OpenRTB it is not in the first `imp` | Check the formats with the manager, send one placement per request |
| `204` on all requests | No user IP and User-Agent | Pass `device.ip` and `device.ua` (`ip` and `ua` in the feed) from the user's device |
| `204` on all requests | The request limit is exceeded or the floor is above the bids | Lower the volume or the floor, check the floor currency and units |
| `400` on notifications | The price is missing or not a number, the URL was changed, or the notification came late | Call the URL as received, right after the event, with the price as a plain number |
| `403` or `404` on requests | The integration is inactive or the `id` in the URL is wrong | Check the URL with the manager |
| Impressions are not counted in the JSON feed | The wrong impression counting URL is called | Ask the manager which impression counting method is set |
