Mobile for Bidders
Buying mobile inventory is very similar to buying other seller-specific external supply on Xandr. This page walks you through the process.
For full bid request documentation, see Bid Request.
At this time, only creatives conforming to the following specifications can serve on mobile inventory:
- Standard Banners, including MRAID
- Additional rich media creative types will be supported in the future
- Image (jpg, gif, png)
Buying Mobile Inventory
- Step 1. Ensure That You Accept Mobile Bid Requests
- Step 2. Target and Bid on Mobile Inventory
- Step 3. Receive Auction Results
Step 1. Ensure That You Accept Mobile Bid Requests
Bidder profiles allow you to filter for the bid requests that you want to receive. To accept mobile bid requests, you must allow the following values within an existing bidder profile or create a new bidder profile specifically for mobile bid requests:
For more details about updating or creating bidder profiles, see Legacy Bidder Profile Service.
Step 2. Target and Bid on Mobile Inventory
When Xandr receives an impression from mobile supply sources, Xandr routes these through a publisher, site, and tag ID combination, in increasing order of granularity. The Xandr bid request includes these IDs, allowing you to target specific slices of mobile inventory. For more information on the content of the inventory, please contact your Xandr representative.
The Xandr bid request for a mobile impression includes other fields that may be useful for your bidder to target. These fields include:
loc(only available on small percentage of impressions)
Step 3. Receive Auction Results
The Xandr Notify request is essential to tracking when an impression is served, the win price of the impression, and to provide you with any custom notify data you may have included with the bid.
Fields Supported by Mobile Bid Requests
Global App Id for Android and iOS devices (For example, for Angry Birds app: "app_id" : "com.rovio.angrybirds" for an Android device, "app_id" : "343200656" or "com.clickgamer.AngryBirds" for an iOS device)
Location of the user, provided in terms of latitude and longitude. Expressed in the format "snnn.ddd,snnn.ddd", for example +123.456 or -456.123. South and west are represented as negative. There can be a maximum of 5 decimal places of precision.
The ID for the carrier. You can use the Carrier Service to map carrier IDs to names and countries. A special carrier "WIFI" exists for users connecting via WiFi.
The ID of the device make on which the ad will be shown. You can use the Device Make Service to map device make IDs to names.
The ID of the device model on which the ad will be shown. You can use the Device Model Service to map device model IDs to names.
The ID of the type of device on which the ad will be shown. This is represented by an integer, and can be looked up using the Device Model Service. Allowed values, and their meanings:
|windowsadid||some||String||The Microsoft Advertising ID for Windows 8 and Windows Phone devices|
The Apple advertising identifier for iOS devices running iOS 6+.
|aaid||some||string||The Google advertising identifier for Android devices as retrieved from Google Play services.|
The SHA1 hash of the
The MD5 hash of the
sha1mac was deprecated as of May 7th, 2019. Do not use.
The OpenUDID of the device. This should only be sent for iOS versions 5 and below.
Example Request/Response Chain
The bid response allows custom notify data, which will be returned in the subsequent notifications.