Banners and interstitials
Standard in-app banners and full-screen interstitials.
Vectravia buys banner, native, video and rewarded placements inside mobile apps, checks each seller against the app-ads.txt file and reads GPP consent first.
In-app advertising places ads inside mobile apps: games, news apps, utilities and more. The bid request carries an OpenRTB App object instead of a Site object, with the app store ID and the bundle name.
Apps publish an app-ads.txt file on their developer website to list who may sell their inventory. Checking that file is the in-app equivalent of checking ads.txt on the web.
The App object gives the store ID, bundle and developer domain.
Path Check reads the developer app-ads.txt file and compares it with the SupplyChain object.
GPP and TCF strings are read before Audience Lab applies any data.
Banner, native, interstitial or video objects are matched to your creatives.
Standard in-app banners and full-screen interstitials.
Video a user chooses to watch in exchange for an in-app reward, where offered.
Native units that match the look of the app.
GPP carries consent for many regions in one string, and its US sections keep growing.
4
US state strings (Maryland, Indiana, Kentucky and Rhode Island) finalized for GPP on December 1, 2025
1.1
the most recent GPP API version listed by IAB Tech Lab (June 2023)
In-app ads are measured on viewability and on actions such as installs or in-app events where you share them. Signal Reports labels each figure as measured or modeled.
Every placement shows the app, the seller and the relationship declared in app-ads.txt.
| Standard | What it does here |
|---|---|
| app-ads.txt IAB Tech Lab | Lets app developers list the sellers authorized to sell their inventory. |
| Global Privacy Protocol (GPP) IAB Tech Lab | Carries consent and privacy signals, including US state strings, in the bid request. |
| OpenRTB 2.6 IAB Tech Lab | The App object identifies the app, store and developer for each request. |
Each product has its own page with the capabilities, standards and questions behind it.
Supply-path checks against ads.txt and sellers.json before every bid.
Identity and consent signals handled before data is used.
One budget, pacing and frequency view across seven channels.
In-stream and out-stream video
Banner inventory with quality controls
Ads that match the page they sit on
It is the app version of ads.txt. An app developer publishes it on the website listed in the app store to declare which companies may sell the app inventory.
Audience Lab reads the GPP or TCF string in the request before any audience data is used. If use is not permitted, the bid can still run on context alone.
Yes, where apps offer it. Rewarded placements arrive as Video requests from apps and are bought like other in-app video.
See how in-app sits beside your other channels in one budget, with the supply path shown for every placement.