Last updated on August 28, 2017
The OpenX Mobile Android SDK leverages the server-side controls on the OpenX platform to safeguard apps against low quality ads, including a creativeThe media asset associated with an ad, such as an image or video file. scanner, whitelistMarking a particular entity as “approved” in order to ensure it is included. A whitelist will block new entities by default whereas a blacklist will allow new entities by default. For example, you could use a whitelist to only allow the "Technology" industry. and blacklistBlocking a particular entity's access to your inventory from the Ad Exchange. A blacklist will allow new entities by default whereas a whitelist will block new entities by default. capabilities, and brand filters. The SDK provides smart logic that minimizes re-directs and spoofed user clicks. It also exposes a unique transaction ID for every ad, giving you immediate control to manage and report ad qualitySettings that control the types of ads that can display on your inventory. issues as they occur.
Transaction ID for identifying ads
The callback method
AdDetails, which includes a
transactionId that uniquely identifies the ad. Use the
adDidLoad method in your
AdEventsListener interface to always have a unique identifier for each ad delivered by the SDK. See examples in banner integration and interstitial integration.
Reporting ad quality issues
If you need to report an ad to OpenX, please create an Ad Quality case at https://community.openx.com/s/contactsupport and include as much of the following information as possible:
- The transaction ID.
- Screenshots and device information.
- Category of the ad quality issue. See the list of categories available in the Ad Reporter tool for examples.
OpenX will review the trace information about the ad and work to resolve the issue.