> 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.md). # Mapping Use this section to connect your reporting data to the right entities in Relevant Yield. These guides cover placement mapping, demand mapping, label setup, and tools for keeping mappings up to date. ### In this section * [Mapping Ad Server and SSP Placement IDs to Relevant Yield Ad Revenue Insights Placements](/ad-revenue-insights/mapping/mapping-ad-server-and-ssp-placement-ids-to-relevant-yield-ad-revenue-insights-placements.md) — Map ad server and SSP placement IDs to Relevant Yield placements so Ad Revenue Insights can report revenue accurately. * [Advanced Mapping Tool](/ad-revenue-insights/mapping/advanced-mapping-tool.md) — Review missing SSP traffic, match new placements, and import updated mappings into Yield with the advanced mapping tool. * [Mapping Advertisers, Buyers and DSPs for Reporting](/ad-revenue-insights/mapping/mapping-advertisers-buyers-and-dsps-for-reporting.md) — Map advertisers, buyers, and DSPs in Ad Revenue Insights to reduce fragmentation and keep reporting consistent across dashboards and reports. * [Importing Advertisers for Mapping from Your CRM](/ad-revenue-insights/mapping/importing-advertisers-for-mapping-from-your-crm.md) — Import advertiser mappings from your CRM with a CSV file to speed up demand mapping setup in Yield. * [Adding Your Own Placement Labels](/ad-revenue-insights/mapping/adding-your-own-placement-labels.md) — Add custom placement labels to group inventory in Ad Revenue Insights and use them as a reporting dimension. --- # 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.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.