MoPub Demand Platform

The MoPub Demand Platform is a user interface that allows Marketplace buyers to optimize the traffic they receive, troubleshoot easily with bidder health metrics, and innovate more quickly with sandbox mode.

Getting Started

  • Access the MoPub Demand Platform at demand.mopub.com
  • For first time users, click the “Forgot password” link, enter your email address, and you will receive an email prompting you to login and set your password
  • Login with your username (it’s your email address) and new password
  • Contact your account team or mopubDSPsuccess@twitter.com with any questions or issues getting started. We are excited to put the power of MoPub Marketplace in your hands.

Bidder Homepage

This page will show all active and inactive bidder profiles for your DSP. You’ll see the unique bidder ID, the OpenRTB and Native spec version integration, and the endpoint URL for the bidder. You can click into the bidder profile to see the health charts, bidder settings, and inventory segments for each.

Homepage

Health Graphs

The bidder health dashboard helps give partners peace of mind that bidder integrations are functioning properly. It also gives visibility to take action faster if issues do arise. Demand partners are able to see metrics like the volume of requests missing due to QPS throttling, the percentage of requests that are timing out, and the proportion of responses that are malformed. See below for an explanation of each graph.

Healthpage

  • Requests and Timeouts: This graph will show you the number of requests (QPS) you’ve received, after all filtering & throttling has been done, compared to timeouts that your bidder experienced. Timeouts are where you do not respond within 300ms to an auction.
  • Requests and Latency: This graph will show you the number of requests (QPS) you’ve received, after all filtering & throttling has been done, as well as the average latency of your Bid Responses.
  • Total Available QPS: This graph will show you the number of requests (QPS) you’ve received, after all filtering & throttling has been done, compared to the upper bound requests (QPS) available on MoPub if there were no filtering or throttling set.
  • Bid Responses: This graph will show you the number of successful (200) Bid Responses from your bidder, compared to the number of Malformed Bid Responses. Malformed Bid Responses are responses that are missing required fields or have fields being passed improperly (id, crid, etc).
  • Available QPS (Post Filtering): This graph will show you the number of requests (QPS) you’ve received, after all filtering & throttling has been done, compared to the available QPS (post filtering) which encompasses QPS if you were not being throttled. Note: If you see a difference between the two lines represented in this graph, it could be because you have setup a segment with a QPS limit, thus preventing you from receiving the maximum QPS.
  • Requests and Throttling Rate: This graph will show you the number of requests (QPS) you’ve received, after all filtering & throttling has been done, compared to your throttling rate. Throttling rate refers to how much MoPub is reducing the maximum number of requests we could be sending due to timeotus from your bidder.

Bidder Settings

Here, you can edit your bidder name and endpoint URL, add an app allowlist or denylist, set exclusion filters for traffic you don’t want to receive, and opt into MoPub’s Auction Notification offering.

Biddersettings1 Biddersettings2

Inventory Segments

All active and inactive inventory segments, along with their QPS thresholds, are displayed here. You can easily toggle a segment on or off from this page, as well as edit or delete the segment.

Segmentshome

Creating New Inventory Segments

Demand partners have self-service access to decide what traffic they want to receive. They have the ability to filter based on operating system, ad format, and ad unit size. Partners can also manage QPS thresholds and add a geo allowlist or denylist.

Newsegment1 Newsegment2

Testing Sandbox

This sandbox leverages the same functions as MoPub’s production Marketplace, so partners can test new features, integrations, and endpoints with ease. Partners can easily receive sample bid requests and can respond from testing endpoints to try new features at any time.

Testingsandbox

  1. Select the ‘Testing’ tab from the top navigation bar.
    • Endpoint URL: Input the URL you would like to test with
    • Number of requests: Select the number of requests you would like to send to the endpoint
    • OpenRTB Version: Test MoPub OpenRTB 2.3 or OpenRTB 2.5
    • Native Version: Test MoPub Native 1.0.0.2 or Native 1.2
    • Platforms: Select the operating systems you would like to receive requests from
    • Ad Formats: Choose the ad formats and ad sizes you would like to bid on
  2. Click the ‘Submit Requests’ button

Troubleshooting Your Bid Responses

Bid Response Status Codes

  1. Other
    • Ensure you are formatting the assets properly and responding with required fields.
  2. Wrong Format
    • The bid response is missing ‘crtype’. Note that ‘crtype’ is only required in OpenRTB 2.3, it is deprecated in OpenRTB 2.5.
      • Native
        • RTB 2.3: bid.ext.crtype = ‘native’
      • Video
        • RTB 2.3: bid.ext.crtype = ‘VAST 2.0’ or ‘VAST 3.0’
  3. Missing Fields: Duration
    • For VAST bid responses, duration is an integer not a string.
      • Correct: “duration”: 30
      • Incorrect: “duration”: “30”
  4. Non HTTP OK
    • Buyer sent HTTP response code that was not one of the following:
      • 200 (HTTP OK)
      • 204 (No bid response)
      • 599 (timeout)
    • Click expand and scroll down to see the HTTP status code

Expand HTTP Status

Known Issues

  1. Error Message: “Error! Couldn’t parse data from MPX”
    • You will see this error message when sending 1000 or more requests
  2. Missing Fields are concatenated
    • A 2.3 bid response missing ‘imptrackers’ and ‘cat’ will look like ‘imptrackerscat’

Last updated August 24, 2020

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.

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