> 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/support-and-troubleshooting/data-quality-and-mapping/how-to-ensure-the-system-has-mapped-all-my-data.md).

# How to Ensure the System Has Mapped All My Data?

## Harnessing the Ad Revenue Insights module to Identify Unmapped SSP Placements with Revenue Yield

### What is Missing SSP Traffic?

Missing SSP traffic refers to SSP placements that have generated revenue but are not mapped within our system. When [establishing connections with new SSPs via the API](broken://pages/4bef1a875c1a4ac5273ae5f1eec165151fcb005b), our platform automatically collects data from these sources. This data is then cross-referenced with your inventory structure in Relevant Yield.

> The list includes essential information such as SSP name, placement details, corresponding SSP IDs, and total revenue accrued over the specified period.

### Find the Missing SSP Traffic

From the left navigation menu, go to **Admin > Missing SSP Traffic**.

You can easily map placements manually into your Publisher account, leveraging the detailed insights provided.

For quick reference, you have the option to export the data as a CSV file.

![Näyttökuva 2025-06-19 kello 9.22.16](/files/729c23bc5d1f4c79137833f2ee1f97fe586bd585)

If you require additional information or assistance, please don't hesitate to contact [support](broken://pages/b548f0284d8ea70222f204b00f639c1eebe8ab00) our your Technical Account Manager.


---

# 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/support-and-troubleshooting/data-quality-and-mapping/how-to-ensure-the-system-has-mapped-all-my-data.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.