Monetize your mobile app with an in-app SDK or SDK-less integration, rewarded video, interstitials, and native ad formats that drive revenue without compromising user retention.
For a free app, ads are how you earn from the people who never buy anything. HBDR's in-app solution integrates the way your team prefers: through the HBDR in-app SDK, or SDK-less via server-side APIs. Either way your app connects to the full breadth of programmatic demand.
Our platform supports all major in-app ad formats — including rewarded video, interstitials, banners, and native ads — with intelligent mediation that maximizes eCPM across every user session. Advanced frequency capping and placement optimization ensure ads enhance rather than interrupt the user experience.
Every format optimized for engagement, revenue, and user retention.
| Placement | Format | Size | How it runs |
|---|---|---|---|
| Rewarded Video | Full screen · 15–30 s | Users opt-in to watch 15-30 second video ads in exchange for in-app rewards. Highest eCPMs with 90%+ completion rates and positive user sentiment. | |
| Interstitials | Full screen | Full-screen ads displayed at natural transition points. Smart frequency capping and contextual triggers ensure maximum impact without disrupting app flow. | |
| Native Ads | Custom template | Seamlessly integrated ads that match your app's look and feel. Custom templates ensure native placements feel organic while delivering strong eCPMs. | |
| Banner Ads | Standard · adaptive | Standard and adaptive banner placements optimized for mobile viewports. Smart refresh cycles maximize revenue per session while maintaining quality. |
Teams that want a client-side integration use the HBDR in-app SDK. Teams that prefer to keep their app lean connect SDK-less: the server-side approach reaches our auction engine through lightweight API calls, which keeps the app binary smaller and lets demand configuration change without an app store submission.
Our solution supports both iOS and Android with native-quality rendering, GDPR/CCPA-compliant consent management, and SKAdNetwork compatibility for attribution without the IDFA.
Attribution has changed on both platforms. On iOS 14.5 and later, an app must ask through App Tracking Transparency before it can read the IDFA; without permission it gets zeros, and install attribution runs through Apple's AdAttributionKit (iOS 17.4 and later) and SKAdNetwork, which work side by side and share ad network IDs. On Android, Google announced in October 2025 that it is retiring the Privacy Sandbox technologies, including the Attribution Reporting API, Protected Audience, Topics and the SDK Runtime; the Google advertising ID remains, resettable by the user and all zeros once they delete it.
The setup buyers and platforms check, whichever integration you choose.
Put app-ads.txt on the developer website listed on your App Store and Google Play pages, and list every seller authorized to sell your inventory. Buyers check the app's store listing against that file to confirm who may sell its inventory.
On iOS, add a clear NSUserTrackingUsageDescription and show the App Tracking Transparency prompt after the person has seen what the app does, not on first launch. People who decline still see ads; they are just measured through AdAttributionKit or SKAdNetwork.
Configure the app to accept attributable ads from each ad network you sell through. Apple's ad network IDs work for both AdAttributionKit and SKAdNetwork, so one list covers both.
Your consent platform writes the IAB Europe TCF string (version 2.3 since 2025) for users in Europe and the IAB Tech Lab Global Privacy Protocol (GPP) string for US state laws. Every SDK and server-side call should read and forward those strings, not a yes/no flag.
Ask each demand partner whether it measures through the IAB Tech Lab OM SDK, the standard that gives verification vendors the same viewability and invalid-traffic signals in apps as on web and CTV.
Sources: Apple Developer, AdAttributionKit, SKAdNetwork, App Tracking Transparency and advertisingIdentifier; Google, Update on Plans for Privacy Sandbox Technologies (17 October 2025); Google Play Console Help, Advertising ID; IAB Tech Lab, ads.txt and app-ads.txt, Global Privacy Protocol and Open Measurement SDK; IAB Europe, TCF v2.3.
HBDR has served ads since 2015 for publishers on the web, in apps and on connected TV.