> For the complete documentation index, see [llms.txt](https://docs.relevant-digital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.relevant-digital.com/hb-manager/setup/mapping-adserver-and-ssp-placement-ids-to-relevant-yield-placements.md).

# Mapping Adserver and SSP placement IDs to Relevant Yield Placements

One of the tasks during HB Manager onboarding is to map adserver and SSP placement IDs to corresponding Relevant Yield placements.

Before you start, **make sure that SSPs and Adserver are saved in Configuration** > **Integrations** view.

### How to map SSP IDs to corresponding Relevant Yield Placements

{% stepper %}
{% step %}

## Navigate to a Placement

Go to Publisher Accounts > Edit Publisher > Websites > Placement

![](/files/44ab9f0c3352acbb4e90fa400c42a23a00ff4985)
{% endstep %}

{% step %}

## Add your Adserver

In placement settings you select your adserver. If not yet integrated, follow [this guide](/hb-manager/setup/setting-up-an-ad-server.md).

![](/files/76baefb3eeb1de81ffd12d7c16151abdf109739d)
{% endstep %}

{% step %}

## Add an SSP and the SSP ID

* In placement settings you select the SSPs you wish to use in the Placement. If no SSP is integrated yet, follow [this guide](/hb-manager/integrations-and-connections/setting-up-a-new-ssp-connection-with-hbm-hba.md).
* Add the SSP ID into the ID\* field

![](/files/d55da062dfd6bd99b88aa02270d80c291d6afb12)
{% endstep %}

{% step %}

## Remember to add all of the SSP you have

Use The onboarding sheet provided by your Technical account manager and fill in all of the SSPs ids.
{% endstep %}

{% step %}

## Save

At the bottom of your account settings you find the "Save" button.

![](/files/fe4554d0c9ddf00d4a1ff2656e0973d9f0bc3b50)
{% endstep %}
{% endstepper %}


---

# 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.relevant-digital.com/hb-manager/setup/mapping-adserver-and-ssp-placement-ids-to-relevant-yield-placements.md?ask=<question>&goal=<endgoal>
```

`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.