Reporting Discrepancies

MoPub Reporting

MoPub generates reporting via two systems: our internal data, and Metamarkets. We offer Metamarkets as a service and tool for DSPs to visualize campaign performance and inventory availability. Metamarkets is the third-party vendor for our demand external reporting dashboard, and collects and processes data slightly differently from MoPub’s internal reporting.

Reporting Dashboard

The third-party vendor Metamarkets provides the dashboard our DSPs use for all system and bidding reporting. If you do not have access to your MoPub Metamarkets account, contact your account team or mopubDSPsuccess@twitter.com.

MoPub Reporting on ‘Impression’ and ‘Spend’

MoPub reports on the clear notification (Server-to-Server nurl and RTB 2.3 imptracker) using the ${AUCTION_ID} macro for Impressions and the ${AUCTION_PRICE} macro for Spend .

We also de-dupe based on ${AUCTION_ID} to ensure that you are not charged in the rare case of a duplicate impression. We require all DSPs in our exchange to adhere to the same reporting logic for “impressions” and “spend” as our own auction mechanics.

MoPub imptrackers are fired client-side from the user’s device, and not server-side from MoPub Marketplace servers. This means the impression tracker may fire from device locations all over the world. It’s important for buyers to minimize any potential latency this may cause in capturing the impressions.

Expected Discrepancies

Metamarkets and MoPub internal reporting are less than 3-4% discrepant with each other.

Most DSPs can expect a 1-5% discrepancy between their internal reporting and our Metamarkets reporting. This range is typical in a mobile exchange environment and is dependent on the impression ad size and format being cleared. In some cases, the discrepancy can be up to 10% for MRAID creatives.

In rare instances, there may be gaps in MetaMarket reporting for a few hours, which Metamarkets will then backfill. Be sure to check the main tab to see if there are such gaps before pulling a report.

Discrepancies in Billing Metrics

Metrics used for monthly billing are “auctions cleared” and “spend”. These two metrics should align. We have noted that “spend” is an estimate within your Metamarkets UI. In the case of a discrepancy, MoPub’s internal data is the final reporting used for billing and payments.

Discrepancies in Click Reporting

Discrepancies between your click reporting and MoPub’s click reporting in Metamarkets are common. This is usually caused by third-party conversion tracking, which MoPub does not currently support.

Troubleshooting Discrepancies

Begin by verifying that a discrepancy exists, then troubleshoot by checking how you handle a number of fields.

Verifying a Reporting Discrepancy

  1. Log into your MoPub Metamarkets account, and check if the metrics in the My Auctions view for Spend Estimate and Auctions Cleared align with your internal reporting.

  2. Compare the Metamarkets reporting for Spend Estimate and Auctions Cleared to your internal reporting by the following parameters:

    • Adomain or campaign
    • Application
    • Publisher
    • Ad Size
    • Country

Contact your account team or dspsupport@mopub.com for assistance.

Troubleshooting a Reporting Discrepancy

Troubleshoot discrepancies in RTB 2.3 or in Server-to-Server by checking how you handle various fields.

RTB 2.3

Check the following:

  • Confirm you are expiring the imptracker. We recommend you allow at least a five-hour window between an auction and a cleared impression (imptracker). This is especially important for ad formats where caching is leveraged; these include native and interstitial formats.

  • Confirm that you are passing the ${AUCTION_ID} macro via the bid response imptracker field to report a cleared impression? MoPub reports a cleared impression on the win notification, replacing the ${AUCTION_ID} macro.

  • Confirm that you are passing the ${AUCTION_PRICE} macro via the bid response imptracker parameter to report on the impression charge price? MoPub reports the impression charge price on the win notification replacing the ${AUCTION_PRICE} macro.

  • Confirm that you are counting an ‘impression’ from the imptracker ${AUCTION_ID} macro, and not an additional pixel within the ad markup.

  • Check that the reporting timezone aligns with the MoPub reporting timezone.

  • Confirm that you dedupe impressions by Impression ID. MoPub de-dupes by ${AUCTION_ID} to ensure you are not charged for a duplicate notification. This is a rare occurrence (less than 1%), but we strongly recommend you do this as well.

Server-to-Server

Check the following:

  • Confirm that you are expiring the nurl. We recommend you allow at least a five-hour window between an auction and a cleared impression (nurl). This is especially important for ad formats where caching is leveraged; these include native and interstitial formats.

  • Confirm that you are passing the ${AUCTION_ID} macro via the nurl parameter to report a cleared impression. MoPub reports a cleared impression on the win notification, replacing the ${AUCTION_ID} macro.

  • Confirm that you are passing the ${AUCTION_PRICE} macro via the nurl parameter to report on the impression charge price. MoPub reports the impression charge price on the win notification, replacing the ${AUCTION_PRICE} macro.

  • Confirm that you are counting an ‘impression’ from the nurl ${AUCTION_ID} macro, and not an additional pixel within the ad markup.

  • Check that the reporting timezone aligns with the MoPub reporting timezone.

  • Confirm that you dedupe impressions by Impression ID. MoPub de-dupes by ${AUCTION_ID} to ensure you are not charged for a duplicate notification. This is a rare occurrence (less than 1%), but we strongly recommend you do this as well.

FAQs

Is it normal for there to be discrepancy between my internal reporting and MoPub’s reporting?

Yes. Metamarkets and MoPub internal reporting are less than 3-4% discrepant with each other. Refer to Expected Discrepancies.

Which metrics should align between MoPub and my internal system’s reporting?

The metrics that should align are “auctions cleared” and “spend”. These two metrics are used for billing on a monthly basis.

Are click reporting discrepancies to be expected?

Yes, it is common for there to be a disparity between your click reporting and MoPub’s click reporting in MetaMarkets. This is usually caused by third-party conversion tracking, which MoPub does not currently support.

Why don’t the numbers in my Metamarkets account align with my monthly invoice?

MoPub generates reporting via two systems: our internal data, and Metamarkets, our third-party vendor for our demand external reporting dashboard. Metamarkets collects and processes data slightly differently from MoPub’s internal reporting, but the two are less than 3-4% discrepant with each other, and we have noted that “spend” is an estimate within your Metamarkets UI. MoPub’s internal data is the final reporting used for billing and payments.

Does MoPub bill me based on the numbers generated by MoPub’s system?

Yes, we bill based on the internal reporting generated within our system for “cleared auctions” and “spend”.

Last updated March 05, 2019

TWITTER, MOPUB, and the Bird logo are trademarks of Twitter, Inc. or its affiliates. All third party logos and trademarks included are the property of their respective owners.

© 2019 MoPub (a division of Twitter, Inc.)