A growing share of programmatic supply comes from apps, and app inventory reaches an exchange differently from web inventory. There is no page tag. Ads load through code inside the app, the app's owner decides which partners get a chance, and device identifiers are not always available. If you run an exchange and want app supply, you need to understand how app publishers choose their demand, because that decides whether your exchange is in their auction at all.
How app publishers connect to demand
Ad network SDKs. The classic approach: the publisher adds a network's SDK to the app, and that SDK requests, renders and tracks its own ads. Each network means another SDK, more app size, more update work and more third-party code to review. Publishers keep only the SDKs that clearly earn their place.
Server-to-server (S2S). The app carries one lightweight SDK that talks to a server, which runs the auction with many partners over standard protocols such as OpenRTB and returns the winning ad for the app to render. The open-source example is Prebid: the Prebid Mobile SDK in the app sends requests to a Prebid Server instance that collects bids. Commercial platforms follow the same principle. New partners can be added on the server without an app release.
For an exchange, S2S is the natural way in. You do not ask a publisher to ship your code; you receive OpenRTB requests from the server side, from a mediation platform, a publisher's own server or a supply partner, and answer them like any other request.
Mediation: who gets the impression
Once several demand sources can fill a slot, a mediation layer decides who gets each impression.
The older model is the waterfall: sources are ranked, usually by historical average price, and called one after another until one fills. It is based on the past rather than on what each source would pay now, and sources lower down rarely get a fair chance.
The newer model is in-app bidding: eligible sources bid at the same time for each impression and the highest bid wins. Most real setups are hybrid, with bidders in a unified auction and non-bidding networks in a shorter waterfall behind them.
For an operator: being a real-time bidder is a much stronger position than a slot in someone's waterfall. Respond within the timeout, bid consistently and report wins and losses cleanly, and mediation platforms and app publishers will keep you in the auction.
What an app bid request looks like
In OpenRTB an app request carries an app object instead of a site object, with fields such as the app's bundle (its store identifier) and storeurl. Device data lives in the device object, including an advertising identifier where one is available.
That identifier is not guaranteed. On iOS it is only available if the user grants permission through Apple's App Tracking Transparency prompt, and on Android users can limit or reset it. Your demand partners will see many requests without one. Make sure the contextual signals you pass on (bundle, store URL, app category, placement, format) are complete and correct, because those are what buyers fall back on.
app-ads.txt: the door opener
Buyers check that whoever sells an app impression is authorised. For apps that means an app-ads.txt file on the developer website listed in the app store. If an app publisher's file does not list your exchange's account, many demand partners will not bid on that supply through you. Give every app supply partner the exact lines to add, and check them.
Formats and rendering
Rewarded video, interstitials, native and playable formats all appear in apps. Know which formats each supply partner sends and which ones each demand partner can actually serve. Sending video requests to a display-only buyer wastes requests on both sides and shows up as low bid rates in your statistics.
The operator's checklist for app supply
- Connect server-to-server, through partners that already aggregate app inventory.
- Pass
app,deviceand placement data on completely; do not strip fields buyers rely on. - Make sure your account is in the app-ads.txt files of the apps you sell.
- Match formats between supply and demand partners.
- Watch bid rates and timeouts by app bundle, not only by partner.
App supply rewards exchanges that are fast, accurate and well declared. None of that needs an SDK of your own. It needs clean integrations and someone watching the statistics.
Want to talk about your own setup? Get in touch with the Xendiz team.