# Consolidated Ad Revenue with multiple mediators

### **Introduction:**

We’ve launched support to include reporting from the ironSource and Applovin mediators into your AdLibertas reporting. By default when migrating from MoPub, reporting will include revenue earned from both platforms.

### **Consolidated Reporting Tables**

<div align="center"><img src="/files/wwmPx5FMIcSIDGjFDu4M" alt=""></div>

The combined ad revenue is located in the tables `Consoldiated Reporting Data` and `Consolidated Reporting Inventory Data`

**Consolidated Reporting:** contains individual ad-unit and app performance by network. Since this data includes ad waterfall and placement data it cannot include ad impression request data. (In MAX this type of reporting is called [Campaign Reporting](https://docs.adlibertas.com/the-platform/consolidated-ad-network-reporting/campaign-reporting-vs.-inventory-reporting)). This table is the basis for the [Ad Network Performance](https://dashboard.adlibertas.com/static_reports) page.

**Consolidated Reporting Inventory Data:** This reporting table aggregates at the ad unit level and provides ad request and impression data. It cannot however report on individual network ad unit requests/bids (MoPub calls this type of reporting [Inventory Reporting](https://docs.adlibertas.com/the-platform/consolidated-ad-network-reporting/campaign-reporting-vs.-inventory-reporting)). This reporting is used for the [App Performance](https://dashboard.adlibertas.com/static_reports/top_app?from=2022-02-16\&to=2022-03-01) page

### **Avoiding duplication when migrating from MoPub to a new platform**

Since mediators report from the same revenue sources there can be duplicate reporting during your transition. To avoid duplication, you’ll need to filter out potentially duplicated data:

**“Non\_mopub”** app name refers to revenue that’s collected from a third-party network but cannot be attributed to an active ad unit in the Max configuration. During a transition, non\_mopub *may include revenue that’s being served by other mediators. For accuracy, filter-out non\_mopub to avoid duplicated revenue between platforms (*[*<mark style="color:blue;">more on non\_</mark>*<mark style="color:blue;">mopub</mark>](https://docs.adlibertas.com/faqs/reporting/what-is-non_mopub-revenue))

**Applovin revenue served through MoPub:** AppLovin revenue reporting comes through in zones, if you have the same zones running for both mediators, you’ll see discrepancies. This can extend to bidding, revenue served on Max.

**Reusing ad units** customers that use the same ad units on multiple platforms will see duplication as both Max and the new platform will report the entire amount of earned revenue causing a [serving discrepancy](https://www.adlibertas.com/impression-discrepancy/).

### **Watch a video on how to dedupe revenue using consolidated reporting**

{% embed url="<https://youtu.be/8KhtbiL_aJo>" %}

### Avoid duplication post-MoPub shutdown

Since AdLibertas connects directly to the revenue sources (e.g. directly to Google to pull Admob earnings) when you've migrated from Mopub and your new platform (Max or ironSource) also reports these earnings, **you'll need to disconnect network connections served through the mediator to avoid duplication.**

This simply means you should remove all network credentials for networks that you are serving through a mediator.

To do so, simply navigate to [<mark style="color:blue;">Manage Connections</mark>](https://dashboard.adlibertas.com/settings/credentials) in your AdLibertas dashboard, then remove credentials from your dashboard.

<img src="/files/tHmxbKUVoQtCGz1rl6tU" alt="" data-size="original">

![](/files/JTOCzSZUzxmHmu7aA73b)

<br>


---

# Agent Instructions: 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:

```
GET https://docs.adlibertas.com/the-platform/consolidated-revenue-reporting/consolidated-ad-revenue-with-multiple-mediators.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.