Marketplace Integration and Certification

• Existing Partners
• New Partners
• Bidder Setup
• iTunes to IAB Category Mapping
• Creative Attributes

This document dictates the steps necessary to integrate a bidder into the MoPub Marketplace.

Existing Partners

Please contact your account team or mopubDSPsuccess@twitter.com with any questions with getting started.

New Partners

To get started, please execute the contract, credit application, and evaluation form.

Once completed, you can begin testing your endpoint in the Demand Platform following the steps below.

Bidder Setup

1. Build your bidder to comply with the MoPub OpenRTB 2.5 spec (recommended). We also support OpenRTB version 2.3 (sunset TBD).

2. REQUIRED Test your endpoint in the Demand Platform Bidder Sandbox

   NOTE: All fields detailed below are required in the bidder response:

   a. Impression ID: The impression ID sent in your bid response (bid_response.id) must match the unique auction ID sent in the bid request (bid_request.id).

   b. Advertiser Domain (adomain): An array of advertiser domain names. For policy guidelines refer to section III Technical Requirements for Advertising Creatives.

   Required by MoPub policy:

   • All Adomains must be passed as the top-level domain with only .com or .countrycode appended. App store URLs are not acceptable.

   • Examples: advertiser.com or advertiser.de or advertiser.uk
     • Hay Day Android: “supercell.com”
     • iOS Nike Running: “nike.com”
     • Vodafone: “vodafone.de”
   • For dynamic creatives, the adomain should map to the top-level domain and be for a singular advertiser and single creative id.

   c. Bundle (bundle): Bundle or package name (e.g., com.foo.mygame) of the app being advertised. This is required for apps.

   d. Category (cat): IAB content categories of the creative. Refer to List 5.1 of the OpenRTB spec.

   e. Creative ID (crid): This should uniquely identify the creative for a campaign, and can be used for blocking or identification/aggregation purposes. Creative id’s should not be swapped (i.e. A single id must never have different adomains associated with it). Creative id’s should also never be 1:1 with an impression.

   f. Impression Trackers (imptrackers): For each bid response, the required ‘imptrackers’ field must contain the impression tracker URL(s) which will be called from the client device directly to the bidder’s servers upon the auction impression/charge event. At a minimum, the impression tracker URL should include substitution macros for ${AUCTION_ID} and ${AUCTION_PRICE}. More information on supported macros can be found in our OpenRTB specification guides.

   Note: It is imperative that the bidder leverage using the ‘imptrackers’ call because ‘imptrackers’ is triggered via the same SDK-side mechanism that MoPub uses to count successful rendering of the creative, and what you will be billed upon.

3. To verify that the bid response is valid, please copy/paste the text of a valid and complete bid response from the Demand Platform, save to a txt file, and email directly to your integrations AM.

4. Your integrations AM will schedule a one-hour integration call with your team. One member from your tech and ad ops team should be present.

5. Confirm acceptance of our Program Policy by submitting the Acceptance form. Please circulate these policies to all relevant internal team members.

6. MoPub leverages IAB Category blocking and Creative Attribute Blocking, all partners are required to support this. This data will be passed in the ‘bcat’ and ‘battr’ field.

7. Complete MoPub Spend Consent Form.

8. Testing

   1. Create a new test endpoint
      • Your endpoint will be capped at a maximum of 10,000 QPS for testing
   2. Go live on an iOS and Android application.
   3. Spend $100 per supported ad format (banner, interstitial, video, native) using creatives from your top 3 campaigns.
      • While this is a “testing” period, it is live traffic and a real application. You will be placing bids and winning inventory.Once you begin bidding on live inventory you will be billed for the impressions won.

9. Report Alignment and Troubleshooting

   Compare reporting to the data generated from the imptrackers URL and verify that reporting is less than 5% discrepant. Your integrations AM will confirm the specific time period to pull the reporting for.

   1. Report Breakdown:
      • Date, OS, application, size, creative type, creative id (if possible)
   2. Report Metrics:
      • Cleared impressions (based on ‘imptracker’ field), Auctions Won (if leveraging ‘nurl’), Spend
   3. UTC timezone

10. Troubleshooting

    • Did you compare all metrics from 8a above?
    • Do the creative IDs have similar discrepancies on the same RTB spec for the same SDK version, OS, and app?
    • Please test your creatives in the MoPub Sample App

11. Post Testing

    Once reporting alignment is complete, your integrations AM will work with you to customize your bidder setup. Let us know which countries you would like to receive inventory from and whether you have a max QPS your infrastructure can support. The total traffic on the MoPub exchange is currently 112k-250k QPS.

12. After customized set up is verified and complete, your integrations AM will turn you live on the RTB 2.5 or RTB 2.3 with the endpoint of your choice.

13. One week post-integration, we will do a check-in to review the integration and evaluate how to optimize your account.

iTunes to IAB Category Mapping

Creative Attributes

The values in bold below are always prohibited on the platform.