Last updated on October 4, 2018
Once you have created a site in OpenX for either mobile appSynonymous with mobile. Refers to the use of an app via a mobile device, specifically to differentiate from mobile web. or for mobile webRefers to the use of the Internet via a mobile device web browser, specifically to differentiate from mobile app. browser inventoryAd space available on a website or app. The basic unit of inventory for OpenX is an ad unit., you need to create ad units for it. Ad units created under Mobile Sites are considered "mobile" ad units whether intended for mobile app or mobile browser display.
For ad units belonging to a mobile app siteAn OpenX component that represents top-level domains or subdomains and is used to organize ad units. Sites enable you to target and report on inventory performance., you can select OpenX, DFP, or MoPub as your ad serverA complete digital advertising platform where publishers sell, manage, and deliver their advertising inventory across all digital formats. to generate the corresponding tag.
If you're creating a mobile ad unitThe smallest inventory component that represents the space on a site where ads display. for video inventory, see the video-specific instructions for Creating a linear video ad unit. See Creating ad units for a list of all types of ad units you can create for different delivery mediums.
You may also opt in your mobile web ad units to rich media PMP deals.
Create a mobile ad unit for mobile web or mobile app
Open the mobile site for which you are creating an ad unit. A mobile "site" is needed in OpenX even for a mobile app, in order to group the inventory together for that app.
Click Create Ad Unit. The Create Ad Unit form is displayed.
In the Name field, enter a unique name.
- From the Ad Unit Type drop-down list, select Mobile.
- From the Ad Server drop-down list, select which ad server you are using: OpenX, DFP, or MoPub. If you choose DFP or MoPub, the Response Format field is removed from the form.
From the Ad Unit Size list, select a size for the ad unit. This is the width-by-height size of the ad unit's viewing area. Alternatively, you can specify a custom size for the ad unit. To do this, select Custom Size in the list, and in the Custom Width and Custom Height fields that appear, type in the ad unit's custom dimensions (in pixels).
If you want to specify multiple sizes for the ad unit (up to 5) so that more ads are eligible to serve to it, see Flexible ad units. For multiple sizes in a mobile app ad unit, the recommended size combinations are 320x480 and 300x250 or 480x320 and 300x250 for interstitial ads. Make sure that the primary size you select is the largest size and that the alternative size fits within the dimensions of the primary size.
(Optional) in the API Framework field, type to select one or more API frameworks. This information can then be passed to buyers. Note that populating this field will override any "af" query argument or OpenRTB "api" argument set in the ad requestCommunication from a web browser or app to an ad server to display an ad..
- (Optional) In the Screen LocationWhere the ad is on the page, such as above the fold (ATF) or below the fold (BTF). This is also referred to as "page position" or "page placement." list, select the placement of the ad unit on the screen, relative to the fold.
- (Optional) In the Site SectionA way of classifying inventory, for example into vertical segments of content. list, select the section of the site where the ad unit resides. This list contains any sections set up for the site in OpenX.
(Optional) In the Content TopicDescribes the main subject of the online content surrounding the ad space, such as sports or automotive. list, select a content topic for the ad unit, which describes the main subject of the online content that surrounds the ad unit on the webpage. Start typing in a string, and then select a content topic in the list. You can select multiple content topics for the ad unit.
(Optional) In the Content Type list, select the content type for the ad unit, which describes the main function of the content around the ad unit in the webpage. By default, OpenX populates this setting with the selected Default Content Type set for the ad unit's site container.
If the ad unit is for a display in mobile browsers (Mobile Web), select one of the following values from the Tag Type list to use when requesting ad delivery from OpenX:
iframe (the default). Uses HTML iframe tags (<iframe>) to deliver an ad (within a separate HTML document) to a specified ad unit.
image only. Uses HTML anchor tags (<a>) and image tags (<img>) to deliver an ad to a specified ad unit.
Depending on your OpenX configuration, you can select the Optimization check box to either:
Make this ad unit available to ad networks or ad exchanges that OpenX has relationships with (if you are using the ad server and also leveraging OpenX SSPSupply-side platform, a platform or provider that allows publishers to manage and optimize revenue for their inventory from multiple sources, often in real time. features).
Allow OpenX to sell this ad unit through the OpenX Ad Exchange (if you are an OpenX Ad Server customer and also leveraging the ad exchange).
- (Optional) In the Real-time Bid FloorThe minimum price a publisher is willing to accept for a given impression. field, you can set a floor price for the ad unit.
(Optional) In the Passback Ad TagA small piece of code that defines the ad space where ads display on a website. It includes parameters that describe the inventory advertising campaigns can target, which may in turn display ads in the ad space. field, type the HTML ad code for a fallback ad to serve in cases when the ad server would otherwise serve a blank ad. Note that if you are using DFP as your ad server for a mobile app ad unit, you can only use a secure (https) passback tag.
Note: You can enter a value in the Passback Ad Tag field if you have the appropriate permissions. You should leave the Passback Ad Tag field empty if you do not have a passback tag for the ad unit.
(Optional) In the External IdentifierA free-form reference ID. For example, "Debbie's Account." field, type a free-form reference ID.
Do one of the following to complete ad unit setup:
Click Create. The Create Ad Unit screen closes, and a confirmation message for the new ad unit appears above the ad units list.
Click Create and Add Another Ad Unit. This opens a new Create Ad Unit screen with a confirmation message for the new ad unit, where you can automatically begin creating another one for this account.
Click the drop-down arrow and then Create and Get Ad Tag. This opens the View Ad Unit screen for the new ad unit, and a confirmation message for the new ad unit appears above the ad tag.
After you create a mobile ad unit, a Mobile Ad Tag is generated. This base Mobile Ad Tag is necessary for serving ads, as well as validation and testing. You can retrieve the tag by selecting the ad unit and copying the Mobile Ad Tag displayed on the ad unit page.
For details about modifying the tag, see MoPub integration or DFP mobile app integration. If you want to further modify or enhance your MoPub or DFP tag, you can also add more fields to your OpenRTB parameter.