LogoLogo
HomeThe PlatformBlogSchedule a demo
  • Getting Started
    • Welcome to AdLibertas
  • The Platform
    • How it works
    • User-Level Audience Reporting
      • Creating Reports
        • Creating a New User Report
        • Creating Advanced User-Level Reports
        • Advanced Audience Builder
        • Custom Event Metrics
      • Report Layout
        • Report Module: Audience Filtering
        • Chart Type Module: Absolute vs. Relative Reports
        • Daily Totals, Per User, Cumulative Totals
        • Lifecycle Reports
        • Forecasting Module
        • Statistics Module
        • Measuring Confidence
      • Advanced Reporting Methods
        • User Measurement & Calculation Details
        • Date Ranges: Define Audience vs. Create Report
        • Exclude GAID tracking opt-outs
        • Scheduled Reports: Keep Updated & Rolling
        • Reporting on a Firebase AB test
        • Understanding “Audience Restraints”
        • Adding user time to your reports
    • Consolidated Revenue Reporting
      • Reporting Discrepancies
      • Reporting Availability & Timezones
      • Ad Network Re-Repost; Also: Revenue Reconciliation Accuracy
      • Consolidated Reporting vs. Consolidated Inventory Reporting
      • Reporting Table – Column Descriptions Common Metrics (Calculated Fields)
      • Facebook Reporting
      • Consolidated Ad Revenue with multiple mediators
    • Business Analytics
      • Analytics Layout
      • Understanding the "Explore Data" button
      • The Data Table
      • Asking a Question
      • Saving a Question
      • Creating a custom dimension
      • Setting up a pulse
    • Custom Dashboards
      • Custom Dashboard Filters
      • Combining data into a single chart
    • Direct SQL Access
    • Exporting Data
      • Ad Network Reports
      • Chart Reports
      • Custom API connections
      • Downloading & Scheduling Data Reports
      • Deprecated: Line Item Change Log
    • General
      • Change your Username & Password
      • Adding Users to your Account
      • Sharing Collaborative Links
      • AdLibertas Cost
  • Data Integrations
    • Connecting in 3 steps
    • Ad Impression-Level Revenue Connections
      • AppLovin Max User Revenue API
      • ironSource Ad Revenue Measurement Integration
      • Impression level tracking with Admob Mediation
      • Collecting MoPub Impression-Level Data as a Firebase Event
    • Ad Network & Store Connections
      • Adding Ad Network Credentials
      • How does App Store Reporting work?
      • Adding access to Google Play
      • Adding Sub User to App Store Connect
      • Getting the most from Ad Network Reports
    • Analytics Connections
      • Data Set Status
      • Connect AdLibertas to Firebase
      • Connecting AdLibertas to BigQuery
      • Firebase Install Counts in Audience Reporting
      • Setting User Campaigns in Firebase
      • Why use revenue to determine Firebase AB test winners?
      • Firebase Best Practices: keeping Google BigQuery Costs Down
    • Custom Integrations
      • Sending Events via Webhooks to AdLibertas
      • Impression level tracking with Admob Mediation
      • Connecting AdLibertas to BigQuery
      • Importing a custom data set
    • IAP Connections
      • Tracking IAP & Subscriptions in Firebase and BigQuery
      • RevenueCat Integration: WebHooks
      • RevenueCat: Setting Universal Identifiers
    • MMP Connections
      • Connecting Adjust
      • Connecting AppsFlyer
      • Connecting Kochava
  • FAQs
    • General
      • Why does AdLibertas need credentials?
    • Audience Reporting
      • Why doesn't my daily active user count match Firebase?
      • Why doesn’t my retention rate match?
      • Why aren't my install rates matching?
      • Why doesn't my relative user count match retention?
      • What is the probability projected LTV becomes actual LTV?
      • Why doesn’t Firebase and AdLibertas revenue match?
    • Reporting
      • What is “non_mopub” revenue
      • How do customers use AdLibertas?
  • Privacy & Security
    • Privacy & Security Details
Powered by GitBook
On this page
  • Introduction:
  • Consolidated Reporting Tables
  • Avoiding duplication when migrating from MoPub to a new platform
  • Watch a video on how to dedupe revenue using consolidated reporting
  • Avoid duplication post-MoPub shutdown
  1. The Platform
  2. Consolidated Revenue Reporting

Consolidated Ad Revenue with multiple mediators

PreviousFacebook ReportingNextBusiness Analytics

Last updated 2 years ago

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

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

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:

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.

Watch a video on how to dedupe revenue using consolidated reporting

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.

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 ). This table is the basis for the 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 ). This reporting is used for the page

“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 ()

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 .

To do so, simply navigate to in your AdLibertas dashboard, then remove credentials from your dashboard.

Campaign Reporting
Ad Network Performance
Inventory Reporting
App Performance
more on non_mopub
serving discrepancy
Manage Connections