> 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/bulk-import-automated-mapping-of-your-hb-structure-with-.csv.md).

# Bulk import (automated mapping) of your HB structure with .csv

## Import your complete or partial mapping structure with adserver and SSP placement IDs with just a few steps

#### The steps described here are following the path that is needed in order to successfully bulk import your structure.

If your account manager completed all these steps during the Relevant Yield onboarding, you have the option to request a copy of the .csv file or you can start filling out the example .csv file that you downloaded in step 4..

{% stepper %}
{% step %}

## Configure settings for the adserver

Find instructions [HERE](broken://pages/cc153d5a09394e07039e874f900cdb82f89a5aaa)
{% endstep %}

{% step %}

## Add the new SSPs

Find instructions [HERE](broken://pages/bddb4efbdf5e4ad5af468b4b91ea66b77475e828)
{% endstep %}

{% step %}

## Set up Placement types

Find instructions [HERE](broken://pages/655a4b62e264cfc8c6b93be019316ac493e1f0ba)
{% endstep %}

{% step %}

## Download example .csv

Navigate to > Publisher Accounts > Import from CSV > Download Example CSV

<div data-with-frame="true"><img src="/files/a67f09c88993b7a87deea646570ec022874901da" alt=""></div>

When you click on the "CSV Import/export" and option to select or drag and drop your CSV file will appear.

You can " **Download example CSV**" file.

<div data-with-frame="true"><img src="/files/4d053a6ee93fd7b4ab7cd52b1074aaffad2f5757" alt=""></div>
{% endstep %}

{% step %}

## Export current structure to CSV

If you already have a structure in place, but want to see what all *Publishers > sites > placements > SSPs* you have in Relevant Yield, you can do that by clicking on the "Export current structure" as seen on bottom image.

<div data-with-frame="true"><img src="/files/e670535b1a56a3b6b5358e5b2d6549d53af83575" alt=""></div>
{% endstep %}

{% step %}

## Do a test import

Perform a test import by modifying the "Publisher name" to a test publisher name. This action will automatically generate a new publisher in your account. By doing this, you can verify the import and see how the structure will appear once you upload it for real.

* Columns with **typos** and wrong names will be **skipped - left empty**, so make sure the names match your integration names.
* **Extra spaces** in the names will also cause **typos** and will be skipped
* **Uppercase vs lowercase** letters will also cause **typos**

If there are no upload errors and you are satisfied with the appearance of the structure, you can safely remove the test publisher and proceed with the actual import.

**WARNING**! - Warning messages usually appear when something already exists in the RY system (e.g. adserver, placement name...). You can **ignore** those warning messages as it is just a reminder that you are updating the said "placement" with newly added SSPs.
{% endstep %}

{% step %}

## Do a "real" import and include new placements in configuration

After completing the import, the final step is to navigate to the "Prebid configuration" on the site level and make sure newly imported placements are enabled in the configuration (they should be added by default when importing, but its good to double-check everything is as it should).

This will ensure that the placements are included in the overall setup and can be used effectively.

<div data-with-frame="true"><img src="/files/03406ecd0821abf49cef02feee49fdb2bf091826" alt=""></div>

<div data-with-frame="true"><img src="/files/9e7d52836d270a5b837a4fe44501e669d1ae758b" alt=""></div>

And don't forget to confirm with **OK button** and then **SAVE button**!
{% 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/bulk-import-automated-mapping-of-your-hb-structure-with-.csv.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.