Prebid Mobile 3.0 accumulates the results of about 500 closed PRs for both platforms, aiming to extend supported inventory and enhance bidding transparency for In-App publishers and advertisers.
The current doc summarizes the key product features for the 3.0 milestone.
Prebid Mobile introduces a standardized protocol for SDK developers to implement custom ad rendering solutions within In-App Prebid integration. This flexibility allows demand partners to move beyond default options like Prebid Universal Creative, Google Ad Manager (GAM), or other built-in rendering solutions, giving them full control over the ad rendering process with their preferred technology.
For publishers, rendering delegation enhances ad quality and ensures a premium ad experience from trusted partners.
Prebid Mobile introduces an enhanced and more publisher-oriented RewardedAdUnit, allowing for greater customization, flexibility, and control over the rewarded ad experience, tailored to the specific needs of the publisher. The RewardedAdUnit implements special In-App behavior that should be configurable by the platform or publisher according to the application or ad experience guides.
Prebid Mobile introduces a way for publishers to add a convenient Prebid-owned first-party identifier to the bid requests. SharedID is a randomly generated first-party identifier that remains the same throughout the app sessions until reset. However, Shared ID values do not remain consistent across different apps on the same device.
Documentation:
Prebid Mobile introduces an API that enables publishers to customize the bid request according to their specific requirements. This customization can be done at two levels: global and impression level.
Prebid Mobile introduces a way to make multiformat bid requests for a single ad unit, specifically within a bidding-only setup. By leveraging this functionality, publishers can request bids that support any combination of ad formats, including banner, video, and native ads, within a single unified request. The SDK’s API was extended with the PrebidAdUnit and PrebidRequest classes responsible for managing multiformat bid requests.
Prebid Mobile introduces a native impression-tracking method that analyzes the application’s view hierarchy at runtime and tracks billing URL(s) only when the ad view is present on the screen. Using this approach, publishers can report more accurate figures for the impression count.
Prebid completely reworked the documentation for Mobile in two ways:
Documentation: iOS
Prebid Mobile introduces support for tracking domains in the initialization method of the SDK. Now, publishers can follow Apple’s ATT requirements and specify both tracking and non-tracking URLs for the Prebid Server.
Documentation: iOS
Prebid Mobile introduces support for SKAdNetwork across all integration APIs, including Bidding-only and Rendering APIs. SKAdNetwork is a privacy-focused solution that allows ad networks to track app installs while protecting user data. These methods include view-through and StoreKit-rendered ads.
Documentation: iOS
Prebid Mobile introduces support for SKOverlay for interstitials. SKOverlay enables developers to present additional content or calls to action as an overlay on top of interstitial ads without interrupting the overall flow of the ad experience.
Documentation: Ad Experience Controls
Prebid Mobile introduces enhanced support and configuration of video ads, including interstitial, outstream, and rewarded ads. The configuration values can either be initialized based on the bid response or explicitly defined by the publisher, providing flexibility in managing the user experience.
In the 3.0 release, the Prebid Mobile SDK gets rid of all previously deprecated methods in order to keep the API clean and minimalistic. Instead of using Ad Unit and configuration properties, the Prebid SDK encourages publishers to use methods to set Arbitrary OpenRTB parameters.