> 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/setup/setting-up-ad-revenue-insights-in-relevant-yield.md).

# Setting Up Ad Revenue Insights in Relevant Yield

Setting up Ad Revenue Insights in Relevant Yield is quick and easy. Below are the main steps to follow during the onboarding process for Relevant Yield's Ad Revenue Insights module.

{% stepper %}
{% step %}

## Create a Map of Your SSP Placements

Your Relevant Digital Technical Account Manager will provide you with a document where you can list all your ad server placements and their corresponding SSP placement IDs. This will be useful later when mapping the SSP placements to the corresponding Relevant Yield placements.
{% endstep %}

{% step %}

## Log In and Give Access to Your Colleagues

You will receive an email with your credentials and a login URL for your Relevant Yield account. You can read more about user roles and how to create users in the documentation about [user management.](/general-platform/user-management/user-management-in-relevant-yield.md)
{% endstep %}

{% step %}

## Define Your Publisher/Website/Placement Structure

Whether you are a publisher or a network user, this article will teach you how to create your own placement structure: [What Are Publisher Accounts?](/general-platform/inventory-management/what-are-publisher-accounts.md)
{% endstep %}

{% step %}

## Add Integration to Your Ad Server

Add an ad server connection in the **Integrations** view of Relevant Yield. Learn more about ad server settings in [**Setting Up a New Ad Server Connection**](/ad-revenue-insights/data-connections/setting-up-a-new-ad-server-connection.md).
{% endstep %}

{% step %}

## Add SSPs

Add your SSPs in the same way you added your ad server. Learn more about SSP settings in [**Setting Up a New SSP Connection**](/ad-revenue-insights/data-connections/setting-up-a-new-ssp-connection-with-api.md).
{% endstep %}

{% step %}

## Map Ad Server and SSP IDs to Corresponding Relevant Yield Placements

Read more about [**mapping ad server and SSP placement IDs to Relevant Yield's Ad Revenue Insights placements.**](/ad-revenue-insights/mapping/mapping-ad-server-and-ssp-placement-ids-to-relevant-yield-ad-revenue-insights-placements.md)
{% endstep %}

{% step %}

## Set up Dashboards

Read more about [**How to use dashboards and reports**](/ad-revenue-insights/dashboards-and-reporting/how-to-use-dashboards-and-reports.md)
{% endstep %}

{% step %}

## Set up Advertiser Reporting

Read more about [**Importing Advertisers for Mapping from your CRM**](/ad-revenue-insights/mapping/importing-advertisers-for-mapping-from-your-crm.md)

and [**Mapping Advertisers & Buyers for reporting**](/ad-revenue-insights/mapping/mapping-advertisers-buyers-and-dsps-for-reporting.md)
{% endstep %}

{% step %}

## Validate Data

Make sure you have mapped all the IDs and check that the Ad Revenue Insights numbers match with ad server and SSP reports. Learn [**How to make sure the system has mapped all my data?**](/support-and-troubleshooting/data-quality-and-mapping/how-to-ensure-the-system-has-mapped-all-my-data.md)
{% endstep %}

{% step %}

## Set up Alarms

Read more about [**Setting Up Your Ad Revenue Insights Alarms**](/ad-revenue-insights/alarms-and-notifications/setting-up-your-ad-revenue-insights-alarms.md)
{% endstep %}

{% step %}

## Done

Go live with Ad Revenue Insights Insights!
{% 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/ad-revenue-insights/setup/setting-up-ad-revenue-insights-in-relevant-yield.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.