Reporting Discrepancies

FAQ

1. Does MoPub provide a dashboard with my bidding reporting?

  • MoPub works with the third-party vendor MetaMarkets for all system & bidding reporting. If you do not have access to your MoPub MetaMarkets account please contact your account team or dspsupport@mopub.com.

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

  • Most DSPs will have a 1-5% discrepancy between their internal reporting and Metamarkets reporting. This range is typical in a mobile exchange environment and is dependent on the impression ad size and format being clearing. 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 couple hours, which MetaMarkets will then backfill. Be sure to check the main tab to see if there are such gaps before pulling a report.

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

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

4. Is it normal for click reporting to not align with the click reporting in my MetaMarkets dashboard?

  • 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 3rd party conversion tracking, which MoPub does not currently support.

5. What are steps to troubleshoot discrepancy?

There are several items to verify when troubleshooting discrepancy:

  • RTB 2.3
    • Are you expiring the ‘imptracker’?
      • We recommend at least 5 hours for an allowed window between auction and cleared impression (imptracker). This is specifically important for ad formats where caching is leveraged: native and interstitials.
    • Can you confirm 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.
    • Can you confirm 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.
    • Can you confirm you are counting an ‘impression’ from the imptracker ${AUCTION_ID} macro, and not an additional pixel within the ad markup?
    • Is the timezone of the reporting aligning with the timezone of the MoPub reporting?
    • Can you confirm you dedupe impressions by Impression ID? MoPub will de-dupe by ${AUCTION_ID} to ensure you are not charged for a duplicate notification. This is a rare occurrence (less than 1%), but we highly recommend you do this as well.
  • Server-to-Server
    • Are you expiring the ‘nURL’?
      • We recommend at least 5 hours for an allowed window between auction and cleared impression (nURL). This is specifically important for ad formats where caching is leveraged: native and interstitials.
    • Can you confirm 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.
    • Can you confirm 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.
    • Can you confirm you are counting an ‘impression’ from the nURL ${AUCTION_ID} macro, and not an additional pixel within the ad markup?
    • Is the timezone of the reporting aligning with the timezone of the MoPub reporting?
    • Can you confirm you dedupe impressions by Impression ID? MoPub will de-dupe by ${AUCTION_ID} to ensure you are not charged for a duplicate notification. This is a rare occurrence (less than 1%), but we highly recommend you do this as well.

6. How does MoPub report 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 ${AUCTION_PRICE} macro for Spend . We also de-dupe based on the ${AUCTION_ID} to ensure that you are not charged for a duplicate impression, in the rare case this should happen. We require all DSPs in our exchange to adhere to the same reporting logic for “impressions” and “spend” as our auction mechanics.
  • MoPub imptrackers are fired client side from the users 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.

7. What are steps for me to verify if there is a reporting discrepancy?

  • Log into your MoPub MetaMarkets account, and verify if the metrics in the My Auctions view for “Spend Estimate” and “Auctions Cleared” are aligning with your internal reporting.
  • Compare the MetaMarkets reporting for “Spend Estimate” and “Auctions Cleared” to your internal reporting by the below parameters:
    • Adomain or campaign
    • Application
    • Publisher
    • Ad Size
    • Country
  • Contact your account team or dspsupport@mopub.com for assistance.

8. How come the numbers in my MetaMarkets account don’t align with my monthly invoice?

  • MoPub generates reporting via two systems – our internal data & MetaMarkets. We offer MetaMarkets as a service & tool for DSPs to visualize campaign performance and inventory availability. MetaMarkets is our third party vendor for our demand external reporting dashboard, and will collect and process data slightly differently than MoPub’s internal reporting. MetaMarkets and MoPub reporting 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 / payments.

9. Will MoPub bill on the numbers generated by their system?

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

Last updated October 10, 2018

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.

© 2018 MoPub Inc.