app-ads.txt for Authorized Digital Sellers

Frameplay’s intrinsic in-game advertising provides support for app-ads.txt, a mechanism for publishers to list their authorized digital sellers, in order to fight against fraud and misrepresented domains.

Please add the following entries to your root domain/app-ads.txt file:, 58779, DIRECT
‍, 22830, RESELLER, 0bfd66d529a55807
‍, 13850, DIRECT, f5ab79cb980f11d1
‍ , 4423, RESELLER, 060d053dcf45cbf3
‍** , *0000*, *TYPE*, *0000000000000000*

*The custom entry is specific to your Game Studio. This will be defined by your Frameplay Integration Specialist during the onboarding process.

Please don’t hesitate to contact us with any questions

Further detail on app-ads.txt can be found at the IAB – 

Additional Info

What is app-ads.txt?
Authorized Sellers for Apps (app-ads.txt) is an extension to the Authorized Digital Sellers (ads.txt) standard, which allows buyers to know who is authorized to buy and sell specific in-app ad inventory.

The extension is written to meet the requirements for software applications distributed through mobile app stores, connected television app stores, and other distribution channels of this nature. The core deliverables for app developers are to provide a developer website URL in app store listings, publish an app-ads.txt file, change the developer website URL for an app, and optionally indicate that there are no authorized sellers.

Why implement app-ads.txt?
App-ads.txt will optimize your opportunity to monetize your game via Frameplay’s intrinsic in-game capability. Advertisers use app-ads.txt to validate that they are buying inventory through an authorized source. Implementation is optional, but we strongly recommend adoption to optimize spend, as many buyers require this level of transparency. 

How does app-ads.txt work for mobile apps?
Non-RTB programmatic demand-side advertising buying technology referred to as a DSP scans the app-ads.txt file on a developer’s website to verify which ad sources are authorized to sell that app’s inventory. Via the DSP, the buyer will only accept validated ad sources listed on the file and authorized by the app developer.

How app-ads.txt can benefit your mobile app
The benefits to app-ads.txt are capturing revenue from brand spend and fighting ad fraud.

  • Capturing revenue from brand spend. Brands today represent a growing and potentially significant revenue opportunity for developers. We can expect that many buyers that adhere to app-ads.txt won’t purchase inventory missing the app-ads.txt file, just as they won’t buy unauthorized inventory on the web. Developers who don’t implement app-ads.txt are likely to be removed from the pool of targeted apps.
  • Fighting ad fraud. Bad actors may forge apps that impersonate legitimate apps, and mislead buyers to spend brand budgets on their forged inventory. Legitimate developers end up losing out on ad revenue that was originally intended for them. App-ads.txt blocks unauthorized developer impersonations and minimizes instances of fraud that ultimately hurt developers’ bottom line.

app-ads.txt example

How developers can make sure their inventory is covered by app-ads.txt:

Step 1.  Provide the developer website URL in your app listing
Ensure that your developer website is updated in the app stores. This website will be used by advertising platforms to verify the app-ads.txt file.

Step 2. Publish an app-ads.txt file
Create an app-ads.txt file in Notepad listing all the lines you received, and save.

Step 3. Upload
Upload the file in the root of your domain website (example:

Wrapping up ads-txt for apps
Frameplay enables intrinsic in-game advertising without disrupting the performance or the experience of the game. Our goal is to optimize monetization opportunities for game developers. Aligning with the app-ads.txt standard supports monetization optimization efforts for our valued game development partners.

Unlock the full potential of️ your ad revenue with Frameplay