> 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/ad-revenue-insights/mapping/importing-advertisers-for-mapping-from-your-crm.md).
# Importing Advertisers for Mapping from Your CRM
If you prefer not to start the demand mapping from scratch, you can import your existing Advertiser setup from your CRM system using a CSV file.
This article explains how to import your existing advertiser setup from your CRM into Yield’s demand mapping. A general overview of demand mapping can be found [here](/ad-revenue-insights/mapping.md).
To get started, you should either reformat the CSV file from your CRM system or use the example file below. The CSV file will be imported into Yield, and it will map your advertisers accordingly. In addition, you can add an external ID, which can be any identifier you use in your CRM or elsewhere.
[**Click Here**](https://help.relevant-digital.com/hubfs/Import%20Advertisers%20Example.csv?hsLang=en) **to download an example CSV file.**
When creating your CSV file from your CRM system, the formatting should follow this structure:
```
IKEA, Ikea
IKEA, IKEA Systems B.V
IKEA, IKEA AT Adverserver
```
We do not support adding multiple advertisers on the same line, as some advertisers use commas in their names. In the example above, all advertisers would be mapped to “IKEA”.
To import the CSV to Yield, go to: **Configuration** → **Demand Mappings** → **Individual Advertisers**, then locate the “Import from .csv” button.
In the image below, you can see the process of selecting the correct columns based on the file you are uploading to the advertiser mapping.
---
# 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/ad-revenue-insights/mapping/importing-advertisers-for-mapping-from-your-crm.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.