Welcome to ClearBid!

The ClearBid team alongside all of UberMedia® would like to formally thank you for choosing ClearBid, the transparent solution for in app bidding. ClearBid was built by us, a publisher, to meet the needs we didn’t have in other solutions. As a result, we welcome your feedback or any product requests at any time. Please reach out to us at clearbid@ubermedia.com with any questions, concerns, feedback, suggestions, or help with any aspect of installation or support.

ClearBid works by reaching out to all of the demand sources you have configured in our UI ahead of the ad request being made to your mediation layer. You have in hand a winning bid at a known price point. This helps boost your monetization by putting additional pressure on your existing ad stack as well as providing solid monetization through the ClearBid stack. Everything is server-side and transparent, so you are welcome to add new demand, adjust existing demand, and make price band changes all without any SDK updates or app releases.

Let’s get to the specifics of using this product.

Overview

Administrative

  1. Setting up your account.
    1. Reach out to clearbid@ubermedia.com to get your login credentials. You may login at http://clearbid.ubermedia.com/login.
  2. Defining your placements
    1. Next you need to ad placements. Each placement should correspond to an ad unit in your mediation stack. Typically every platform (iOS or Android), app, and size within an app gets an individual placement. You can add as many as you need for discrete and accurate reporting purposes. Please make the placement name descriptive and without spaces.
  3. Supported ad types
    1. At the moment we support all banner sizes and interstitials. We’re working as hard as we can on video and native support.
  4. Choosing your price bands and auction adjustments
    1. Deciding on price bands is a decision that deserves a bit of thought. You can change this dynamically at any time, but please note that you’ll need to adjust targeting parameters in your mediation layer at the same time to avoid any issues. Price band can be different for every placement but are persistent to all demand in a given placement to keep the auction fair. More specifics can be found in “Strategies for ClearBid—Floors and Pricing”.
      1. ClearBid groups price points together for ease of targeting in the mediation layer, as a yield management tool, and to keep the number of line items manageable and within system limits for ad servers. We articulate price bands in the UI in the following format: [0.01,0.10,1.00,15.00].
        1. The value here is the lowest value CPM in USD in the price band and what will be passed into the mediation SDK in the targeting param “um_price:”. All values up to the next number in the comma separated range held in brackets will be grouped into that lowest value. In this instance, any winning bid from 0.01 to 0.09 will be have a corresponding um_price:0.01.
          1. It’s important to note that our system requires at least one integer in front of the decimal place and two values behind. Examples include “0.01” and “20.00”.
          2. These values are completely configurable on the fly, but if you make any changes, be sure to change the um_price values in your line item targeting as well.
          3. Be sure to put these in ascending order (smallest to largest) to keep the integrity of your intended price bands.
        2. You’ll need to make some decisions about how you group your price bands. Generally, it is best practice to have increased granularity around your average eCPM and less density elsewhere. Some examples are included.
        3. Additionally, how you value these line items in your ad stack is another tool for yield management. Conservatively you can place the value of all bids at the lowest range of the price band, which will correspond to the um_price you use to target the line item with. Others choose a median or a higher price to help push the other players in the space. It’s a strategy worth exploring and testing.
    2. Every demand source will have two multipliers available to you.
      1. Discrepancy multiplier: This value defaults to “1” and will adjust how that particular demand source’s bid will be valued in the ClearBid auction. If bids come in gross, you’ll want to adjust them to net for an “apples-to-apples” auction that is fair and accurate. In the case of a discrepancy, you can adjust this value to more accurately reflect its true value. Changing a value to “1.07” will increase the value of every bid by 7%, likewise changing the value to “.97” will put an downward adjustment of 3% on every bid. Please note that our logging and reporting tracks the original bid value, not the adjusted value.
      2. Throttle rate: This value default to “0”. Our system uses this to probabilistically adjusted the amount of queries sent to this demand source for that particular placement. Making this value “1” will stop the demand source, making this value “.25” will allow only 25% of requests to be sent.
    3. Adjusting all bids from the unified auction. To account for the cost of ClearBid and to make sure you are maintaining the integrity of your ad stack, you may elect to adjust all placements by the value of the revshare. For instance, if 10% is charged, you can apply a global adjustment of .9 to give you a true, net value of every auction to your ad stack.
  5. Configuring demand sources
    1. Adding new partners
      1. This is as easy as copy and pasting your unique values in the fields. This varies by partner. Any assistance required can be sent
    2. Throttling partners for testing
      1. Use the “throttle_rate” parameter described in the above section
    3. Turning partners on or off
      1. You can remove a partner by either removing your configuration values or setting your “throttle_rate” param to “1”
    4. Requesting UberAds® advertising solution demand
      1. Please contact clearbid@ubermedia.com for access
  6. Setting up mediation:
    1. Pricing strategies
      1. Ahead of setting up your line items, you should decide if you’ll value these line items with the minimum, maximum, median, or custom value of your price band described above
    2. Quick reference table
      Mopub All params are customizable, including height, width, and unique adunit_ids should be used
      Platform Type Class JSON
      iOS banner MPUberMediaBannerCustomEvent {“ad_unit_id”: “”}
      iOS interstitial ClearBidMPInterstitialCustomEvent {“h”: “320”, “ad_unit_id”: “”, “w”: “480”}
      Android banner com.ubermedia.MoPubAdapter {“ad_unit_id”: “”}
      Android interstitial com.ubermedia.MoPubInterstitialAdapter {“h”: “320”, “ad_unit_id”: “”, “w”: “480”}
      DFP
      Platform Type Label/Classname
      iOS banner  UMDFPTargetingCustomEventBanner
      iOS interstitial CBDFPInterstitialCustomEvent
      Android banner  com.ubermedia.DfpBannerAdapter
      Android interstitial   com.ubermedia.DfpInterstitialAdapter
    3. Mopub for banners
      1. Set up line items in Mopub in P12 (or wherever you have price priority to compete across the board). In the case above, you’ll need 33 line items for every size and placement you have. If you have 2 platforms (ios and android) and 2 sizes (320×50 and 300×250), you’ll need 132 line items, and I’d suggest you break those out into 4 separate orders. Here’s what the custom event looks like, this particular one is for the $1.00 line item. To make other line items, simply copy this one, change the name, change the um_price and change the line item value.You’ll apply inventory that is appropriate (one size per set of line items). No other targeting is necessary outside of the price point here:This line item only gets called if your other line items above $1.00 have failed to return an ad. Because of the custom targeting, the SDK will only get called if it has that bid and creative actually available. Of course there is some slippage in render rates and closing the app before render, but the fill should theoretically be 100% barring usual external forces that typically cause discrepancies.
      1. Mopub for interstitials
        1. The same process as above with the different class and json provided in the summary above
      2. DFP for banners
        1. Set up line items in DFP in Price Priority 12 (or wherever you have price priority to compete across the board). In the case above, you’ll need 33 line items for every size and placement you have. If you have 2 platforms (ios and android) and 2 sizes (320×50 and 300×250), you’ll need 132 line items, and I’d suggest you break those out into 4 separate orders. Here’s what the line item’s creative looks like, this particular one is for the $0.99 line item. To make other line items, simply copy this one, change the name, change the um_price and change the line item value.You’ll apply inventory that is appropriate (one size per set of line items). No other targeting is necessary outside of the price point here:This line item only gets called if your other line items/yield group partners/AdX above $.99 have failed to return an ad. Because of the custom targeting, the SDK will only get called if it has that bid and creative actually available. Of course there is some slippage in render rates and closing the app before render, but the fill should theoretically be 100% barring usual external forces that typically cause discrepancies.
      3. DFP for interstitials
        1. The same process as above with the different class and parameter provided in the summary above

QA

  1. Looking at network requests for ClearBid
  2. Mopub:
    1. Validate that um_price and um_bidder are being passed in the request
      1. You should see the bids passed in the ad call like this: 
    2. Validate the custom adapter is firing
      1. Here’s the headers that called the ClearBid adapter from Mopub on a winning bid, in this case Aerserv at $1.00. 
  3. DFP:
    1. Validate that um_price and um_bidder are being passed in the ad request 
    2. Validate the custom adapter is firing 

Reporting

For API access, please email clearbid@ubermedia.com. ClearBid utilizes UTC and all numbers are not adjusted by discrepancy multipliers.

S2S Connections

Please contact clearbid@ubermedia.com for more information.

Fine Tuning ClearBid

  1. Requesting new partner integrations
    1. Please contact clearbid@ubermedia.com for more information.
  2. A fair, unified auction: Adjusting for discrepancies
    1. In the case of discrepancies, it is prudent to adjust all incoming bids to make the auction in ClearBid reflective of reality. An easy way to adjust is look at third party revenue divided by ClearBid revenue for any demand source in any placement. The value of this should guide your adjustments.
  3. Changing price bands
    1. Adjustments and overhauls can be made at any time. Be sure to change targeted values for all line items to make sure you aren’t missing out on bids. Also be sure that all values in the array are in ascending order!

Strategies for ClearBid

  1. Floors and Price Bands
    1. We are working on some products to assist this, but publishers should certainly experiment with putting floors on demand sources and looking at net revenue outcomes.